claude@clouddev1
dfb5f0b1b1
The website subproject drew ADR numbers from the same global integer pool
as main, so every merge risked a collision — this already happened twice
(drafted 0042, bumped to 0044, both landing on numbers main had taken; main
has now used 0044 for relationship visualization). Give the website its own
ADR namespace so the two never compete again.
- docs/adr/0044-public-website-...md
-> docs/website/adr/20260604-adr-website-001.md (id: ADR-website-001)
- docs/plans/20260604-adr-0044-website.md
-> docs/website/plans/20260604-website-implementation-plan.md
- new docs/website/adr/README.md index (dated <date>-adr-website-<NNN> seq)
- docs/adr/README.md: drop the 0044 entry, add a namespace pointer in the
intro (keeps the list tail == merge-base, so main's 0044 merges cleanly)
- ADR-0000: record the subproject-ADR-namespace convention
- update references in STYLE.md, astro.config.mjs, the plan body
Handoff files left untouched as point-in-time history.
20 lines
2.2 KiB
Markdown
20 lines
2.2 KiB
Markdown
# Website Architecture Decision Records
|
||
|
||
Decision records for the **public website + documentation site** subproject
|
||
(the Astro/Starlight site under `website/`). These are kept in their own
|
||
namespace, separate from the project-wide ADRs in
|
||
[`docs/adr/`](../../adr/README.md), so website decisions never compete with
|
||
the main global ADR sequence for numbers — see
|
||
[ADR-0000 "Numbering discipline"](../../adr/0000-record-architecture-decisions.md).
|
||
|
||
**Numbering.** Files are named `<date>-adr-website-<NNN>.md` and referenced
|
||
in prose as `ADR-website-NNN`. The `<date>` (the ADR's accepted/created day,
|
||
`YYYYMMDD`) plus the `website` segment keeps the namespace disjoint from
|
||
`main`'s integers. Assign the next free `NNN` from this index. Every ADR
|
||
change updates this index in the same edit (the ADR-0000 index-upkeep rule
|
||
applies here too).
|
||
|
||
## Index
|
||
|
||
- [ADR-website-001 — Public website and documentation site](20260604-adr-website-001.md) — **Accepted 2026-06-04** (formerly ADR-0044 in the main index; moved here 2026-06-10 to end recurring cross-branch number collisions). The first public website: a marketing landing page plus the **canonical** user docs. Stack **Astro 6 + Starlight + Tailwind v4** (chosen over SvelteKit + Tailwind for a docs-heavy + marketing site; interactive bits as Astro islands). Showcase demos are **asciinema** `.cast` recordings (scripted-input driver for paced, re-recordable sessions — *not* `history.log` replay), reused inline in docs. The **in-page WASM playground is deferred** (OOS: deferred) behind a stable `Demo` seam, with the portable-core vs native-edge boundary recorded for a future ADR + iteration plan. Portable **static build** (Vercel target, but host-agnostic); **no CI yet**; **monorepo** (`website/`). Docs cover the **full supported feature set** with "planned" callouts for the unshipped minority; two wording rules bind user-facing copy — **no engine name** (continues ADR-0002) and **no "DSL"** ("simple mode" / "advanced mode"). Install docs cover **prebuilt binaries + package managers** (D1–D3 track the release tooling). Plan: [`docs/website/plans/20260604-website-implementation-plan.md`](../plans/20260604-website-implementation-plan.md)
|