Contribute to Apollion
This section is for people who change the design system itself: the component folders, the vendor
wrappers, the token engine and the release. Every engine change must state its impact on the layers above
it — a change that leaks engine detail into the theming config or the token vocabulary is wrong.
Contributing
The codebase
- Repository Layout — the six-file component folder and the documentation layers.
- Vendor Isolation — why every third-party library sits behind
src/vendors/<Lib>/. - App Scaffolding — the
@apollion-dsi/scriptsCLI.
The engine
- Theming, Config-First — runtime and build share one derivation, pinned by parity tests.
- Output Formats — the pure renderers over the token IR.
- Server-Side Rendering — deterministic class names and static output.
The gate
Run yarn validate before you push. The pre-push hook enforces it locally; CI runs only on demand.
Use Conventional Commits, stage files by name, and add a changeset for every consumer-visible change.