What is written, and what is not
The pages that exist, linked. The ones that do not are named below rather than shown as cards leading nowhere.
Installation
From a bare Debian machine to a bot that answers, with every command it takes.
Operator guide
What it costs to run, what is opt-in twice, and what an update does and does not touch.
Troubleshooting
Eight things that actually went wrong on a running deployment, and what each turned out to be.
Recorded, rather than imagined
The troubleshooting page is a list of real incidents. That decision is also why one page here is missing on purpose.
Why there is no list of imagined questions
The troubleshooting page is a list of things that actually happened on a running deployment, with what each one turned out to be and what to do about it. It is not a list of questions somebody imagined a reader might ask.
That is also why there is no frequently-asked-questions page here. The material this section is written from rules one out in its first line, and inventing one would be the single easiest way to make this documentation worth less than it is.
Every row is a real recorded incident, not an invented FAQ. That is the point of printing them.
Not written yet
Member guide, Command reference, FAQ: these are in the tree and have no page. They are named here rather than linked, because a card leading to an empty page is worse than an honest gap.
Install, then the five first things
In that order. The order matters more than it looks, because two of the steps need a running core.
Install it, then do the five first things in order, then read the operator guide for what it costs to run and what an update does to it. Keep the troubleshooting page for the day something goes wrong, which the recorded failures suggest is a question of when.