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
|
|
@ -48,7 +48,7 @@ start. The `ensure-callout-keys` verb creates each pair when the store holds
|
|||
none, taking an issuer or user seed from the import file it is given when that
|
||||
file exists, and removes the file once the store holds a seed. It runs from
|
||||
its own unit before the server, because the server needs the public halves to
|
||||
start and the responder needs the server. `docs/swarm/credentials.md` has the
|
||||
start and the responder needs the server. `docs/2-handbook/swarm/credentials.md` has the
|
||||
paths and the boot order.
|
||||
|
||||
## Rules the code follows
|
||||
|
|
|
|||
Loading…
Reference in a new issue