aboutsummaryrefslogtreecommitdiff
path: root/doc/manual/src/SUMMARY.md.in
AgeCommit message (Collapse)Author
2022-08-04use singular for class names consistentlyValentin Gagarin
2022-08-04remove incomplete section: input/content-addressingValentin Gagarin
2022-08-04remove incomplete section: nix archivesValentin Gagarin
2022-08-04remove incomplete section: content-addressed objectsValentin Gagarin
2022-08-04remove incomplete section: relocatabilityValentin Gagarin
2022-08-04remove incomplete section: related workValentin Gagarin
2022-08-04remove incomplete section: buildingValentin Gagarin
2022-08-04Fix manual TOC linksJohn Ericson
2022-08-04design -> architecture, add motivationValentin Gagarin
following ideas found in Architecture of Gazelle[1] [1]: https://github.com/bazelbuild/bazel-gazelle/blob/56d35f8db086bb65ef876f96f7baa7b71516daf8/Design.rst
2022-08-04remove separate meta-section, add architecture diagramValentin Gagarin
the diagram is a first approximation and only covers that same section. of course there is much more going on, and other features should at some point also be illustrated. we also have to think about presentation format and technicalities behind it. the manual has to render to `man`, but we may want something more refined for web view.
2022-08-04Add draft "Rosetta stone" by @fricklerhandwerk and stub commentaryJohn Ericson
The idea and most of the execution are @fricklerhandwerk's. I changed a few things best I could based on @edolstra's corrections, and a Bazel glossary. Valentin Gagarin <valentin@fricklerhandwerk.de>
2022-08-04Rename files after store entry -> store object renameJohn Ericson
2022-08-04doc: Store entry -> store objectJohn Ericson
This matches the terminology in Eelco's thesis.
2022-08-04Start on the derivations sectionJohn Ericson
2022-08-04Move the bits on relocating store entires to the endJohn Ericson
They are too advanced for up front.
2022-08-04Flesh out TOCJohn Ericson
2022-08-04WIP: Document the design of NixJohn Ericson
The current docs are all "how to do things" and no "what is Nix" or "why are things the way they are". I see lots of misconception on the wider internet, and I also think we would benefit from a "living document" to answer some questions people currently turn to the thesis for. I think a new section of the manual can address all these issues.
2022-07-28manual: values -> data typesValentin Gagarin
2022-07-28manual: fix section title in table of contentsValentin Gagarin
2022-07-11Branch 2.10 release notesEelco Dolstra
2022-05-30Branch 2.9 release notesEelco Dolstra
2022-04-19Move rl-next.md to rl-2.8.mdEelco Dolstra
2022-03-07Move rl-next.md to rl-2.7.mdEelco Dolstra
2022-01-25Move rl-next.md to rl-2.5.mdEelco Dolstra
2021-12-13Move rl-next.md to rl-2.5.mdEelco Dolstra
2021-11-11Documenting how to use/build Nix' Docker imageRok Garbas
2021-10-28Rename rl-2.5.md to rl-next.mdEelco Dolstra
Having a generically named file for release notes for the next release makes things easier for PRs.
2021-09-09Manual: Link to 2.4 release notesEelco Dolstra
2020-12-17smaller fixesRok Garbas
2020-12-07Merge remote-tracking branch 'origin/master' into cli-guidelineRok Garbas
2020-12-02Generate separate manpages for each nix subcommandEelco Dolstra