How-to guides

A how-to guide takes one task from the first command to the last check, in the order you do it, and nothing else. It does not explain the machinery: every step links to the chapter of the Developer book that does, so you can follow the guide without reading a book first and read the book when a step makes you curious.

Each guide is written from a real run in a sub-tree of its own: every step in it was taken, and every file and message it shows is what that run produced; then the guide is audited claim by claim against the code.

1. Creating a block, step by step — a testimonial block for pages: a quote, a name and a picture from the library, with a look an editor can choose.