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
|
|
@ -168,7 +168,7 @@ impl axum::response::IntoResponse for StatusUnavailable {
|
|||
/// Every error this daemon returns, in one shape.
|
||||
///
|
||||
/// RFC 9457 `application/problem+json` is the hive-wide contract for HTTP
|
||||
/// error bodies (`docs/process/conventions.md`), and the operator UIs read `detail`
|
||||
/// error bodies (`docs/5-project/process/conventions.md`), and the operator UIs read `detail`
|
||||
/// for display. A bare string forces the reader to treat the entire body as
|
||||
/// the message, which is the difference between a UI that can offer "copy the
|
||||
/// cause" and one that can only dump a response.
|
||||
|
|
|
|||
Loading…
Reference in a new issue