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
|
|
@ -9,7 +9,7 @@
|
|||
//! execution, build-log, cancel, and the dashboard group (a group root's
|
||||
//! subtree *is* the group). A DAG used to be a second level above it, with
|
||||
//! its own store and its own id; there is no container node any more, so a
|
||||
//! job is exactly the nodes it declared. See `docs/scheduler/coordinator.md::Job queue`
|
||||
//! job is exactly the nodes it declared. See `docs/4-implementation/scheduler/coordinator.md::Job queue`
|
||||
//! for the full design.
|
||||
|
||||
pub use hive_host_sock::jobs::State;
|
||||
|
|
@ -23,7 +23,7 @@ use serde::Serialize;
|
|||
///
|
||||
/// What each kind does, the resource/lease rules, and the DAG shapes they
|
||||
/// compose into live in the node-inventory table and surrounding sections
|
||||
/// of `docs/scheduler/coordinator.md` — this enum is deliberately not a
|
||||
/// of `docs/4-implementation/scheduler/coordinator.md` — this enum is deliberately not a
|
||||
/// second copy of that; each variant below gets a one-line pointer.
|
||||
#[derive(Debug, Clone, PartialEq, Eq, Serialize, strum::IntoStaticStr)]
|
||||
#[serde(tag = "kind", rename_all = "snake_case")]
|
||||
|
|
|
|||
Loading…
Reference in a new issue