Appearance
Build Pipeline
Every stage is a plain Node script in tools/. There is no bundler: the stylesheet is compiled by Sass, the runtime is one hand-written file, and the rest is assembly.
Overview
tools/build-tokens.mjs ─────────────────────► src/css/tokens.css
src/scss/** ──► tools/build-css.mjs (Sass) ─► src/css/adminvora.css (+ .min.css)
html/_src + _partials ──► tools/build-html.mjs ──► html/pages/, html/_qa/, index.html
node_modules ──► tools/vendor-sync.mjs ─────► src/vendor/ (SHA-256 pinned)
src/css + src/js + src/vendor ──► tools/build-dist.mjs ──────► dist/
html/pages + dist ──► tools/build-html-dist.mjs ─────────────► html-dist/
docs/ ──► VitePress (tools/build-docs.mjs) ──────────────────► docs-dist/
dist + html-dist + docs ──► tools/pack.mjs ──────────────────► dist-package/| Command | Stage |
|---|---|
npm run tokens | Generates src/css/tokens.css from the ramp tables in tools/build-tokens.mjs, PRESETS in tools/presets.mjs and STYLES in tools/styles.mjs |
npm run build:css | Compiles src/scss/adminvora.scss with Sass, expanded and minified |
npm run build:html | Assembles the demo pages from page sources and partials |
npm run build | All three, plus check:tokens |
npm run vendor | Copies the pinned third-party files into src/vendor/ and verifies their checksums |
npm run build:dist | Assembles the redistributable bundle |
npm run build:html-dist | Rewrites the demo pages to run from inside html-dist/ with nothing fetched from outside it |
Every output is gitignored. npm run setup runs vendor, images and build after a fresh clone.
The HTML build
tools/build-html.mjs is a small template engine, deliberately tiny:
| Syntax | Meaning |
|---|---|
{{> name }} | Include html/_partials/name.html |
{{ key }} | A value from the page's JSON header (title, nav, …), or version from package.json |
{{ root }} | ../ repeated to the output depth, so relative links work from any folder |
{{ icon name }} | Inline the SVG from html/_icons/name.svg |
{{# key }}…{{/ key }} / {{^ key }}…{{/ key }} | Emit the block only when key is truthy / falsy |
Each file in html/_src/ starts with a JSON header that names its output path and the sidebar row it lights:
html
<!--av { "title": "Orders", "out": "pages/apps/orders.html", "nav": "orders" } av-->
{{> shell-open }}
…
{{> shell-close }}The build fails on a nav, sub or group value that no sidebar row reads.
How the stylesheet is configured
There is no src/scss/_config.scss, no !default declaration anywhere under src/scss/, and no @use 'adminvora' with (…) surface. Earlier versions of this page printed twenty-seven $av-… variables as though there were; none of them existed, and npm run check:scss-api now fails the build on any $av-… name in this documentation that src/scss/ does not declare.
The knobs are real, but they are custom properties and document attributes, not SCSS variables — which is a deliberate consequence of the theme engine: everything selectable at runtime has to be selectable without a rebuild, and a value that is compiled in cannot be one of them. Three tiers, cheapest first.
1. Attributes on <html> — no build at all
html
<html lang="en"
data-bs-theme="dark"
data-av-preset="pine"
data-av-layout="horizontal"
data-av-density="compact"
data-av-radius="sharp"
data-av-contrast="high"
data-av-motion="reduced"
dir="rtl">Every preset, style, layout, density and radius step is selected this way. The customizer writes exactly these, and the inline boot script restores them before first paint. This is the tier most "how do I change the brand colour" questions actually want.
2. Custom-property overrides — a stylesheet, no rebuild
Load your own sheet after tokens.css and set what you want. Every value the product paints with resolves through one of these, so an override reaches the whole product rather than the components you remembered:
css
/* after tokens.css, before or after adminvora.css — @layer tokens is the
lowest layer, so an unlayered rule of your own wins either way */
:root {
--av-radius-scale: 0; /* the whole radius ladder is a calc() off this */
--av-font-sans: 'Söhne', system-ui, sans-serif;
--av-primary-500: oklch(63% 0.19 340);
--av-primary-600: oklch(55% 0.20 340);
--av-primary-700: oklch(47% 0.18 340);
}--av-radius-scale is the one true scale knob: --av-radius-xs through --av-radius-3xl are each a calc() against it, so 0 squares every corner in the product from one declaration. There is no --av-space-scale or --av-type-scale to match it — the spacing and type ladders are literal values, and changing them means changing the tokens.
3. Rebuild the tokens or the stylesheet
tools/build-tokens.mjs holds the lightness and chroma tables and the ramp function, and tools/presets.mjs holds the preset definitions and tools/styles.mjs the UI styles' tokens. It is a plain script with no configuration file, so a brand palette is a change to it followed by npm run tokens. src/scss/adminvora.scss is a flat list of @use lines with no conditionals; dropping a component from the build means deleting its line and running npm run build:css. Both are crude next to a with (…) map — and both are honest about what they are, which a configuration surface that does not exist is not.
Shipping the SCSS source to customers makes the partial layout, the @use order, the layer order in _layers.scss and the abstracts/ mixin signatures a public API. The $av- namespace is currently empty; the only SCSS variables in the product are the status-role lists in abstracts/_variants.scss.
Size, measured
The complete stylesheet, every preset and every layout included, with no configuration. The measured sizes are on Performance.
Build outputs
dist/
├── README.md, LICENSE.md, NOTICE.md
├── css/
│ ├── adminvora.css tokens + components, one file
│ ├── adminvora.min.css
│ └── tokens.css tokens only, for regenerating against a custom palette
├── js/adminvora.js the runtime
├── vendor/ the ten libraries, lazy-loaded from js/../vendor/
├── scss/ the SCSS source
└── img/dist/README.md is written by build:dist and is the authority for this tree; npm run check:bundle fails if a docs sample links a file the bundle does not contain.
Read next: Asset Vendoring.