Add sections and section content

A roadmap is divided into curriculum sections, and each section holds several section-content lessons. The clever part is the two-tag scheme: a lesson's primary tag is the track tag (so it nests under the roadmap) while a secondary section tag groups it into the right curriculum section. Getting the tag order right is the whole job.

First create each section tag as a public tag under Settings → Tags, following the convention train-{track}-NN-{section}, for example train-admin-roadmap-01-foundations. The numeric prefix orders the sections. Give it the section title as its name and a short description.

Then create a post for each lesson and tag it in this precise order:

Section-content lesson tags (order matters):
  1. admin-roadmap                        <- PRIMARY: the TRACK tag (nests under track)
  2. #training-content                    <- marks the post as a section lesson
  3. train-admin-roadmap-01-foundations   <- SECONDARY: the section tag (groups it)

The first tag must be the track's public tag, not the section tag. This is the single most common mistake. Because Ghost treats the first tag as primary, using the track tag is what makes the lesson nest at /training/{track}/{lesson-slug}/ and appear in the roadmap's curriculum. If you accidentally make the section tag primary, the lesson's URL and nesting break.

The internal #training-content tag (second) marks the post as a roadmap lesson, distinct from a standalone course lesson. The section tag (third) is public but is used only to group lessons into their section in the curriculum view — it does not drive the URL.

Give each lesson a slug matching the convention (train-{track}-NN-{section}-{title}) and set spaced publish dates in end-to-end order across all sections so the roadmap reads sequentially. Write real teaching content with clean headings and code blocks where relevant. Repeat for every lesson in every section. The final roadmap doc explains how end-to-end navigation walks all these lessons in order.