A design system for the federal government

Re:A design system for the federal government by raylus on Monday September 11, 2023 @02:16AM (#37463541)

In our foundational setup for the new https://beta.nasa.gov and https://beta.science.nasa.gov websites, we've adopted the US Web Design System (USWDS). While our other core products primarily rely on Tailwind, we are quite familiar with this toolkit. In my opinion, comparing the two is not entirely straightforward, but the USWDS toolkit has been implemented effectively, despite some of its "America First" usa-* class names.

The decision to use the same toolkit across our projects is largely influenced by the 21st Century Integrated Digital Experience Act (IDEA), which mandates federal agencies to modernize their websites and digital services. You can find more information about IDEA here: https://www.hhs.gov/web/governance/21st-century-idea.html#:~....

[ Parent | on HN ]

Re:A design system for the federal government by thaumasiotes on Monday September 11, 2023 @05:10AM (#37464689)

> despite some of its "America First" usa-* class names

It's the American government... isn't it?

What namespace would you expect them to use?

[ Parent | on HN ]

[dead]

Re:A design system for the federal government by wink on Monday September 11, 2023 @11:33AM (#37468823)

Somewhere in London some intern at gov.uk is still not finished rewriting all the god-save-the-queen-hr-<color> CSS class names to god-save-the-king-...

[ Parent | on HN ]

Re:A design system for the federal government by koshergweilo on Monday September 11, 2023 @03:02PM (#37472081)

*god-save-the-queen-hr-<colour>

[ Parent | on HN ]

Re:A design system for the federal government by galaxyLogic on Monday September 11, 2023 @03:14PM (#37472270)

LOL

[ Parent | on HN ]

Re:A design system for the federal government by raylus on Friday September 15, 2023 @09:25AM (#37522596)

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/ ♥

[ Parent | on HN ]