docs: sort the top-level directories into five sections by what the reader wants
Every docs directory moves under 1-getting-started, 2-handbook, 4-implementation or 5-project; the options reference (section 3) comes from the website and has no directory here. trust-boundary stays whole under the handbook for now. web-ui, swarm and tools split between handbook and implementation, and the command-line references move to 2-handbook/reference. Links, path references in code and nix, and the docs index follow the moves; no page content changes.
This commit is contained in:
parent
53ccbcb4b3
commit
6739bb903d
1 changed files with 736 additions and 701 deletions
|
|
@ -2,7 +2,7 @@
|
|||
# host and renders it as a base16 `colors.css` overlay file. `colors.css`
|
||||
# is the entire theme-swap contract for every frontend bundle in this
|
||||
# project (`theme.css` derives every semantic var from these 16 slots —
|
||||
# see docs/web-ui/css-vars.md), so "apply the operator's stylix palette"
|
||||
# see docs/4-implementation/web-ui/css-vars.md), so "apply the operator's stylix palette"
|
||||
# always reduces to "write this one file over the prebuilt dist's own
|
||||
# `colors.css`" — no npm/esbuild rebuild needed.
|
||||
#
|
||||
|
|
|
|||
Loading…
Reference in a new issue