# Abilian Design System > A closed token vocabulary for Litestar and Jinja. A few knobs, everything else derived. **Anything not on the reference below does not exist.** The system is a closed vocabulary: a `--ads-*` custom property or an `ads-*` class. There is no utility layer, no arbitrary-value syntax and no `style=` attribute, and `abilian-ds lint` fails on all three. **Knobs are the overridable surface; everything else derives from them.** Set `--ads-brand` and the hover, active, tint, border and foreground shades follow. Set `--ads-space-scale` and every padding, gap, margin and control height follows. Override a derived token only when you mean to break that link. **Never write a `dark:` variant.** Every colour holds both themes in one value, resolved by `light-dark()` against `color-scheme`. There is no second styling pass to get wrong. Missing a value you need? That is a signal to add a token, not to reach for a literal. Commands: `abilian-ds sync` vendors the stylesheet and macros into a project, `abilian-ds lint` checks templates against the vocabulary, `abilian-ds tokens` regenerates the reference. Paths live in `[tool.abilian-ds]` in `pyproject.toml`, so they take no flags. ## Home - [Overview](https://ads.lab.abilian.com/): Abilian Design System styles Abilian's business applications, built on Litestar and Jinja with plain CSS. A small set of knobs is the whole overridable surface; everything else is derived from them. - [About](https://ads.lab.abilian.com/about/): Abilian builds and maintains a range of business applications. They share a server stack and share nothing visually: each one accumulated a Bootstrap fork, spacing habits and an idea of what a "card" is, all of them different. The cost is that a fix in one is a fix in one. A developer moving between them starts over. ## Getting started - [Install and adopt](https://ads.lab.abilian.com/getting-started/): It needs Python 3.11 or later (situ needs 3.12). The package ships the stylesheet, the application shell, the Jinja macros, the linter and the token reference. It has no front-end toolchain and does not want one. - [Your first page](https://ads.lab.abilian.com/getting-started/first-page/): A page extends the packaged shell and fills its blocks. This walks through one, using only classes from the reference. - [Theming it](https://ads.lab.abilian.com/getting-started/theming/): Everything visual comes from the knobs. Override them on :root, after the stylesheet, and the rest of the system follows. Knobs and derivation explains why that works and where each one reaches. ## Guides - [Knobs and derivation](https://ads.lab.abilian.com/guides/knobs/): How to set them is in Theming it. This page is why it works. - [Layout primitives](https://ads.lab.abilian.com/guides/layout/): Ten primitives compose almost every page, plus a handful of one-line helpers. They are unopinionated about what they contain and are meant to be put on a component: - [Application shells](https://ads.lab.abilian.com/guides/shells/): The shell is the frame around every page: skip link, sidebar, top bar, page header, content. It ships as a template, ads/shell.html, vendored by abilian-ds sync, and your pages extend it. The class names, their nesting and the four layouts are the part of a design system hardest to keep in step across applications, which is why they ship packaged. - [Forms](https://ads.lab.abilian.com/guides/forms/): Business applications are mostly forms and tables. This is the first half; Data and lists is the second. - [Data and lists](https://ads.lab.abilian.com/guides/data/): This page covers the second half of a business application, after Forms. - [Accessibility](https://ads.lab.abilian.com/guides/accessibility/): Accessibility claims here need tests. Everything below is swept across all routes of the reference application on each run. - [Dark mode](https://ads.lab.abilian.com/guides/dark-mode/): There is no dark mode to implement. Each colour in the system holds both themes in one value: - [Using situ](https://ads.lab.abilian.com/guides/situ/): situ compiles a Python component into a JavaScript island, so interactive state can be written once, in Python, and sited explicitly: Local (client only), Url (shareable, server re-renders), Server (a command), Synced. ## Developers - [Architecture](https://ads.lab.abilian.com/developers/architecture/): ads.css is the only place the order is written down. That order is the cascade: - [The linter](https://ads.lab.abilian.com/developers/linter/): The linter is the contract. The documents describe it; it decides. The project has a standing rule: - [Calibration](https://ads.lab.abilian.com/developers/calibration/): Tabler sets the taste and we implement it. Calibration is how we know the two still agree. - [Testing](https://ads.lab.abilian.com/developers/testing/): The project has three suites and a calibration run. - [Contributing](https://ads.lab.abilian.com/developers/contributing/): Ask first whether it can be derived. If two values must move together, one should be computed from the other. The architecture is built on that rule. ## Reference - [Knobs](https://ads.lab.abilian.com/reference/knobs/): The overridable surface has 31 values, each a single number or colour. Defaults are Tabler's measured values, so a project that overrides nothing looks like Tabler, except --ads-contrast, which defaults to a palette that meets WCAG AA. - [Derived tokens](https://ads.lab.abilian.com/reference/tokens/): These 100 values are computed from the knobs. Do not override them: overriding one breaks the link that keeps the system coherent. They are listed so you can read them and check whether the value you need already exists before adding one. - [Components](https://ads.lab.abilian.com/reference/components/): The stylesheet defines 276 classes, grouped here by the part file that defines each. A modifier (--sm) and an element (body) are listed under the block they belong to. - [Jinja macros](https://ads.lab.abilian.com/reference/macros/): abilian-ds sync vendors them into templates/ads/. The navigation macros, menu() and item() in ads/nav.html, are documented with the shell that uses them: Application shells. - [Command line](https://ads.lab.abilian.com/reference/cli/): Paths come from [tool.abilian-ds] in pyproject.toml, so in a configured project the commands take no flags.