primeng VS uswds

PrimeNg GitHub

> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.

Would you like to elaborate on that?

In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.

For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/

Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/

Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main

Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/

React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.

Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.

PrimeNG (MIT license)

PrimeNg Release Notes

PrimeNG: Something nice about this collection is how you choose the base theme. You are presented with choosing design options that are taken from other popular design frameworks such as Material Design, Bootstrap, Soho, Fluent, Nano, and more. This is done with a visual editor, which is part of the theming options. PrimeNG also has a Figma UI kit, ready-made templates, and a SASS API.

PrimeNG is released under the MIT License https://github.com/primefaces/primeng/blob/master/LICENSE.md

We use PrimeNG which MIT licensed. It's great.

After months of hard work, we're excited to share the new major update on PrimeNG that mostly focuses on the documentation.

Now and then I stumble upon the USWDS (the article mentions it) and am surprised how good that thing actually is.

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/

I learnt a lot of Sass patterns from using the US Web Design System.

USWDS: https://designsystem.digital.gov/

FYI I recommend following U.S. gov't standards: https://designsystem.digital.gov/documentation/developers/

Dark/light mode is fine and all, however be wary of accessibility. Note that the US actually even publishes it's own CSS/JS framework similar to bootstrap. I believe (but I am not positive) it is here: https://designsystem.digital.gov/

I don't claim it to be perfect, but the last time I had the opportunity to use it, it put other UI/UX frameworks to shame.