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,7 +16,7 @@
|
|||
//! dashboard while the bucket says otherwise.
|
||||
//!
|
||||
//! **Absence is the case this is built around** — the freshness states
|
||||
//! and the reasoning behind each are in `docs/swarm/README.md`. The two
|
||||
//! and the reasoning behind each are in `docs/2-handbook/swarm/README.md`. The two
|
||||
//! properties that constrain the code rather than describe it:
|
||||
//! freshness is **derived at read time**, never stored (a stored
|
||||
//! `healthy: bool` goes stale silently the moment nothing arrives), and
|
||||
|
|
|
|||
Loading…
Reference in a new issue