-
uswds
The U.S. Web Design System helps the federal government build fast, accessible, mobile-friendly websites.
I would like to note that there currently is no centralized Design System for the Dutch Government, unfortunately. All agencies are creating their own Design System based on the Rijkshuisstijl.
Currently I'm working on ROOS (https://rvo.nl/roos) which is the Design System for the Netherlands Enterprise Agency. This is build with the already mentioned NL Design System. My hope being that this will bring the different agencies together and start working on a centralized Design System for the Dutch Government and follow the excellent examples of https://design-system.service.gov.uk and https://designsystem.digital.gov/
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
> You're unlikely to build anything that's usable by everyone using React/Vue/Angular.
I wonder why so few actually try doing this. I mentioned this in another comment, but PrimeFaces is one of the few (only one?) sets of usable components, that have libraries available for Angular/React/Vue/Java (though using Java is a bit of a mess because of JSF, though some like it): https://www.primefaces.org/
It's immensely cool to be able to use similar components and such across different technologies, as opposed to wanting one of those component libraries and thus being pigeonholed into either using just React (or something else), or third party bindings of questionable quality.
It's probably never going to be truly 1:1, but getting close enough seems like a good thing to me, here's an example of a random component:
https://primeng.org/treetable
https://primereact.org/treetable/
https://primevue.org/treetable/
https://www.primefaces.org/showcase/ui/data/treetable/basic....
-
-
-
-
haha, fair point. Still, I'm on the fence about how utility components are namespaced in USWDS. Perhaps giving users the flexibility to define the namespace might work better? One thing that bugs me is the absence of class-sorting like we have in TailwindCSS. Plus, there are some gaps I've noticed in USWDS. The naming, especially when comparing "padding-x-2" and "p-x-2", can be really annoying when switching around, maybe that could also be an option for the developer or project. Similar to the ideas antfu has on uno.css https://unocss.dev/ ♥
