Started writing a decision log for our #DesignSystem. Documenting why we chose to build plain ol' #HTML and #CSS where we can and #WebComponents where client-side #JS is needed is turning into a bit of a manifesto. Essentially we're using (and encouraging others to use) #ProgressiveEnhancement 😉
Spent this afternoon wrangling NPM dependencies in our #DesignSystem's monorepo. Managed to nuke a few and also eliminate all the vulnerable package versions being reported by npm audit.
I think something that can sometimes be misunderstood about the GOV.UK Design System is that if you find a component or pattern isn't right for your users, you can adapt or create a new one
Dzisiaj artykuł wyjątkowy, bo... nienapisany przeze mnie. Powitajcie Ewelinę, która mam nadzieję, że co jakiś napisze coś o byciu PO oraz swojej pasji, czyli UX. Na pierwszy ogień bierze temat Design Systemu. Zapraszam.
I think the GOV.UK Design System is very close to this. Widely tested, accessible, tech-agnostic, just needs to be more theme-able (edit - including internationalisation, thanks @whitingx )
@joelanman - I find the concept of a 🌐 Global #DesignSystem interesting and have been following along with the discussions being led by @brad_frost.
Great to see a focus on #Accessibility in the plans but feels like we risk losing a lot of creativity and diversity by working from a standardised, homogenised system. 🤔
@joelanman -
Your example of the GDS #DesignSystem as a frame of reference for this 🌐 Global Design System is a good call - but seeing the work³ done⁴ by various⁵ Orgs. required to extend this, and the reduction in support⁶ for other GovUK tools, also would be interesting to see more conversation to address how this Global Design System might be maintained and iterated on. 🤔
@joelanman - That's right, extensibility is certainly a positive thing. 👍
Issue I've seen though is that these changes made at an org. specific #DesignSystem level rarely/never make it back upstream to the primary DS meaning we have further 🔀 fragmentation and disparity of approaches that become difficult/impossible to reconcile as projects progress. 🤔
As you say, these useful elements should make it back into the main DS but in regard to evidence and examples I've seen of this … ¯_(ツ)_/¯
Out of interest - Do you know if the process to move elements/components back upstream to the GDS #DesignSystem are documented anywhere? And if there are any examples/blog posts showing how this has worked to share with others? 🤔
Once again facing that classic #designsystem conundrum: Theme and/or customize a 3rd party component library, or build one from scratch.
Actually, we need two component libs: A #WebComponent one for web products and a #ReactNative one for iOS & Android apps. We already have designs in #Figma and want to have parity in terms of design & naming across Figma, web & RN.
My gut and past experiences make me lean towards building from scratch.
The Nord Design System team are 🤏🏻 this close to wrapping up on the first iteration of a project we began building just over a year ago, a project that was designed to be Just The Beginning™ for Nordhealth's flagship product Provet Cloud https://provet.cloud