Obviously niche, but the GOV.UK Design System is very well supported in Rails.<p>There's a form builder and library of components (built and maintained by me) which, between them, provide full coverage. Most new Rails services use them.<p>It's a good match because accessibility is one of the Design Systems' primary concerns so JavaScript is used very sparingly and only to enhance.<p>They're not official, only Nunjucks is supported by the Design System team.<p><a href="https://design-system.service.gov.uk/" rel="nofollow">https://design-system.service.gov.uk/</a><p><a href="https://govuk-form-builder.netlify.app/" rel="nofollow">https://govuk-form-builder.netlify.app/</a><p><a href="https://govuk-components.netlify.app/" rel="nofollow">https://govuk-components.netlify.app/</a>
Not to nitpick terminology, but I don't think it's helpful to equate "design system" with component library. A design system is the design tokens used to describe an organization's application(s), and largely independent of the exact technologies.<p>I worked with our UX team at a mixed tech company (Rails, React, mobile) who defined the patterns and tokens, and then my team implemented so that we could use across our stack.<p>Largely this was accomplished via ensuring the design system could be used via CSS and we settled on Bootstrap with custom theme. This made it easy enough to use across Rails views/view components and React components.<p>Bootstrap is not sexy to devs now but you could do same with Tailwind and Daisy UI with custom theme.<p>With that said, component libraries are really helpful, but I prefer to align them with the design system and not the other way around.
I came across CSS Zero recently:<p><a href="https://csszero.lazaronixon.com/lookbook/pages/overview" rel="nofollow">https://csszero.lazaronixon.com/lookbook/pages/overview</a><p>which bills itself as an "opinionated front-end starter kit" specifically for Rails and includes Stimulus.js code for JavaScript functionality.<p>It seems the benefits are that it is no build (pure CSS with CSS variables) and easy to modify and extend.
Totally get the struggle — I spent way too many hours figuring which design system should I use for my next project. Ended up creating a site to compare the options: [<a href="https://rails.style" rel="nofollow">https://rails.style</a>]. Might help others in the same spot.
I'm currently building one called Nitro Kit.<p>Everyone seems to have their own opinion on what something like this should and should be or do. Nitro Kit is my opinion and I'm getting a lot of joy from using it on my own sites and services.<p>It's free and open source and, full disclaimer, there's a paid premium offering too.<p><a href="https://nitrokit.dev/" rel="nofollow">https://nitrokit.dev/</a><p>Here's a video about my reasoning behind building it:<p><a href="https://www.youtube.com/watch?v=Li-RPk561l8" rel="nofollow">https://www.youtube.com/watch?v=Li-RPk561l8</a>
Github's <a href="https://primer.style/product/getting-started/" rel="nofollow">https://primer.style/product/getting-started/</a> does a good job of making a cohesive design language that works just as well for server-rendering Ruby views and "upgrading" parts of the ui to React views when you need more interactivity. That's a constraint that I wish more of the Rails ecosystem design tooling would attempt to solve for.
Just saw a BugBytes video for a new one that might be interesting - <a href="https://devdojo.com/pines" rel="nofollow">https://devdojo.com/pines</a>
I really think that a design system solution has to be framework/implementation agnostic. It’s why I’ve never been too interested in shadcn, impressive though it may be.<p>Right now I’m trying to build a tool that produces an intermediate representation of your UI components, which can then be transpiled into whatever target format you prefer.<p>That way we can build design systems that aren’t coupled to a specific downstream tech stack.
I use TailwindUI for many of my rails projects. Or just grab some Tailwind things from around the web.<p>Tailwind has really rekindled my joy in creating views.