Adding a volume

Updated

July 30, 2026

Adding a volume

Use this when you want another independent track in the series (Rust, Kubernetes, Linux internals, Networking, …).

Filesystem convention

content/
  00-program/           # series-wide (edit sparingly)
  01-go/                # volume 1
  02-nixos/             # volume 2
  03-maths/             # volume 3
  04-<short-name>/      # volume 4 — NEW
    00-sub-book-overview.qmd
    01-syllabus.qmd
    # 02-… chapters later
  _planning/            # not published

Part titles come from the directory name (04-rust → sidebar part Rust).

Checklist for a new volume

  1. Baseline — language/runtime version pin (date it).
  2. Audience — who this volume is for and what is assumed.
  3. Expert syllabus — 4 stages, 4 gates, out-of-scope, modern defaults.
  4. 30-day mapping — show which original topics combine into each day.
  5. Capstone — one prove-it artifact.
  6. Overview + syllabus first (no empty chapter spam).
  7. Run bash scripts/update-index.sh (never hand-edit _quarto.yml).
  8. Update this book’s index.qmd volume table and README.md.

How readers use multiple volumes

Approach Notes
Sequential Finish or pause volume A, then start volume B (recommended default)
Overlapping Personal choice only; this series does not define a joint timetable
Pick one Perfectly valid—the series is a library of volumes

Do not design a new volume assuming every reader also completes every other volume.

Naming

  • Folder: NN-short-name with numeric prefix for order
  • Portal book title remains 30DaysOfX (series container)
  • A volume may later graduate to a standalone monorepo book if it outgrows the series