Every two weeks or so, the Micro Frontends Squad has a Product & Design session. I’ll try to regularly post notifications about these calls before they happen; the calls are also publicly accessible and kept up-to-date on the OpenMRS calendar.
The next call is this coming Monday, and we have a special agenda: We’ll be working through ideas for Design Systems from UX Designer Ciarán Duffy (profile here; portfolio here). Ciarán will lead us through:
- What is a design system
- Examples applied to OpenMRS
- Common Reservations
When: Monday July 13, 7:30pm IST | 5pm Nairobi | 4pm Cape Town | 2pm UTC | 10am Boston | 7am Seattle
Where: https://om.rs/zoommicrofrontend Meeting ID: 501 082 750 One tap mobile +12532158782,501082750# US +13462487799,501082750# US
Background on Styleguides Discussions in this Squad
The full story of concerns and posts started here in a PR and here in Talk if you want to read about the pros and cons in detail, but the tl;dr of that conversation was that we were very concerned that getting attached to a given 3rd party library would cause massive upgrade issues/tech debt we’d have to sort out whenever the 3rd party updated.
Over the last year we’ve been trying out the OMRS style guide that we made at that time. Getting code-hitched to a 3rd party that causes us upgrade pain is still a very reasonable concern (and arguably in tension with a core promise of MFEs: making front-end updates much easier). We are not the only organization with these concerns. Many organizations decide to use their own styleguide. But, not having clear design guidance (both for code and UI) is currently slowing us down, and we need to make the best use of the wonderful dev contributors we have available. An interesting quandry!
(Others are welcome to add or correct my understanding of the background and present state.)
Notes and a visual recording will be available after as well.