Build on shared foundations.
Use the design system in any framework, or with plain HTML. No runtime dependency is required for the styles.
1. Add the styles
Download and vendor a reviewed release into your application. Load tokens before components. The documentation shell styles are separate from the reusable UI styles.
<link rel="stylesheet" href="/vendor/skunkworks/tokens.css">
<link rel="stylesheet" href="/vendor/skunkworks/components.css">
<script src="/vendor/skunkworks/components.js" defer></script>Map the Skunkworks Group colour tokens to semantic roles in your application. Check the resulting foreground and background pairings in both themes.
2. Use semantic markup
<a class="sk-button" href="/services/">Explore services <span aria-hidden="true">→</span></a>
<button class="sk-button secondary" type="button">Save draft</button>Use links for navigation and buttons for actions. CSS classes do not add semantics to an element.
3. Choose a theme
<html lang="en-ZA" data-theme="dark">Set data-theme="light" or dark on the root. Omit the attribute to follow the operating system. Save a preference only after the user chooses it.
4. Validate the integration
- Test the actual application with a keyboard and screen reader.
- Check both themes, zoom to 200%, long labels and narrow viewports.
- Keep authentication, permissions and persistence in your application services.
- Pin the resource version and review release notes before upgrading.
Source and downloads
Explore the GitHub repository ↗ or use the downloadable resources.

