Appearance
FAQ
General
Is AdminVora a JavaScript framework?
No. It is a UI layer that enhances markup your backend or framework already produced. There is no virtual DOM, no router, no state management for your data. It works identically in a Blade template, a React tree, and a static HTML file.
Do I need Node.js?
Only if you want to customise the SCSS or build from source. To use the compiled dist/ build, copy the directory and write HTML.
Can I use it with Tailwind?
Technically yes, but you would be paying for two design systems. AdminVora's value is the token system and the component layer; Tailwind's is utility-first authoring. If you want Tailwind, use a Tailwind-based template.
Which CSS framework is this built on?
None. The component layer is an independent .av-* system compiled from src/scss/ — no Bootstrap, no Tailwind, no utility layer. The 1.0.0 specification called for Bootstrap 5.3 compiled from source and that plan was dropped.
The practical consequence for a backend developer, which is the reason the question gets asked: you are not reusing framework knowledge here, but you are also not composing pages out of utility classes in the markup. A page is named blocks — .av-card, .av-table, .av-btn — and the design decisions stay in the stylesheet where npm run lint:css can hold them to the token scale.
Is it accessible?
WCAG 2.2 Level AA, verified per release by automated axe-core runs plus a manual screen-reader audit. A VPAT is published with each minor release. See Accessibility.
How big is it?
Performance lists the measured sizes. The runtime is the same size on every page, including the login screen, because it is one unminified file with no build step. There is no trimmed build. What is deferred is the expensive part: the ten vendored libraries are dynamic-imported on first use, so a page with no chart never downloads ApexCharts. See Performance.
Customisation
How do I change the brand colour?
Pick one of the shipped presets and it is an attribute:
html
<html data-av-preset="oxford">For your own brand, override the ramp in a stylesheet loaded after tokens.css:
css
:root {
--av-primary-500: oklch(63% 0.19 340);
--av-primary-600: oklch(55% 0.20 340);
--av-primary-700: oklch(47% 0.18 340);
}Everything in the product paints through those, so contrast, dark mode, focus rings and chart series all follow. For the greys to pick up a matching tint as well, change the hue and chroma in tools/build-tokens.mjs and run npm run tokens — the generator writes all eleven steps of every ramp consistently, which is the bookkeeping you do not want to do by hand. See Color System.
Can I match our exact brand hex?
Yes, with a caveat. Convert your hex to OKLCH, take the hue and chroma, and let the generator build the ramp. Do not paste your brand hex directly into step 600 — brands rarely pick colours that meet 4.5:1 contrast. If legal requires the exact hex, use it for large surfaces and let the generated step 600 handle small text and controls.
How do I make it smaller?
Mostly you do not have to. The complete stylesheet is small (see Performance), and the heavy third-party libraries lazy-load on first use — a page with no chart never downloads ApexCharts, with no configuration from you.
Beyond that: serve adminvora.min.css rather than adminvora.css, and delete the @use lines you do not need from src/scss/adminvora.scss before running npm run build:css. There is no SCSS configuration map and no selective-compilation flag; that promise was withdrawn because it had no implementation behind it.
Full guide: Performance.
Can I use only the CSS, or only the JS?
Yes, both directions. The CSS works with no JavaScript for everything except behaviour that genuinely requires it. The runtime works with your own CSS if you want to keep only the module system.
Can I use this alongside Bootstrap, Tailwind or my existing stylesheet?
Yes, and the naming is what makes it safe: every class this build defines is .av--prefixed, and every rule sits inside a cascade layer. An unlayered stylesheet of your own therefore beats AdminVora wherever the two ever meet, rather than the two fighting on specificity — so adding AdminVora to a page that already has a framework does not restyle what is already there.
The one attribute that is deliberately not ours is data-bs-theme, the colour-mode switch. It carries Bootstrap's prefix on purpose, so a project already using Bootstrap 5.3's colour modes can adopt this theme engine without changing the attribute it already sets.
How do I add my own component?
By hand — there is no generator. Write the partial, register it with a @use line in src/scss/adminvora.scss, and add a row to the component index; the full sequence is under Adding a component.
Technical
Why no CDN?
Six reasons, all of them real: CSP compliance, GDPR (the German Google Fonts rulings), air-gapped enterprise deployments, CDN outages, supply-chain attacks (Polyfill.io, 2024), and the fact that cross-origin cache partitioning has eliminated the only performance argument for CDNs. See Asset Vendoring.
Why OKLCH instead of hex?
Because equal lightness numbers in HSL do not produce equal perceived lightness. OKLCH means step 600 clears 4.5:1 on white for every hue automatically, color-mix() never produces mud, and changing one hue value rebrands the system without breaking contrast. See Color System.
Why is the boot script inline?
Any other approach produces a visible flash of the wrong theme. An external or deferred script runs after the first paint. The cost is 0.4 ms of parser-blocking execution. See Theme Engine.
Does it work with a strict CSP?
Yes, including require-trusted-types-for 'script'. The only inline script is the boot script, which takes a nonce. No unsafe-inline, no unsafe-eval, no external origins. See Security.
Does it collect any data?
No. No telemetry, no analytics, no external requests, no cookies. One localStorage key for theme preferences. This is what makes it deployable without a DPIA or a cookie banner.
Does it support SSR?
Yes. It is designed server-rendered-first. The boot script handles the theme; DOM-touching code is guarded. See Next.js & Nuxt.
Does it work with Turbo / htmx / Livewire?
Yes, with no adapter. A MutationObserver initialises swapped-in markup containing data-av-* and destroys instances on removed elements.
Migration
I am on Bootstrap already. How hard is this?
Two stylesheets, side by side. AdminVora does not compile or replace Bootstrap — keep loading yours, and your existing classes keep working untouched, because nothing here defines a name outside .av-*. Add the shell markup, add the boot script, and adopt .av-* components page by page.
What that costs is honest to state: for as long as both are loaded you are shipping two design systems, and the two will not agree on radii, shadows or spacing until you finish. The pages you have converted are the ones that look like this product.
The one place they meet on purpose is data-bs-theme: this build reads Bootstrap's own colour-mode attribute, so a project that already toggles it gets both switching together.
I am on Bootstrap 4, or on jQuery plugins.
The version does not matter to AdminVora, since it does not compile Bootstrap at all — but the runtime here has no jQuery and none of the ten vendored libraries need it. A jQuery plugin you rely on continues to work; it simply has no counterpart in this build to migrate onto.
I have a jQuery-based template.
AdminVora contains no jQuery and offers no adapter that would add it. Plan to remove jQuery — it is 88 KB on every page for functionality the platform now provides natively.
I use DataTables everywhere.
There is no adapter, and DataTables is not vendored. Your screens become the built-in grid, which enhances the server-rendered table rather than rendering rows itself; most of the mapping is markup rather than configuration. The table is in Data Grids.
Will upgrading break my customisations?
Not within a major version. av-* classes, --av-* properties, data-av-* attributes, and the AdminVora.* API are semver-protected. Every major release ships a migration guide and a codemod.
Licensing
What licence?
Commercial. Five tiers — see License & Attribution.
Can I use it in a client project?
Yes, with a Regular or Extended licence, depending on whether the end product is sold to its users.
Can I use it in a SaaS product?
Yes, with an Extended licence.
Can I use it in multiple projects?
One licence per application. The Plus tiers cover five; an OEM licence covers unlimited.
Can I resell it?
No. You may not redistribute AdminVora as a template, theme, or component library, whether modified or not. You may include it as part of a functioning application you built.
Is there an open-source version?
No. The vendored third-party libraries are all permissively licensed and remain so — see NOTICE.md. AdminVora's own source is commercial.
Do I get updates?
12 months of updates and support with every licence. Renewal is optional; the version you have keeps working indefinitely.
Can I get the source?
Yes. Every licence includes the full source: SCSS, JS, tokens, HTML templates, and build tooling. There is no minified-only tier.
Support
How do I report a bug?
GitHub Issues with a minimal reproduction.
How do I report an accessibility problem?
a11y@creativeigniter.com. Treated as P1 — 2-day response target, fixed in the next patch.
How do I report a security vulnerability?
security@creativeigniter.com. Never open a public issue. 48-hour acknowledgement, 7 days for a critical fix. A PGP key is at /.well-known/security.txt.
Is there commercial support?
Yes — priority support, custom development, and design services. support@creativeigniter.com.
Where do I ask a question?
Design
Why does it look so plain?
Deliberately. It is designed for the eighth hour of use, not for a marketplace thumbnail. Colour is spent on things that need attention; everything else is neutral. Gradients, glass, and glows exist as opt-in utilities. See Design Principles.
Can I make it look more like [popular template]?
Yes — that is what the token system is for. Increase --av-radius-scale, raise the shadow ladder, enable gradients, and add .av-glass where appropriate. Roughly 20 token values separate "restrained" from "expressive".
Why are a preset and a style separate things?
Because a theme should differ in how it is built, not only in its button colour. A preset is colour: the palette, the greys, the canvas and the rail. A style is construction: surface material, shadows, shapes, heading face, KPI tiles and chart shapes. Each preset wears one style by default, so it reads as a whole personality, and data-av-style puts any palette in any style. Every preset × mode combination is snapshot-tested and contrast-tested, and the token build refuses two presets that look too alike. The retired names still render, mapped to their replacements.
Why no dark-only or light-only mode?
Both are supported — set mode: 'light' or 'dark' and never expose the toggle. What is not supported is building for only one, because the token system makes supporting both free.
Is there a Figma file?
Yes. tokens/figma-variables.json imports into Figma Variables via the Tokens Studio plugin, and values round-trip back into the repository as a reviewable pull request.
Comparisons
How does this compare to a typical marketplace admin template?
| Typical | AdminVora | |
|---|---|---|
| jQuery | Usually required | None |
| CDN requests | 20–40 | 0 |
| JS on every page | 420–780 KB | 38–190 KB, page-dependent |
| Rebranding | Find-and-replace across a 2 MB CSS file | One token value |
| Dark mode | A second stylesheet, often incomplete | A token flip |
| WCAG conformance | Rarely claimed, rarely tested | AA, verified per release |
| RTL | A mirrored stylesheet, often stale | Free via logical properties |
| Source | Sometimes minified-only | Always full source |
How does this compare to building our own design system?
Building your own is the right call if your product's visual identity is a competitive advantage and you have a dedicated design-systems team. For everyone else, AdminVora is roughly 18 months of that team's output, already tested across 9 themes, 2 colour modes, 2 directions, 3 densities, 6 browsers, and 5 screen readers.
How does this compare to a component library like Radix or shadcn/ui?
Different scope. Those are headless primitives for React applications. AdminVora is a complete, styled, framework-agnostic system including layouts, pages, and a build pipeline. If you are building a React-only product and want full control over styling, use those. If you want a working admin panel next week across any stack, use this.
Read next: License & Attribution.