Skip to content

The SCSS Source ​

The compiled stylesheet is not the only thing you get. dist/scss/ is the source it was built from, and this page is the promise that comes with it.


Why it ships ​

Overriding a compiled stylesheet sounds like the cheap option and is the expensive one here. Every rule AdminVora writes is inside a cascade layer, and unlayered author CSS beats every layer, whatever the layer order says. So your first override wins unconditionally — and so does your second, and the one a colleague adds next year. The layer order stops meaning anything the moment you start writing rules outside it, and the 0-3-0 specificity ceiling the whole codebase is built to respect becomes a rule only the vendor follows.

Recompiling puts your changes back inside the cascade the product was designed with. That is worth more than a smaller download, so the source ships.


What you get ​

dist/scss/
├── adminvora.scss      the entry — one @use per partial, in cascade-relevant order
├── _layers.scss        the @layer declaration, and nothing else
├── abstracts/          compile-time only, emits no CSS
├── base/               @font-face rules, element selectors, reset and typography
├── layout/             the shell regions — sidebar, topbar, footer, content, public pages
├── components/         one BEM block per file
├── plugins/            restyling for the vendored libraries
├── styles/             the UI styles, one partial each
└── utilities/          single-purpose classes
DirectoryPartialsHolds
abstracts/3Mixins, variables and the style guard. Emits no CSS.
base/3_fonts, _reset, _base
layout/8The shell regions
components/111One av-* block per file
plugins/7One per vendored library that needs restyling
styles/13_bento, _blueprint, _bold, _brutal, _clean, _duotone, _editorial, _flat, _glass, _luxe, _organic, _soft, _tactile
utilities/8_a11y, _demo, _depth, _grid, _hidden, _motion, _print, _spacing

Every partial in the tree is reachable from adminvora.scss. There is no dead file and no curated "public subset" — a subset would be a second list to keep in step with the @use block, and this codebase has shipped that defect enough times to stop volunteering for it.


Compiling it ​

bash
npm install sass
npx sass scss/adminvora.scss css/adminvora.css --style=expanded

That reproduces dist/css/adminvora.css exactly, minus the banner the bundler adds. npm run check:scss-source asserts it byte-for-byte on every lint run, from a relocated copy of the tree — so a partial that only compiles because of where it sits in this repository fails here rather than in your project.

Tokens are not in that compile. css/tokens.css is generated separately by tools/build-tokens.mjs and must still be linked first. The SCSS reads var(--av-…) throughout and defines none of it; compile the SCSS alone and you get a stylesheet whose every colour, space and radius is an unresolved custom property.


There are no !default variables ​

This is the part that surprises people, so it is stated plainly rather than discovered.

There is not one !default declaration anywhere in the tree, so @use 'adminvora' with (…) has no parameters to accept and will fail rather than silently ignore you. No example of that form appears anywhere in this documentation, and npm run check:scss-api fails the build if one is added — naming a Sass variable a customer cannot set is a configuration API that does not exist.

That is deliberate. Colour, spacing, radius, density, depth and motion are custom properties, not Sass values — which is exactly what lets the Customizer change all of them at runtime, in the browser, without a recompile. A Sass variable is decided at build time and can never do that.

Retheming means overriding tokens. See Theme Engine for the attribute axes and Theme Presets for how a preset is defined.


The public API, and its limits ​

Shipping the source makes four things public. A minor release will not break them:

  1. The layer order. Declared once, in _layers.scss:

    scss
    @layer reset, base, components, plugins, styles, utilities;

    Five layers. There is no bootstrap layer because there is no Bootstrap, no tokens layer because tokens are a separate stylesheet, and no layout layer because the shell partials put their rules in components. CSS Architecture explains each.

  2. The entry point. adminvora.scss stays the entry, and _layers.scss stays the first thing it uses. Compile anything else and the layer order is undefined.

  3. The directory contract. A partial's directory says what it may contain — abstracts/ emits no CSS, components/ holds one block per file, utilities/ holds single-purpose classes. A partial does not move between directories in a minor release.

  4. The abstracts/ signatures. These are the only compile-time API, and they are small:

    FromSignatureWhat it is
    abstracts/motion@mixin stillWraps content in both reduced-motion triggers — the OS preference and the product's own switch
    abstracts/variants@mixin soft-surface($role, $bordered: true)A low-emphasis surface for one status role
    abstracts/variants$statussuccess, warning, danger, info
    abstracts/variants$status-with-neutralsuccess, warning, danger, info, neutral
    abstracts/variants$status-with-primaryprimary, success, warning, danger, info
    abstracts/variants$status-allprimary, success, warning, danger, info, neutral
    abstracts/styles@mixin style($name, $extra: '')Rules that apply while <html> wears that UI style; $extra adds a compound to <html>, such as :not([data-av-depth="plain"])
    abstracts/styles@mixin vivid-tilesThe KPI tiles filled with their own colour, white ink by construction
    abstracts/styles$style-presets( clean: (aurora, material), editorial: (heritage, paper, sand, midnight), soft: (frost, sage), tactile: (pine, tidewater, ocean, harbour), bold: (jewel), glass: (oxford, neon, grape), brutal: (granite, graphite, mono, github, carbon), flat: (urbanite, arctic, slate, nord), luxe: (storm), organic: (matsuba, evergreen, forest), blueprint: (deepsea), duotone: (catawba), bento: (kuri, terracotta, ember, crimson, forge, noir), )

    A variable's third column is its value, checked against the source. A mixin's is prose.

    check:scss-source holds this table to the source in both directions: a mixin added to abstracts/ without a row here fails the build, because an undocumented helper that customers can see is public API whether or not anyone meant it to be.

What is not public ​

  • A component partial's internals. The selectors inside components/_card.scss are ours to change; .av-card as a class is documented in the component index and that is the contract, not the partial's private structure.
  • @use order within a layer. Two rules of equal specificity in one layer resolve by source order, and that order can change when a partial is added. If a rule of yours must win, give it real specificity rather than a position.
  • utilities/_demo.scss. It styles the reference pages in this repository. It ships because the tree ships whole, not because anything in it is supported.
  • The compiled CSS's rule order. It is an output.

What this does not include ​

There is no Vite pipeline, no dist/types/, no per-module CSS chunk and no source map in the bundle. dist/scss/ is the source and dist/css/adminvora.css is the output; there is nothing between them but sass.

Documentation for @creativeigniter/adminvora