1. Create the book

In the admin, go to Content → Books and add a book. You will set:

  • Name — what readers see as the title of the whole set.
  • Slug — the URL segment. Books are served beneath a /books prefix, so a book with the slug user-documentation lives at /books/user-documentation.
  • Layout — the book's own layout, which supplies its editable areas.

2. Fill in the book's areas

A book layout typically offers an intro line, a badge, an optional body, and often an audience marker that tells the templates whether this is user-facing or developer-facing documentation. Fill these in now — they are what makes the book's landing page look finished rather than like an empty list.

3. Add units

Units are the chapters. Add them from within the book. Each needs a name, a slug and a position, and gets its own short intro describing what the chapter covers.

Plan the chapter list before writing any articles. Reordering later is possible but it changes URLs if you also rename slugs, and it is much cheaper to get the shape right first.

4. Add pages

Pages are added inside a unit. A page must have a layout assigned to hold any content at all — a book page has no plain text field of its own, so everything lives in layout areas. A page with no layout renders its title and nothing else.

5. Publish, in order

Publish the book, its units and its pages. All three levels need to be published for a reader to reach an article — an unpublished book hides everything beneath it, however carefully you published the individual pages.

A note on ordering

Position controls reading order, which is what drives previous and next links. Leave gaps in your numbering if you expect to insert articles later.