Release 1.0.0-alpha.1 · CMSgov/design-system

🚀 Added

Utility classes! A utility class modifies a single trait, typically a single CSS property. To apply a trait, or a combination of traits to an element, add the corresponding utility class directly to the HTML element. We can begin using utility classes to prototype possible components. Once we've identified what these components are, we can then roll them into the design system using more succinct names. This is just a first pass and I'm very open to feedback, especially on the naming convention. I'm currently favoring clarity over succinctness. This means the design system may be verbose, but it should deliver clarity and resilience in exchange. The styling of these utility classes will likely also evolve as we continue pushing on the design front.
A new base CSS layer. You can apply the ds-base class to the <body> or parent element to apply a base layer of styling (color, font-family, font-size, line-height). Let me know if you have feedback or more ideas on how we can apply base HTML styles while still allowing the design system to be effectively implemented into existing codebases.

The namespace changed from hc- to ds- to align closer with CMS.gov as a whole, rather than being tied to just HealthCare.gov. No promises that this will be the last time this changes 😬
The package is now published to the cmsgov NPM account rather than Nava's. If you previously installed the package, you'll want to update the package name since it's now @cmsgov/design-system-core.

Still lots of work to be done, but there's now a bit more organization applied to the documentation.
Code snippets can now be hidden using the @hide-markup KSS flag
A new @status KSS flag allows us to mark components as Prototype/Alpha/Beta/etc
Published online so anyone can now read it without generating it locally. Temporarily hosted on S3 until we get GitHub pages working.
KSS markup comments can now use EJS to generate more complex examples.