saasaloy 0.7.0 → 0.8.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -2
- package/dist/index.js +222 -79
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
- package/schemas/registry-item.schema.json +5 -2
- package/templates/base/AGENTS.md +80 -470
- package/templates/base/_agents/skills/saasaloy-design/SKILL.md +33 -22
- package/templates/base/_agents/skills/saasaloy-landing-copy/SKILL.md +17 -2
- package/templates/base/_agents/skills/saasaloy-setup/SKILL.md +38 -7
- package/templates/base/_saasaloy-base.json +1 -0
- package/templates/base/apps/web/DESIGN.md +4 -4
- package/templates/base/apps/web/astro.config.mjs +2 -1
- package/templates/base/apps/web/src/layouts/Layout.astro +2 -2
- package/templates/base/oxlint.config.mjs +14 -10
- package/templates/base/package.json +1 -0
- package/templates/base/packages/env/src/define.test.ts +33 -0
- package/templates/base/packages/ui/AGENTS.md +159 -0
- package/templates/base/packages/ui/CLAUDE.md +1 -0
- package/templates/base/packages/ui/components.json +1 -1
- package/templates/base/packages/ui/src/containers/README.md +4 -4
- package/templates/base/packages/ui/src/styles/brand.css +145 -0
- package/templates/base/packages/ui/src/styles/globals.css +6 -7
- package/templates/base/packages/ui/src/styles/web.css +7 -139
- package/templates/base/turbo.json +1 -0
|
@@ -0,0 +1,159 @@
|
|
|
1
|
+
# `@repo/ui` — the design layer
|
|
2
|
+
|
|
3
|
+
This file holds the rules for `packages/ui`: the theme, the primitives, the blocks, the containers and the copy. The root `AGENTS.md` holds the rules for the whole repository, and they apply here too. Read this file before you add or change UI in any app.
|
|
4
|
+
|
|
5
|
+
## What lives here
|
|
6
|
+
|
|
7
|
+
`packages/ui` owns the design layer: the Tailwind 4 theme in `src/styles/`, the `cn()` helper and the client-state stores in `src/lib/`, the vendored [shadcn](https://ui.shadcn.com) primitives in `src/components/`, the **blocks** in `src/blocks/`, the shells and layouts in `src/containers/`, and the copy in `src/content/`.
|
|
8
|
+
|
|
9
|
+
Those layer folders are the whole top level of `src/`: `assets` (images, SVGs and icons, added when the first one arrives), `blocks`, `components`, `containers`, `content`, `lib` and `styles`. Do not add an app folder such as `src/admin/` or `src/web/` beside them. When one app needs its own files inside a layer, give that layer a child folder (`blocks/admin/`, `components/shared/`).
|
|
10
|
+
|
|
11
|
+
## The theme
|
|
12
|
+
|
|
13
|
+
The theme is one shared file, one brand file, and one stylesheet per app:
|
|
14
|
+
|
|
15
|
+
- **`src/styles/globals.css`** is the shared layer: the Tailwind imports, the `@source` globs and the base layer. It holds no token values, and no app imports it directly.
|
|
16
|
+
- **`src/styles/brand.css`** is the product's theme: the `dark` custom variant, the `:root` and `.dark` token values, the `@theme inline` colour mapping and the radius scale. It imports `globals.css`, so an app stylesheet that imports `brand.css` gets the whole theme. `components.json` points here, so a shadcn preset lands here.
|
|
17
|
+
- **`src/styles/web.css`** is the web app's stylesheet. It imports `brand.css` and adds the landing page's layout, type and motion utilities, which a preset leaves alone. `apps/web` pulls it in once, through the shared layout that imports `@repo/ui/styles/web.css`.
|
|
18
|
+
- **`src/styles/admin.css`** is the admin app's theme, written by `saasaloy add admin`. It imports `globals.css` and carries its own tokens in the same shape as `brand.css`.
|
|
19
|
+
|
|
20
|
+
Each theme file repeats the `dark` variant and the `@theme inline` mapping on purpose. shadcn merges a preset in place only when the target file itself holds them, and it does not look through an `@import`. Move either one into `globals.css` or `web.css` and a preset appends a duplicate to `brand.css` instead.
|
|
21
|
+
|
|
22
|
+
**Each app has its own `DESIGN.md`, in its own folder.** `apps/web/DESIGN.md` records the tokens in `brand.css`, the landing vocabulary in `web.css` and the rules behind them, and fingerprints `brand.css`. An app that carries its own theme file gets its own `apps/<app>/DESIGN.md`, which fingerprints that file. There is no `DESIGN.md` at the repository root. Read the document for the app you are changing before you add or change UI.
|
|
23
|
+
|
|
24
|
+
With the admin app installed, `apps/admin/DESIGN.md` records the admin tokens in `packages/ui/src/styles/admin.css` and fingerprints that file. A preset never targets `admin.css`; the admin theme changes by hand.
|
|
25
|
+
|
|
26
|
+
## Imports and the folder layout
|
|
27
|
+
|
|
28
|
+
Primitives, blocks and containers are reached by subpath — none is re-exported from the package root, so importing one never drags in the rest. The root export is project-wide constants only (`siteName`, which re-exports `config.app.name`):
|
|
29
|
+
|
|
30
|
+
```ts
|
|
31
|
+
import { siteName } from "@repo/ui";
|
|
32
|
+
import { Button } from "@repo/ui/components/button";
|
|
33
|
+
import { PricingTable } from "@repo/ui/blocks/pricing-table";
|
|
34
|
+
import { landing, ui } from "@repo/ui/content/landing";
|
|
35
|
+
import { cn } from "@repo/ui/lib/utils";
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
**The signed-in apps share their own primitive set.** `saasaloy add shell` writes it into `src/components/shell/`, with its blocks in `src/blocks/shell/`, its shell and layouts in `src/containers/shell/`, and its tokens and motion in `src/styles/shell.css`. `admin` and `app` install `shell` for you. Their code imports only that set, and a lint rule makes a base primitive under `apps/admin/**` or `apps/app/**` an error, because both sets have a `button` and the wrong one renders with no complaint:
|
|
39
|
+
|
|
40
|
+
```ts
|
|
41
|
+
import { Button } from "@repo/ui/components/shell/button";
|
|
42
|
+
import { DataTable } from "@repo/ui/blocks/shell/data-table";
|
|
43
|
+
import { PageHeader } from "@repo/ui/blocks/shell/page-header";
|
|
44
|
+
import { PageLayout } from "@repo/ui/containers/shell/page-layout";
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
The `saasaloy-shell` skill lists the whole set and how a page composes it.
|
|
48
|
+
|
|
49
|
+
**Seven top-level folders, and no app folder at the root of `src/`.** A folder may hold `shell/`, `admin/`, `web/` or `shared/` children where one module owns the files, for example `src/blocks/shell/` or `src/containers/shell/`, which `saasaloy add shell` writes. A project without that module carries none of them.
|
|
50
|
+
|
|
51
|
+
1. **`src/assets/`** holds images, SVGs and icons. The base ships no asset, so the folder does not exist until the first one lands, together with an `assets.d.ts` that types its imports.
|
|
52
|
+
2. **`src/components/`** holds the vendored shadcn primitives, official and custom. No stores, no copy.
|
|
53
|
+
3. **`src/blocks/`** holds compositions of primitives plus copy from the content module. Local state is allowed (an open accordion, a ticking clock). Importing a shared store is forbidden: a block takes its data as props and reports changes through callbacks, so every app can drive the same block from its own data source.
|
|
54
|
+
4. **`src/containers/`** holds the shells and layouts that hold blocks and components on a page: an app shell, a page layout, a page frame. A container takes its data, its links and its callbacks as props. It imports no router and no session, so the app that owns them passes them in.
|
|
55
|
+
5. **`src/content/`** holds copy, in one place for later translation.
|
|
56
|
+
6. **`src/lib/`** holds utilities and the client-state stores.
|
|
57
|
+
7. **`src/styles/`** holds the CSS files with the token variables.
|
|
58
|
+
|
|
59
|
+
**One rule covers the whole package: no IO in `@repo/ui`.** No fetch, no persistence, no auth, no router, in any layer. Client-state stores (nanostores) live in `src/lib/`; the app that owns the data hydrates the store and passes what a block needs as props. When a store-shaped need shows up in a block, move the binding up into the app instead of importing the store in place.
|
|
60
|
+
|
|
61
|
+
## Primitives and presets
|
|
62
|
+
|
|
63
|
+
**Adding a primitive the base doesn't vendor.** `shadcn` is already an exact-pinned dependency of `@repo/ui`, so reach it with `--filter … exec` — that runs in the package directory, where `components.json` lives:
|
|
64
|
+
|
|
65
|
+
```sh
|
|
66
|
+
pnpm --filter @repo/ui exec shadcn add dialog
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
- **Not `pnpm -C packages/ui dlx …`.** `-C` scopes pnpm's own workspace resolution; it does *not* change the directory `dlx` spawns the command in. shadcn then looks for `components.json` wherever your shell happens to be and dies at `Verifying framework`. If you must use `dlx`, pass shadcn's own flag: `--cwd packages/ui`.
|
|
70
|
+
- Never `npx` (see "Never Do" in the root `AGENTS.md`).
|
|
71
|
+
- The CLI writes into `src/components/`. Anything it appends to `package.json` arrives as a range — **re-pin it to an exact version**.
|
|
72
|
+
- **Add the primitive to a `@source` list, or it renders unstyled.** `globals.css` names the components it scans one file at a time, because Tailwind scans content rather than imports and a blanket glob charges every app for every primitive. A primitive the landing page or `src/blocks/` renders gets an `@source "../components/<name>.tsx";` line in `globals.css`; a primitive only one app renders gets its `@source` line in that app's own theme file, the way `src/styles/admin.css` takes the whole directory. Nothing errors when you skip this — the classes just never reach the CSS.
|
|
73
|
+
- `style` is `base-nova` (Base UI) and is fixed at init — the CLI cannot change it later.
|
|
74
|
+
- `rsc` is `false`, so the CLI strips the `"use client"` directive for you. It means nothing in Astro, and the vendored primitives don't carry it.
|
|
75
|
+
|
|
76
|
+
Primitives are source you own. Edit them in place rather than wrapping them.
|
|
77
|
+
|
|
78
|
+
**No UI kit or component library as a dependency.** When a design comes from a kit (Tailark, coss ui, a licensed dashboard kit), copy or rebuild the component into `src/components/` or `src/blocks/` as source this project owns. Do not install the kit's package, and keep no link to its repository for later updates. A copied component changes by hand, like any other file here. The shadcn CLI above is the one sanctioned way to fetch a primitive, because it writes source and leaves no runtime dependency behind.
|
|
79
|
+
|
|
80
|
+
**Swapping the whole theme for a preset.** The token set in `packages/ui/src/styles/brand.css` is shadcn's `neutral` with `cssVariables: true`, and any shadcn **`registry:style`** item is a drop-in replacement for it. The same `--filter … exec` form applies — there is no separate theme command:
|
|
81
|
+
|
|
82
|
+
```sh
|
|
83
|
+
pnpm --filter @repo/ui exec shadcn add https://tweakcn.com/r/themes/modern-minimal.json
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
The CLI merges the preset's `:root`, `.dark` and `@theme inline` blocks **into** the existing ones in `brand.css` and keeps its `@custom-variant dark`, so the hand-written parts in `globals.css` — the `@source` rules and the `@layer base` rules — stay put, the landing utilities in `web.css` stay put, and `components.json` is not touched. The preset reaches the web app only; the admin theme in `admin.css` keeps its own values. It usually *extends* `@theme inline` with mappings the base does not carry (fonts, tracking, shadows); that is expected.
|
|
87
|
+
|
|
88
|
+
Two places to get an item from:
|
|
89
|
+
|
|
90
|
+
1. **[`https://ui.shadcn.com/create`](https://ui.shadcn.com/create)** — first-party. Describe or dial in a theme and it hands you a URL.
|
|
91
|
+
2. **[`https://tweakcn.com`](https://tweakcn.com)** — a much larger preset library, serving items at `https://tweakcn.com/r/themes/<name>.json`.
|
|
92
|
+
|
|
93
|
+
Neither is special: the mechanism is the `registry:style` shape, so any URL that serves one works.
|
|
94
|
+
|
|
95
|
+
**This edits a file the project owns.** `brand.css` is an owned base file: `saasaloy update` never overwrites it, and a later template change to it reaches you only through the merge plan. A swapped theme is yours to maintain, including re-applying anything you had customised in `brand.css` that the preset overwrote. Diff the file after running the command rather than assuming.
|
|
96
|
+
|
|
97
|
+
A preset swap invalidates `apps/web/DESIGN.md`, which records the token values the old theme had. The `saasaloy-design` skill's `theme` flow runs the command above for you and re-derives the contract from the merged result, so prefer it over running the command by hand. Pick one or the other — running both applies the preset twice.
|
|
98
|
+
|
|
99
|
+
Theme switching is unaffected by any of this. It keys off the `.dark` class, which every preset keeps. The web toggle has two states, light and dark: `system` is only the starting state for a visitor who never pressed it, and no press steps back to `system`. Do not give the web toggle a third state or a light/dark/system menu. The signed-in apps are different: the `shell` account menu has a Light / Dark / System submenu, and it keeps it.
|
|
100
|
+
|
|
101
|
+
## Blocks
|
|
102
|
+
|
|
103
|
+
**Blocks — the page-level compositions.** `src/blocks/` holds the thirteen marketing blocks the landing page is built from: `navbar`, `hero`, `logo-cloud`, `pain-points`, `how-it-works`, `feature-grid`, `showcase`, `audience`, `testimonials`, `pricing-table`, `faq`, `cta` and `footer`. They need the landing utilities at the end of `web.css`, from the comment that opens "The landing page's layout" to the `stylelint-enable` line.
|
|
104
|
+
|
|
105
|
+
**The section recipe.** `index.astro` composes the page from explicit imports, one line per section. To remove a section, delete its line and its import, delete its file in `src/blocks/`, and blank its navbar and footer labels in `landing.ts`. To reorder, move the lines. Every block uses the same container (`section-container`, `-narrow`, `-wide`) and spacing (`section-y`) utilities from `src/styles/web.css`, so any order keeps one rhythm. A block sets no width, no section padding and no keyframes of its own; motion comes from the named utilities there (`blur-in`, `beam-in`, `reveal`, `marquee`, `shine-text`, `nav-float`, `hover-lift`), and every one stops under reduced motion.
|
|
106
|
+
|
|
107
|
+
**The logo recipe.** `landing.logos.items[]` is `{ id, name, mark }`. `mark` is a key in `LOGO_MARKS` at the top of `blocks/logo-cloud.tsx`. Paste a customer's SVG there under a kebab-case key with `fill="currentColor"`, then name the key in content. An unknown key renders `name` as a text wordmark.
|
|
108
|
+
|
|
109
|
+
**The production bar.** The page holds to a rubric: no axe violation at WCAG 2.1 AA in either theme, no sideways scroll from 360px up, nothing animating under reduced motion, a skip link to `<main>` on every page, link-preview metadata on `/`, and exactly two islands (`Navbar`, `PricingTable`). Keep each true when you change a block: a new section with state is a third island and needs a reason.
|
|
110
|
+
|
|
111
|
+
The rules below are not stylistic — each one prevents a real failure:
|
|
112
|
+
|
|
113
|
+
- **One block, one file, one component export (plus its prop types).** `pricing-table.tsx` exports `PricingTable` alongside `PricingTier` and `PricingTableProps`, and nothing else — no second component, no default export, no `blocks/index.ts` barrel. Astro gives every `client:*` component its own React root, so a compound primitive (accordion, dialog, dropdown) split across an `.astro` file throws "must be used within" at runtime. Keep the whole composition inside the block.
|
|
114
|
+
- **Props-driven, with every default read from the content module.** Every prop is still optional and still carries a default — but the *words* come from `packages/ui/src/content/landing.ts`, not from the block. `hero.tsx` has `title = landing.hero.title`; `pricing-table.tsx` holds no tier data at all. Keep the props for the cases a page really varies (a second landing page can override any of them); change the copy by editing the content module. See below.
|
|
115
|
+
- **Never pass a component or a function as a prop from `.astro`.** Astro serializes island props, so icons live *inside* the block. Swap one by editing the block.
|
|
116
|
+
- **Semantic kebab-case filenames** (`feature-grid.tsx`), never shadcn's registry-style `{category}-{NN}` numbering — that disambiguates variants in a public registry, and this project has neither.
|
|
117
|
+
- **Static by default.** A block with no state renders to HTML and ships zero JS. Add a client directive only to the block that actually needs the browser, and pick the cheapest one: `client:idle` above the fold, `client:visible` below it. A blanket `client:load` on the page hydrates everything and throws away the reason this is a static site — see `apps/web/src/pages/index.astro` for the worked example.
|
|
118
|
+
- **`theme-toggle` is the exception that proves the rule.** It sits in `src/blocks/` beside the marketing blocks but is chrome, not copy: `navbar.tsx` renders it inside the bar, and it needs **no** client directive of its own despite being interactive. It has no `onClick` and no state — the pre-paint inline script the shared layout emits (`THEME_INIT_SCRIPT`, from `packages/ui/src/lib/theme.ts`) drives every `[data-theme-toggle]` on the page through one delegated listener, and CSS picks the icon off `<html data-theme>`. Move it, restyle it via its `className`, or delete the one line in `navbar.tsx` to drop it. Do **not** "fix" it by adding `client:*` or an `onClick`, and do not paste a second copy of the boot script into a page: any document that renders the block must inline that one constant in its `<head>`, or the control stays hidden.
|
|
119
|
+
- **`error-state` is the only error screen, and every app renders it.** An app that adds a route surface answers a miss with `ErrorState` — `apps/web` through `src/pages/404.astro`, the admin SPA through the root route's `notFoundComponent` and its error boundary, and `apps/api` through `base.notFound(...)`, which answers the same `{ error: { code, message } }` envelope as every other failure. Do **not** write a second error screen in an app: one block means one restyle when the theme moves, and a bespoke copy drifts out of the token vocabulary the day nobody is looking. Change the words in `packages/ui/src/content/errors.ts`, the markup in `packages/ui/src/blocks/error-state.tsx`.
|
|
120
|
+
- **A `prerender = false` page inherits `500.astro`.** `apps/web` registers `@astrojs/cloudflare` while staying on `output: "static"`, so `src/pages/500.astro` is built ahead of time and carries no detail from the failed request. The day a page opts into on-demand rendering, a throw inside it lands on that page for free — nothing to add. Two things move on that day and only that day: `wrangler.jsonc` gains a `main` pointing at the server entry the adapter now writes, and `dist/server` stops being empty. Setting `main` before then breaks the build, which is why the comment in `wrangler.jsonc` says to wait.
|
|
121
|
+
- **A block never reaches the network; the app injects the behaviour.** A block that needs to send something takes a function prop (`onSubmit`) and calls it. It does not import an api package, an http client, or `import.meta.env`. Two reasons, both concrete. `packages/ui` has a `typecheck` script and consumes workspaces as source, so one `import type { AppType } from "@repo/api/client"` here makes `tsc` compile the entire Worker source tree under this package's tsconfig. And a block that hardcodes an endpoint is a block you cannot reuse on a second page. The counterpart lives in the app: a small React file under `apps/web/src/components/` builds the client and passes the function down. Astro serializes island props, so the page renders **that** file, never the block directly.
|
|
122
|
+
- **A link that leaves the site opens a new tab.** Spread `externalLinkProps(href)` from `@repo/ui/lib/external-link` onto the anchor and render `newTabHint(href)` inside it. The href decides: an absolute URL gets `target="_blank"`, `rel="noopener noreferrer"` and a screen-reader hint, and a path or a same-page anchor stays in the tab. Do not write `target="_blank"` by hand.
|
|
123
|
+
- **A value that waits on a request shows a skeleton.** Render the `Skeleton` primitive at the size the value will take until the response arrives, never a blank gap or a spinner. Add it with `pnpm --filter @repo/ui exec shadcn add skeleton` the first time a block needs it.
|
|
124
|
+
- **A block never imports a store either.** Local state is fine; shared state is not. The app-side island reads the store and passes the values and the handlers down, the same pattern it uses for `onSubmit`.
|
|
125
|
+
- **A module's UI arrives here too, and you wire it up by hand.** `saasaloy add <module>` writes a UI-bearing module's block into `src/blocks/` exactly like the base blocks, adds the app-side island that feeds it, and then stops: nothing globs a folder, and no command edits `index.astro`. The command prints a pointer to the module's skill, and that skill's **Wire-up** section carries the import line, the component to render, the client directive, and a suggested spot on the page. Put it where you want it. `saasaloy remove` deletes the files it wrote and leaves your import alone, so take that line out yourself.
|
|
126
|
+
|
|
127
|
+
Blocks, like primitives, are source you own — they are meant to be edited, not wrapped.
|
|
128
|
+
|
|
129
|
+
## Containers
|
|
130
|
+
|
|
131
|
+
**Containers — the shells and the layouts.** `src/containers/` holds the compositions that place blocks and components on a page: an app shell, a page layout, a page frame. The base ships none; `saasaloy add shell` writes the signed-in apps' into `src/containers/shell/`.
|
|
132
|
+
|
|
133
|
+
- **A container places, a block renders.** It decides where the panels, the header and the detail view go, and it adds no copy a block could hold.
|
|
134
|
+
- **No router, no session.** A container takes the nav data, the current area, a link component and the account as props. The app reads its router and its session and passes them in, so a container never depends on one app's routes.
|
|
135
|
+
- **Still no IO.** A container does not fetch, persist, or authenticate.
|
|
136
|
+
- **Same file rules as blocks:** one container per file, semantic kebab-case filename, no barrel.
|
|
137
|
+
|
|
138
|
+
## Copy
|
|
139
|
+
|
|
140
|
+
**The content module — where the words live.** `packages/ui/src/content/landing.ts` holds every user-visible string on the landing page, in two namespaces:
|
|
141
|
+
|
|
142
|
+
- **`landing.*`** — marketing copy. What the product is, who it is for, what it costs. This is the whole surface a copy rewrite touches. The brand itself is not here: it is `config.app.name` in `packages/config/src/project.ts`, is not translated, and is set once by `saasaloy-setup`. The currency symbol and the tier ids and names are read from `@repo/config` for the same reason — they are ids and numbers, and `packages/billing` charges against the same ids.
|
|
143
|
+
- **`ui.*`** — chrome and accessibility labels (`Monthly`, `Most popular`, `Close menu`, `Billing period`). Nothing here says anything about the product, so a copy pass never rewrites it. It does get translated, key for key, when `landing.*` is written in some language other than English — no translation layer ships in the base, so that pass is the only one these strings get.
|
|
144
|
+
|
|
145
|
+
Blocks import it **directly** — `import { landing, ui } from "@repo/ui/content/landing"` — never as props from `index.astro`. Astro serializes island props, so passing content into `<PricingTable client:visible />` would write every string into the HTML payload *and* still ship the defaults inside the island's bundle. Direct import keeps the static blocks at zero JavaScript.
|
|
146
|
+
|
|
147
|
+
Five rules keep that file mechanically translatable — a translation layer reads a keyed record and nothing else. Follow them when you add a block or a key:
|
|
148
|
+
|
|
149
|
+
1. **Max three levels below a namespace** (`landing.features.title`). Compiler-based i18n libraries emit one flat identifier per message and cannot see deeper nesting.
|
|
150
|
+
2. **Position is never the key.** Lists are arrays whose items carry a stable `id`, so reordering the feature grid cannot silently reattach the wrong translation. One list is exempt — a tier's `features` bullets stay a plain `string[]`, because nothing reads them individually (a feature id and an FAQ id both anchor an item that outlives its wording) and a tier's bullets are rewritten with that tier. The content file states the trade-off in full.
|
|
151
|
+
3. **Single-brace `{token}` placeholders, never a template literal.** Copy is data; a template literal is a function, which no extraction tool can read. Render with `interpolate()` from `@repo/ui/lib/interpolate`.
|
|
152
|
+
4. **No runtime concatenation.** `/month` plus `", billed annually"` is two whole messages (`ui.pricing.perMonth`, `ui.pricing.perMonthAnnual`) — word order does not survive the seam in every language.
|
|
153
|
+
5. **Only user-visible strings move.** Section `id`s and the same-page anchors pointing at them are structure and stay in the block. A few things break the rule, all because a thing rewritten *with* the copy belongs *near* the copy: the whole `tiers` array (prices and `ctaHref`s included); every `icon`, held as a registry *name* like `"zap"` and resolved to a component by `packages/ui/src/lib/icons.ts`, and every logo `mark`, resolved by `blocks/logo-cloud.tsx`; every outbound link (`*Href`), which leaves the page and so cannot break a section link; and the code the page quotes (terminal commands, module names, file paths). A translation layer reads `id`, `icon`, `mark`, every `*Href` and the quoted code as non-message data. A pair of backticks inside a message renders as `<code>` through `inlineCode()` from `@repo/ui/lib/inline-code`.
|
|
154
|
+
|
|
155
|
+
**No copy that goes stale.** Do not write a version number, a release date or a count into a message. Say something general and link to where the current value lives: the hero pill says "See what's new" and links to the changelog, so it stays true across every release.
|
|
156
|
+
|
|
157
|
+
Two consequences worth knowing. Blanking a navbar or footer link's label in content drops that link, which is how a removed section loses its nav entry without editing a block. And the theme toggle's labels deliberately stay in `packages/ui/src/lib/theme.ts`: that file is inlined verbatim into a pre-paint `<script>` and is import-free on purpose.
|
|
158
|
+
|
|
159
|
+
**The default copy is Saasaloy's own.** A fresh project's page describes Saasaloy, and `config.app.name` defaults to `"Saasaloy"`, so the brand and the words agree until you replace both. `saasaloy-setup` writes the product brief and sets the name, and `saasaloy-landing-copy` rewrites `landing.ts` from the brief. Use them rather than editing thirteen blocks by hand, and if you do edit by hand, keep the strings in the content module so the next pass finds them.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
@AGENTS.md
|
|
@@ -2,11 +2,11 @@
|
|
|
2
2
|
|
|
3
3
|
Containers are the shells and layouts that hold blocks and components on a page: an app shell, a page layout, a page frame. The visual weight of a screen sits in its blocks; a container decides where they go.
|
|
4
4
|
|
|
5
|
-
The base ships none. `saasaloy add
|
|
5
|
+
The base ships none. `saasaloy add shell` writes the signed-in apps' shell and layouts into `src/containers/shell/`.
|
|
6
6
|
|
|
7
|
-
Rules (the full version is in
|
|
7
|
+
Rules (the full version is in `packages/ui/AGENTS.md`):
|
|
8
8
|
|
|
9
9
|
- A container takes its data, its links and its callbacks as props. It imports no router and no session; the app that owns them passes them in.
|
|
10
10
|
- No IO anywhere in `@repo/ui`: no fetch, no persistence, no auth.
|
|
11
|
-
- One container, one file. Reach it by subpath: `import { ShellLayout } from "@repo/ui/containers/
|
|
12
|
-
- A folder may hold `admin/`, `web/` or `shared/` children where one
|
|
11
|
+
- One container, one file. Reach it by subpath: `import { ShellLayout } from "@repo/ui/containers/shell/shell-layout";`.
|
|
12
|
+
- A folder may hold `shell/`, `admin/`, `web/` or `shared/` children where one module owns the files.
|
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
/* The brand: the token values, the colour mapping, the radius scale and the `dark`
|
|
2
|
+
variant. Every app that wears the product's look imports this file once, through its
|
|
3
|
+
own stylesheet: web.css for the landing page today, and any later app stylesheet the
|
|
4
|
+
same way. apps/web/DESIGN.md records these values and fingerprints this file.
|
|
5
|
+
|
|
6
|
+
This is the file components.json names, so a shadcn preset merges into it. The
|
|
7
|
+
`dark` variant and the `@theme inline` mapping sit here rather than in globals.css on
|
|
8
|
+
purpose, and admin.css repeats both for the same reason: shadcn 4.21.0 merges a preset
|
|
9
|
+
in place only when the target file itself holds them. It does not follow the
|
|
10
|
+
`@import`, so with either one left in globals.css it appends a second
|
|
11
|
+
`@custom-variant dark`, or a second `@theme inline` with its own radius formula, to
|
|
12
|
+
this file. Keep them together here.
|
|
13
|
+
|
|
14
|
+
This file imports the shared layer itself, so an app stylesheet needs one line,
|
|
15
|
+
`@import "./brand.css";`, to get Tailwind, the base layer and the tokens in order.
|
|
16
|
+
The other choice, an app stylesheet that imports globals.css and then this file,
|
|
17
|
+
makes every app repeat the pair in the right order, and a file that imports this
|
|
18
|
+
one alone gets tokens with no Tailwind under them. Never import globals.css next to
|
|
19
|
+
this file: a second copy of Tailwind's entrypoint duplicates every rule. */
|
|
20
|
+
@import "./globals.css";
|
|
21
|
+
|
|
22
|
+
/* Dark mode is the `.dark` class shadcn assumes. It is set pre-paint by the inline
|
|
23
|
+
THEME_INIT_SCRIPT (packages/ui/src/lib/theme.ts) that every host document emits —
|
|
24
|
+
from the visitor's stored choice, falling back to the OS preference. The chosen
|
|
25
|
+
state also lands on <html> as `data-theme`, which is what blocks/theme-toggle.tsx
|
|
26
|
+
keys its icons off; nothing here needs to know about it. */
|
|
27
|
+
@custom-variant dark (&:is(.dark *));
|
|
28
|
+
|
|
29
|
+
:root {
|
|
30
|
+
/* Tell the browser which palette the document is using, so native UI it renders for
|
|
31
|
+
us — scrollbars, form controls, the default canvas — follows the theme too. The
|
|
32
|
+
tokens below only cover what we paint ourselves. Paired with `.dark` rather than
|
|
33
|
+
`light dark` on :root, because the theme is class-driven, not media-driven: the
|
|
34
|
+
pre-paint script resolves the visitor's choice (or the OS preference behind it)
|
|
35
|
+
into a class, and re-resolves on the fly when the OS flips while the choice is
|
|
36
|
+
`system`. `light dark` here would let the OS override an explicit choice. */
|
|
37
|
+
color-scheme: light;
|
|
38
|
+
|
|
39
|
+
--radius: 0.625rem;
|
|
40
|
+
--background: oklch(1 0 0);
|
|
41
|
+
--foreground: oklch(0.145 0 0);
|
|
42
|
+
--card: oklch(1 0 0);
|
|
43
|
+
--card-foreground: oklch(0.145 0 0);
|
|
44
|
+
--popover: oklch(1 0 0);
|
|
45
|
+
--popover-foreground: oklch(0.145 0 0);
|
|
46
|
+
--primary: oklch(0.205 0 0);
|
|
47
|
+
--primary-foreground: oklch(0.985 0 0);
|
|
48
|
+
--secondary: oklch(0.97 0 0);
|
|
49
|
+
--secondary-foreground: oklch(0.205 0 0);
|
|
50
|
+
--muted: oklch(0.97 0 0);
|
|
51
|
+
--muted-foreground: oklch(0.556 0 0);
|
|
52
|
+
--accent: oklch(0.97 0 0);
|
|
53
|
+
--accent-foreground: oklch(0.205 0 0);
|
|
54
|
+
--destructive: oklch(0.577 0.245 27.325);
|
|
55
|
+
--border: oklch(0.922 0 0);
|
|
56
|
+
--input: oklch(0.922 0 0);
|
|
57
|
+
--ring: oklch(0.708 0 0);
|
|
58
|
+
--chart-1: oklch(0.87 0 0);
|
|
59
|
+
--chart-2: oklch(0.556 0 0);
|
|
60
|
+
--chart-3: oklch(0.439 0 0);
|
|
61
|
+
--chart-4: oklch(0.371 0 0);
|
|
62
|
+
--chart-5: oklch(0.269 0 0);
|
|
63
|
+
--sidebar: oklch(0.985 0 0);
|
|
64
|
+
--sidebar-foreground: oklch(0.145 0 0);
|
|
65
|
+
--sidebar-primary: oklch(0.205 0 0);
|
|
66
|
+
--sidebar-primary-foreground: oklch(0.985 0 0);
|
|
67
|
+
--sidebar-accent: oklch(0.97 0 0);
|
|
68
|
+
--sidebar-accent-foreground: oklch(0.205 0 0);
|
|
69
|
+
--sidebar-border: oklch(0.922 0 0);
|
|
70
|
+
--sidebar-ring: oklch(0.708 0 0);
|
|
71
|
+
}
|
|
72
|
+
|
|
73
|
+
.dark {
|
|
74
|
+
color-scheme: dark;
|
|
75
|
+
|
|
76
|
+
--background: oklch(0.145 0 0);
|
|
77
|
+
--foreground: oklch(0.985 0 0);
|
|
78
|
+
--card: oklch(0.205 0 0);
|
|
79
|
+
--card-foreground: oklch(0.985 0 0);
|
|
80
|
+
--popover: oklch(0.205 0 0);
|
|
81
|
+
--popover-foreground: oklch(0.985 0 0);
|
|
82
|
+
--primary: oklch(0.922 0 0);
|
|
83
|
+
--primary-foreground: oklch(0.205 0 0);
|
|
84
|
+
--secondary: oklch(0.269 0 0);
|
|
85
|
+
--secondary-foreground: oklch(0.985 0 0);
|
|
86
|
+
--muted: oklch(0.269 0 0);
|
|
87
|
+
--muted-foreground: oklch(0.708 0 0);
|
|
88
|
+
--accent: oklch(0.269 0 0);
|
|
89
|
+
--accent-foreground: oklch(0.985 0 0);
|
|
90
|
+
--destructive: oklch(0.704 0.191 22.216);
|
|
91
|
+
--border: oklch(1 0 0 / 10%);
|
|
92
|
+
--input: oklch(1 0 0 / 15%);
|
|
93
|
+
--ring: oklch(0.556 0 0);
|
|
94
|
+
--chart-1: oklch(0.87 0 0);
|
|
95
|
+
--chart-2: oklch(0.556 0 0);
|
|
96
|
+
--chart-3: oklch(0.439 0 0);
|
|
97
|
+
--chart-4: oklch(0.371 0 0);
|
|
98
|
+
--chart-5: oklch(0.269 0 0);
|
|
99
|
+
--sidebar: oklch(0.205 0 0);
|
|
100
|
+
--sidebar-foreground: oklch(0.985 0 0);
|
|
101
|
+
--sidebar-primary: oklch(0.488 0.243 264.376);
|
|
102
|
+
--sidebar-primary-foreground: oklch(0.985 0 0);
|
|
103
|
+
--sidebar-accent: oklch(0.269 0 0);
|
|
104
|
+
--sidebar-accent-foreground: oklch(0.985 0 0);
|
|
105
|
+
--sidebar-border: oklch(1 0 0 / 10%);
|
|
106
|
+
--sidebar-ring: oklch(0.556 0 0);
|
|
107
|
+
}
|
|
108
|
+
|
|
109
|
+
@theme inline {
|
|
110
|
+
--radius-sm: calc(var(--radius) - 4px);
|
|
111
|
+
--radius-md: calc(var(--radius) - 2px);
|
|
112
|
+
--radius-lg: var(--radius);
|
|
113
|
+
--radius-xl: calc(var(--radius) + 4px);
|
|
114
|
+
--color-background: var(--background);
|
|
115
|
+
--color-foreground: var(--foreground);
|
|
116
|
+
--color-card: var(--card);
|
|
117
|
+
--color-card-foreground: var(--card-foreground);
|
|
118
|
+
--color-popover: var(--popover);
|
|
119
|
+
--color-popover-foreground: var(--popover-foreground);
|
|
120
|
+
--color-primary: var(--primary);
|
|
121
|
+
--color-primary-foreground: var(--primary-foreground);
|
|
122
|
+
--color-secondary: var(--secondary);
|
|
123
|
+
--color-secondary-foreground: var(--secondary-foreground);
|
|
124
|
+
--color-muted: var(--muted);
|
|
125
|
+
--color-muted-foreground: var(--muted-foreground);
|
|
126
|
+
--color-accent: var(--accent);
|
|
127
|
+
--color-accent-foreground: var(--accent-foreground);
|
|
128
|
+
--color-destructive: var(--destructive);
|
|
129
|
+
--color-border: var(--border);
|
|
130
|
+
--color-input: var(--input);
|
|
131
|
+
--color-ring: var(--ring);
|
|
132
|
+
--color-chart-1: var(--chart-1);
|
|
133
|
+
--color-chart-2: var(--chart-2);
|
|
134
|
+
--color-chart-3: var(--chart-3);
|
|
135
|
+
--color-chart-4: var(--chart-4);
|
|
136
|
+
--color-chart-5: var(--chart-5);
|
|
137
|
+
--color-sidebar: var(--sidebar);
|
|
138
|
+
--color-sidebar-foreground: var(--sidebar-foreground);
|
|
139
|
+
--color-sidebar-primary: var(--sidebar-primary);
|
|
140
|
+
--color-sidebar-primary-foreground: var(--sidebar-primary-foreground);
|
|
141
|
+
--color-sidebar-accent: var(--sidebar-accent);
|
|
142
|
+
--color-sidebar-accent-foreground: var(--sidebar-accent-foreground);
|
|
143
|
+
--color-sidebar-border: var(--sidebar-border);
|
|
144
|
+
--color-sidebar-ring: var(--sidebar-ring);
|
|
145
|
+
}
|
|
@@ -1,14 +1,13 @@
|
|
|
1
1
|
/* The shared layer of the theme. `@repo/ui` owns Tailwind's entrypoint, the source globs
|
|
2
|
-
and the base layer here, and NO token values.
|
|
3
|
-
|
|
4
|
-
first:
|
|
2
|
+
and the base layer here, and NO token values. The tokens, colour mapping and `dark`
|
|
3
|
+
variant live in a theme file beside this one, which imports this file first:
|
|
5
4
|
|
|
6
|
-
-
|
|
5
|
+
- brand.css the product's tokens (web.css imports it, and Layout.astro imports web.css)
|
|
7
6
|
- admin.css the admin app's tokens, written by the admin module
|
|
8
7
|
|
|
9
|
-
An app imports its
|
|
10
|
-
shadcn's `neutral` base color with `cssVariables: true`, and components.json points
|
|
11
|
-
|
|
8
|
+
An app imports its own stylesheet, never this one directly. The token set in brand.css
|
|
9
|
+
is shadcn's `neutral` base color with `cssVariables: true`, and components.json points
|
|
10
|
+
at brand.css, so a preset or `pnpm --filter @repo/ui exec shadcn add <x>` lands there. */
|
|
12
11
|
@import "tailwindcss";
|
|
13
12
|
@import "tw-animate-css";
|
|
14
13
|
@import "shadcn/tailwind.css";
|
|
@@ -1,146 +1,14 @@
|
|
|
1
|
-
/* The web app's
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
`dark` variant and the `@theme inline` mapping sit here rather than in globals.css on
|
|
8
|
-
purpose, and admin.css repeats both for the same reason: shadcn 4.21.0 merges a preset
|
|
9
|
-
in place only when the target file itself holds them. It does not follow the
|
|
10
|
-
`@import`, so with either one left in globals.css it appends a second
|
|
11
|
-
`@custom-variant dark`, or a second `@theme inline` with its own radius formula, to
|
|
12
|
-
this file. Keep them together here. */
|
|
13
|
-
@import "./globals.css";
|
|
14
|
-
|
|
15
|
-
/* Dark mode is the `.dark` class shadcn assumes. It is set pre-paint by the inline
|
|
16
|
-
THEME_INIT_SCRIPT (packages/ui/src/lib/theme.ts) that every host document emits —
|
|
17
|
-
from the visitor's stored choice, falling back to the OS preference. The chosen
|
|
18
|
-
state also lands on <html> as `data-theme`, which is what blocks/theme-toggle.tsx
|
|
19
|
-
keys its icons off; nothing here needs to know about it. */
|
|
20
|
-
@custom-variant dark (&:is(.dark *));
|
|
21
|
-
|
|
22
|
-
:root {
|
|
23
|
-
/* Tell the browser which palette the document is using, so native UI it renders for
|
|
24
|
-
us — scrollbars, form controls, the default canvas — follows the theme too. The
|
|
25
|
-
tokens below only cover what we paint ourselves. Paired with `.dark` rather than
|
|
26
|
-
`light dark` on :root, because the theme is class-driven, not media-driven: the
|
|
27
|
-
pre-paint script resolves the visitor's choice (or the OS preference behind it)
|
|
28
|
-
into a class, and re-resolves on the fly when the OS flips while the choice is
|
|
29
|
-
`system`. `light dark` here would let the OS override an explicit choice. */
|
|
30
|
-
color-scheme: light;
|
|
31
|
-
|
|
32
|
-
--radius: 0.625rem;
|
|
33
|
-
--background: oklch(1 0 0);
|
|
34
|
-
--foreground: oklch(0.145 0 0);
|
|
35
|
-
--card: oklch(1 0 0);
|
|
36
|
-
--card-foreground: oklch(0.145 0 0);
|
|
37
|
-
--popover: oklch(1 0 0);
|
|
38
|
-
--popover-foreground: oklch(0.145 0 0);
|
|
39
|
-
--primary: oklch(0.205 0 0);
|
|
40
|
-
--primary-foreground: oklch(0.985 0 0);
|
|
41
|
-
--secondary: oklch(0.97 0 0);
|
|
42
|
-
--secondary-foreground: oklch(0.205 0 0);
|
|
43
|
-
--muted: oklch(0.97 0 0);
|
|
44
|
-
--muted-foreground: oklch(0.556 0 0);
|
|
45
|
-
--accent: oklch(0.97 0 0);
|
|
46
|
-
--accent-foreground: oklch(0.205 0 0);
|
|
47
|
-
--destructive: oklch(0.577 0.245 27.325);
|
|
48
|
-
--border: oklch(0.922 0 0);
|
|
49
|
-
--input: oklch(0.922 0 0);
|
|
50
|
-
--ring: oklch(0.708 0 0);
|
|
51
|
-
--chart-1: oklch(0.87 0 0);
|
|
52
|
-
--chart-2: oklch(0.556 0 0);
|
|
53
|
-
--chart-3: oklch(0.439 0 0);
|
|
54
|
-
--chart-4: oklch(0.371 0 0);
|
|
55
|
-
--chart-5: oklch(0.269 0 0);
|
|
56
|
-
--sidebar: oklch(0.985 0 0);
|
|
57
|
-
--sidebar-foreground: oklch(0.145 0 0);
|
|
58
|
-
--sidebar-primary: oklch(0.205 0 0);
|
|
59
|
-
--sidebar-primary-foreground: oklch(0.985 0 0);
|
|
60
|
-
--sidebar-accent: oklch(0.97 0 0);
|
|
61
|
-
--sidebar-accent-foreground: oklch(0.205 0 0);
|
|
62
|
-
--sidebar-border: oklch(0.922 0 0);
|
|
63
|
-
--sidebar-ring: oklch(0.708 0 0);
|
|
64
|
-
}
|
|
65
|
-
|
|
66
|
-
.dark {
|
|
67
|
-
color-scheme: dark;
|
|
68
|
-
|
|
69
|
-
--background: oklch(0.145 0 0);
|
|
70
|
-
--foreground: oklch(0.985 0 0);
|
|
71
|
-
--card: oklch(0.205 0 0);
|
|
72
|
-
--card-foreground: oklch(0.985 0 0);
|
|
73
|
-
--popover: oklch(0.205 0 0);
|
|
74
|
-
--popover-foreground: oklch(0.985 0 0);
|
|
75
|
-
--primary: oklch(0.922 0 0);
|
|
76
|
-
--primary-foreground: oklch(0.205 0 0);
|
|
77
|
-
--secondary: oklch(0.269 0 0);
|
|
78
|
-
--secondary-foreground: oklch(0.985 0 0);
|
|
79
|
-
--muted: oklch(0.269 0 0);
|
|
80
|
-
--muted-foreground: oklch(0.708 0 0);
|
|
81
|
-
--accent: oklch(0.269 0 0);
|
|
82
|
-
--accent-foreground: oklch(0.985 0 0);
|
|
83
|
-
--destructive: oklch(0.704 0.191 22.216);
|
|
84
|
-
--border: oklch(1 0 0 / 10%);
|
|
85
|
-
--input: oklch(1 0 0 / 15%);
|
|
86
|
-
--ring: oklch(0.556 0 0);
|
|
87
|
-
--chart-1: oklch(0.87 0 0);
|
|
88
|
-
--chart-2: oklch(0.556 0 0);
|
|
89
|
-
--chart-3: oklch(0.439 0 0);
|
|
90
|
-
--chart-4: oklch(0.371 0 0);
|
|
91
|
-
--chart-5: oklch(0.269 0 0);
|
|
92
|
-
--sidebar: oklch(0.205 0 0);
|
|
93
|
-
--sidebar-foreground: oklch(0.985 0 0);
|
|
94
|
-
--sidebar-primary: oklch(0.488 0.243 264.376);
|
|
95
|
-
--sidebar-primary-foreground: oklch(0.985 0 0);
|
|
96
|
-
--sidebar-accent: oklch(0.269 0 0);
|
|
97
|
-
--sidebar-accent-foreground: oklch(0.985 0 0);
|
|
98
|
-
--sidebar-border: oklch(1 0 0 / 10%);
|
|
99
|
-
--sidebar-ring: oklch(0.556 0 0);
|
|
100
|
-
}
|
|
101
|
-
|
|
102
|
-
@theme inline {
|
|
103
|
-
--radius-sm: calc(var(--radius) - 4px);
|
|
104
|
-
--radius-md: calc(var(--radius) - 2px);
|
|
105
|
-
--radius-lg: var(--radius);
|
|
106
|
-
--radius-xl: calc(var(--radius) + 4px);
|
|
107
|
-
--color-background: var(--background);
|
|
108
|
-
--color-foreground: var(--foreground);
|
|
109
|
-
--color-card: var(--card);
|
|
110
|
-
--color-card-foreground: var(--card-foreground);
|
|
111
|
-
--color-popover: var(--popover);
|
|
112
|
-
--color-popover-foreground: var(--popover-foreground);
|
|
113
|
-
--color-primary: var(--primary);
|
|
114
|
-
--color-primary-foreground: var(--primary-foreground);
|
|
115
|
-
--color-secondary: var(--secondary);
|
|
116
|
-
--color-secondary-foreground: var(--secondary-foreground);
|
|
117
|
-
--color-muted: var(--muted);
|
|
118
|
-
--color-muted-foreground: var(--muted-foreground);
|
|
119
|
-
--color-accent: var(--accent);
|
|
120
|
-
--color-accent-foreground: var(--accent-foreground);
|
|
121
|
-
--color-destructive: var(--destructive);
|
|
122
|
-
--color-border: var(--border);
|
|
123
|
-
--color-input: var(--input);
|
|
124
|
-
--color-ring: var(--ring);
|
|
125
|
-
--color-chart-1: var(--chart-1);
|
|
126
|
-
--color-chart-2: var(--chart-2);
|
|
127
|
-
--color-chart-3: var(--chart-3);
|
|
128
|
-
--color-chart-4: var(--chart-4);
|
|
129
|
-
--color-chart-5: var(--chart-5);
|
|
130
|
-
--color-sidebar: var(--sidebar);
|
|
131
|
-
--color-sidebar-foreground: var(--sidebar-foreground);
|
|
132
|
-
--color-sidebar-primary: var(--sidebar-primary);
|
|
133
|
-
--color-sidebar-primary-foreground: var(--sidebar-primary-foreground);
|
|
134
|
-
--color-sidebar-accent: var(--sidebar-accent);
|
|
135
|
-
--color-sidebar-accent-foreground: var(--sidebar-accent-foreground);
|
|
136
|
-
--color-sidebar-border: var(--sidebar-border);
|
|
137
|
-
--color-sidebar-ring: var(--sidebar-ring);
|
|
138
|
-
}
|
|
1
|
+
/* The web app's stylesheet: the brand tokens, then the landing page's layout, type and
|
|
2
|
+
motion vocabulary. apps/web/src/layouts/Layout.astro imports this file once.
|
|
3
|
+
brand.css holds the token values, the colour mapping, the radius scale and the `dark`
|
|
4
|
+
variant, and it imports the shared layer first. A shadcn preset merges into
|
|
5
|
+
brand.css, never here. apps/web/DESIGN.md records the vocabulary below. */
|
|
6
|
+
@import "./brand.css";
|
|
139
7
|
|
|
140
8
|
/* The landing page's layout, type and motion vocabulary. Blocks use these names and write
|
|
141
9
|
no widths, no section padding, no keyframes of their own, so the page keeps one rhythm
|
|
142
10
|
and a preset or a redesign changes it in one place. None of this is a colour: a theme
|
|
143
|
-
preset replaces the colour tokens
|
|
11
|
+
preset replaces the colour tokens in brand.css and leaves these alone.
|
|
144
12
|
|
|
145
13
|
Widths. `page` is every section's container. `narrow` is a deliberate reading measure
|
|
146
14
|
for the FAQ and the closing CTA. `wide` is for the chrome around the page: the navbar
|