Repository navigation
ADR 0002
Status: accepted · Built: planned · Date: 2026-11-18 · Superseded by: 0005, 0008, 0010
Decision only; the package skeleton and builds land in the foundation PR.
Spotstrap's consumers differ in what they can take in:
- Projects on Tailwind v4 with
@tailwindcss/vite(spotcraft, lifts and bars on the web, sokobanko, tagtape, vinskiano) can compile Tailwind source. - The kodentuzo and librevitalis websites have no Tailwind and a CSP of
script-src 'none'. They can only take a plain CSS file. - The lifts and bars apps are React Native with Uniwind. Uniwind reads Tailwind v4 CSS,
including
@utility, but React Native has no attribute selectors, pseudo-classes or pseudo-elements, so state (pressed, checked, open, invalid) can't be styled from CSS selectors there. - Brand colors are also needed outside CSS: meta tags, favicons, manifests, canvas code.
-
One package,
spotstrap, public on npm, MIT. Its exports:Export What For spotstrap/tailwind.cssTailwind v4 source: tokens, base layer, @utilityclassesProjects with Tailwind spotstrap/spotstrap.cssPrebuilt CSS, every class, no theme Sites without Tailwind spotstrap/themes/<name>.cssOne theme: the neutral one and a preset per brand Both spotstrap/tokens.jsonResolved token values per theme and mode Meta tags, icons, canvas spotstrap/recipesTS class recipes keyed by state props React Native (Uniwind) spotstrap/jsOptional behavior for plain HTML (ADR 0004) Sites without a framework -
Classes are written once, as Tailwind
@utilityin the source. The prebuilt CSS and the recipes are generated from it at build time, never edited by hand. -
Brand presets ship in the package, one per current look (kodentuzo, librevitalis, librelifts, spotcraft, sokobanko, tagtape, vinskiano), plus a neutral default.
-
Releases are
vX.Y.Ztags onmain, published by CI with npm trusted publishing and provenance. The version follows SemVer; the public API is the export paths, class names, token names and recipe signatures.
- Plain sites use spotstrap like Bootstrap: one
<link>to the CSS and one to a theme. - Tailwind projects get only the classes they use, and can mix in utilities.
- Renaming a class, token or export is a breaking change.
- The build has three outputs to keep in step with the source; a test checks they match.
Published from docs/. Edit the files there; changes here are overwritten.