4 ms·
In our foundational setup for the new https://beta.nasa.gov https://beta.nasa.gov and https://beta.science.nasa.gov https://beta.science.nasa.gov websites, we'v
by raylus 3y ago
In our foundational setup for the new https://beta.nasa.gov https://beta.nasa.gov and https://beta.science.nasa.gov 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#:~:text=The%2021st%20Century%20Integrated%20Digital%20Experience%20Act%20(IDEA)%20requires%20federal,their%20websites%20and%20digital%20services https://www.hhs.gov/web/governance/21st-century-idea.html#:~....
- thaumasiotes 3y ago> 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?
- junon 3y agoI would wager the intention there is that the prefix is unnecessary or that it could otherwise reflect the name of the toolkit as opposed to the country. As an American I also find it a little "yeehaw, 'murica" and not the norm for design frameworks, but it's much ado about nothing.
- wink 3y agoSomewhere 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-...
- koshergweilo 3y ago*god-save-the-queen-hr-<colour>
- galaxyLogic 3y agoLOL
- raylus 3y agohaha, 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/ https://unocss.dev/ ♥