Add Author Quickstart chapter for docs-spec-template#155
Conversation
Add a chapter walking spec authors through bootstrapping a repo from docs-spec-template: renaming the template, where content files live, the single-source PDF/Antora model, manual steps, and the local build loop. Wire it into the book between the intro and authoring chapters. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Bill Traynor <wmat@riscv.org>
|
|
||
| The single most important idea: your chapter content lives **once**, in | ||
| `modules/ROOT/pages/`. Both the PDF and the site read those same files. What you | ||
| maintain by hand is a one-line _pointer_ to each chapter in two glue files -- not |
There was a problem hiding this comment.
in two glue files?
| === Where the content files go | ||
|
|
||
| All chapter content goes in `modules/ROOT/pages/`, one file per chapter. Each | ||
| page is a standalone Antora page that starts with a **level-0 title** |
There was a problem hiding this comment.
they do? level-0 title? that is an h1, right? pretty sure they are all h2s
There was a problem hiding this comment.
I don't know why this is highlighted yellow for me so if you see yellow, I dunno - ignore it?
| [source] | ||
| ---- | ||
| modules/ROOT/pages/ | ||
| index.adoc <1> |
There was a problem hiding this comment.
add copyright.adoc after this. or is this something that we will have to add later because it might muck up the PDF?
There was a problem hiding this comment.
Let's add copyright in the next PR.
| <3> Front matter. | ||
| <4> Back matter. | ||
| <5> Bibliography database. | ||
| <6> PDF assembler -- glue, not content (see below). |
There was a problem hiding this comment.
glue again
| heading, reproducing the historical PDF chapter numbering. | ||
|
|
||
| So there is no copy to keep in sync. What you _do_ maintain is a one-line pointer | ||
| to each page in **two** glue files. Whenever you add, remove, or reorder a |
There was a problem hiding this comment.
glue again
| (`riscv-admin/antora.riscv.org`), keyed to the **line numbers of the `xref` | ||
| entries in `modules/ROOT/nav.adoc`** -- not by anything in your repo. When your | ||
| nav lines shift, the matching `chapters: {start, end}` entry in the playbook's | ||
| `numbering_rules` must be updated in lockstep, or site numbering silently drifts. |
There was a problem hiding this comment.
I think you are using lockstep too much. Maybe "at the same time" this time?
There was a problem hiding this comment.
Fair enough. I replaced one and left one.
|
|
||
| ==== Every time you change chapter structure | ||
|
|
||
| Update the **central playbook's numbering rule.** This is the easiest step to |
There was a problem hiding this comment.
I dunno - I think that this shouldn't be in here, unless they have the chaptering ability in their own playbook. Until we are building their stuff, it seems weird that they would come edit it in our central playbook.
There was a problem hiding this comment.
Agreed, in fact I'd like to remove it from the playbook altogether somehow.
|
|
||
| ==== One-time site registration | ||
|
|
||
| Your spec must be added as a `content.sources:` entry in the central playbook |
There was a problem hiding this comment.
this won't happen until after ratification, yes?
There was a problem hiding this comment.
Depends if we start exposing dev specs before ratification. I was hoping that issuing a PR against the playbook to add a new spec could fall on the authors.
| make stamp-antora VERSION=vX.Y.Z # then commit antora.yml | ||
| ---- | ||
|
|
||
| In normal CI this is automated: the release build stamps `antora.yml` and opens a |
There was a problem hiding this comment.
if this is automated, then why is it in the Manual section?
| No dual-source concern -- just edit these directly: | ||
|
|
||
| * `modules/ROOT/pages/index.adoc` -- the site cover / landing page. Replace the | ||
| abstract placeholder; leave the stamped version and phase attribute lines |
There was a problem hiding this comment.
what is the abstract placeholder?
| * `modules/ROOT/pages/index.adoc` -- the site cover / landing page. Replace the | ||
| abstract placeholder; leave the stamped version and phase attribute lines | ||
| alone. | ||
| * `MAINTAINERS.md`, `CONTRIBUTING.md`, the contributors page, the bib database. |
There was a problem hiding this comment.
I edit these? is the contribors page contributors.adoc? same with bib database? bibliography.adoc and then the .bib? is that a database?
| alone. | ||
| * `MAINTAINERS.md`, `CONTRIBUTING.md`, the contributors page, the bib database. | ||
|
|
||
| ==== Mostly automatic -- don't do these by hand |
There was a problem hiding this comment.
Mostly automatic? but they don't do these by hand? Maybe call it "Versioning" or something more descriptive of what is happening.
|
|
||
| * **Citations and `bibliography::[]` render as raw text** locally. The ASAM | ||
| bibliography extension exists only in the central playbook. Check citations in | ||
| the `make` PDF or on the dev site. |
There was a problem hiding this comment.
they won't be on the dev site until ratified though.
Signed-off-by: Bill Traynor wmat@riscv.org Signed-off-by: Bill Traynor <wmat@riscv.org>
|
OK I've pushed changes to address your review items, mostly. |
Summary
Adds a new Author Quickstart chapter that walks a spec author through bootstrapping a repository created from
docs-spec-template:.docmode.modules/ROOT/pages/) and the single-source model shared by the PDF and the Antora site..adocfiles, and the two glue files (nav.adoc+ the PDF assembler) to keep in lockstep.Wired into the book in
docs-dev-guide.adocbetween the intro and authoring chapters, and formatted to match the existing chapters ([[anchor]]+ level-2 title,===/====subsections, no per-file TOC).🤖 Generated with Claude Code