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
|
|
@ -7,7 +7,7 @@ field its bytes are in, and how this deployment's environment becomes a
|
|||
logged-in client.
|
||||
|
||||
The surrounding picture — which secret is minted where, and why delivery is a
|
||||
copy rather than a bind mount — is [`docs/swarm/credentials.md`](../docs/swarm/credentials.md).
|
||||
copy rather than a bind mount — is [`docs/2-handbook/swarm/credentials.md`](../docs/2-handbook/swarm/credentials.md).
|
||||
|
||||
## Why a crate and not a module per binary
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue