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
|
|
@ -16,6 +16,6 @@ admin socket.
|
|||
## Shape
|
||||
|
||||
Serde-derived request/response types only — no server or client logic. Both
|
||||
sides import them so the shapes stay in sync. See `docs/trust-boundary/boundary.md` +
|
||||
`docs/trust-boundary/security.md` for the privilege boundary these types sit on, and
|
||||
sides import them so the shapes stay in sync. See `docs/2-handbook/trust-boundary/boundary.md` +
|
||||
`docs/2-handbook/trust-boundary/security.md` for the privilege boundary these types sit on, and
|
||||
`hive-priv/README` for the helper itself.
|
||||
|
|
|
|||
Loading…
Reference in a new issue