@rathnasgala2/theme-amaze
v4.2.1
Published
The Amaze presentation theme (editorial magazine: serif display type, generous measure, magenta accent) for Galascribe portable publications (`@rathnasgala2/template@^4.4.0`). A build uses it only when a publication's `appearance.theme` names it. This pac
Readme
@rathnasgala2/theme-amaze
The Amaze presentation theme (editorial magazine: serif display type, generous measure, magenta accent)
for Galascribe portable publications (@rathnasgala2/template@^4.4.0). A build uses it only when a publication's appearance.theme
names it. This package is a closed, passive file set: JSON and CSS
only, no JavaScript, no build step, no runtime dependency, no lifecycle
script. A missing selected theme fails a build rather than silently changing
appearance.
In generation 4 the template owns page layout and component structure. This theme selects the Editorial composition and supplies its established 116-token Amaze palette plus a small amount of skin CSS.
Composition
theme.json embeds the complete generation-4 Editorial composition:
- magazine home
- editorial article
- portrait author page
- row listings
- masthead header
- expanded footer
- landscape media
- comfortable density
Files
package.json: exactlyname,version,license,repository,files.theme.json: validated againsturn:gala:schema:theme-contract:2.0.0. It carries the contract-4 identity and Editorial composition,templateRange(^4.4.0), the stylesheet/layer/hook projection, both palettes for all 116 tokens, asset digests, size budgets, and the generation-4stylingContractDigest.tokens.css: generated fromtheme.jsonbytokens:generate. Never edit it by hand;tokens:checkfails if it drifts fromtheme.json.components.css: a small skin layer (cards, chips, avatars, strong text) that uses tokens only.print.css: print rules.LICENSE,README.md.
Token values are the owner-approved Amaze preview values; theme.json is
their only source (edit tokens there, then run tokens:generate).
Commands
Node 24.18.0 (see .nvmrc). tooling/ is private and never packed; every
gate lives in @rathnasgala2/theme-tooling and is reached through
tooling/run.mjs.
npm --prefix ../theme-tooling run vendor:check
npm --prefix ../theme-tooling ci
GALA_THEME_TOOLING_DIR=../../theme-tooling npm --prefix tooling run tokens:generate
GALA_THEME_TOOLING_DIR=../../theme-tooling npm --prefix tooling run digest:generate
GALA_THEME_TOOLING_DIR=../../theme-tooling npm --prefix tooling run verifyRe-run digest:generate after editing theme.json, tokens.css,
components.css or print.css. It recomputes asset digests and the chain
fixtureDigest, evidenceDigest, integrity.
Only theme tooling is consumed from an explicit source checkout. Its exact
Schema 3.16.0 and Template 4.4.0 dev dependencies install from the npm
registry, and Schema and Template resolve from those installed packages.
GALA_SCHEMA_DIR and GALA_TEMPLATE_DIR are development overrides, not part
of this flow. None is a runtime dependency, and these commands do not publish
the package.
Rules
CSS is limited to the root scope and the template's published styling hooks,
contains no @import, external url(), outline: none or script
constructs, and every stylesheet is one @layer block matching theme.json.
Contrast (WCAG 2.2 AA) is checked for both palettes by contrast:check.
The shared tooling README describes each gate.
