Building a REI Resupply Used Inventory Notifier
Get notified of 'New' Used Gear. This was a humble attempt to help encourage people to minimize the impact on the Earth.
Cut to the chase - the GitHub Repository with a List of Government Design Systems is here.
As classically defined, a Design System is:
A design system is a collection of reusable components and clear standards that can be assembled together to build any number of applications. Design systems aid in digital product design and development of products such as mobile applications or websites. Source: Wikipedia
There isn’t much to debate here, the government tends to stick to the above definition for what a Design System is and how teams can/should utilize it. There may, however, be multiple design systems within a Department/Entity if there are different user-facing applications (i.e. end-users v. internal-only users v specific workplace setting). You can even see this within the United Kingdom with the National Health Service having their own Design System and smaller towns having their own.
Initially, I set out on this as a way to determine who is utilizing Web Components within their Design System. Web Components are a way to encapsulate a set of features allowing you to use them in microfrontends - regardless of the Javascript Framework. My thinking here was that if development teams created Web Components, various departments would not be married to a singular application framework and could start to build in consistency across applications with different technologies.
However, it’s since expanded a bit into a broad list of Design Systems exist at the Federal/Country, State/Regional, and Local/Municipal level.
Currently, there are 37 known Government Design Systems chronicled on the GitHub Repository. I’m sure that even since initially collecting this information about a year ago more have popped up onto the scene and some have maybe even been deprecated.
The review process takes a bit of time for each Government Design System since there is not a standardized way that the documentation is written. Sourcing whether or not components in the design system are a11y friendly / 508 compliant often takes some manual work to explore. Finding out other information like if there is a Storybook / Figma page requires in depth reading of the documentation.
Perhaps there is a way to expedite this process in the future, but once it’s chronicled, I don’t expect many of the entries to change.
By collecting this information, I feel that it can help other digital service or delivery teams that operate in the public sector reuse existing technologies to expedite delivery.
If you know of a government design system that is not currently listed in this repository, please create a new issue with the details. Include as much information as possible, such as the name of the government entity, a link to the design system, and any other relevant information.
If you find any bugs or issues, please create a new issue in the issue tracker. Describe the issue in detail so we can reproduce it and fix it.
If you have an idea for a new feature or an enhancement to an existing one, please create a new issue in the issue tracker. Describe your idea in detail so we can discuss it further.