Skip to content

Add Author Quickstart chapter for docs-spec-template#155

Merged
Bill Traynor (wmat) merged 2 commits into
mainfrom
author-quickstart
Jul 16, 2026
Merged

Add Author Quickstart chapter for docs-spec-template#155
Bill Traynor (wmat) merged 2 commits into
mainfrom
author-quickstart

Conversation

@wmat

Copy link
Copy Markdown
Collaborator

Summary

Adds a new Author Quickstart chapter that walks a spec author through bootstrapping a repository created from docs-spec-template:

  • Renaming the template (component name/title, PDF assembler, Makefile pointer, bib database) and confirming .docmode.
  • Where chapter content lives (modules/ROOT/pages/) and the single-source model shared by the PDF and the Antora site.
  • Why you never duplicate .adoc files, and the two glue files (nav.adoc + the PDF assembler) to keep in lockstep.
  • Manual steps (numbering rule, site registration, release-time version stamping) vs. what's automatic.
  • The local build and preview loop, including expected local-preview gaps.

Wired into the book in docs-dev-guide.adoc between 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

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>
Comment thread src/author-quickstart.adoc Outdated

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

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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**

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

they do? level-0 title? that is an h1, right? pretty sure they are all h2s

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add copyright.adoc after this. or is this something that we will have to add later because it might muck up the PDF?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add copyright in the next PR.

Comment thread src/author-quickstart.adoc Outdated
<3> Front matter.
<4> Back matter.
<5> Bibliography database.
<6> PDF assembler -- glue, not content (see below).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

glue again

Comment thread src/author-quickstart.adoc Outdated
(`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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you are using lockstep too much. Maybe "at the same time" this time?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough. I replaced one and left one.

Comment thread src/author-quickstart.adoc Outdated

==== Every time you change chapter structure

Update the **central playbook's numbering rule.** This is the easiest step to

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this won't happen until after ratification, yes?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread src/author-quickstart.adoc Outdated
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

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if this is automated, then why is it in the Manual section?

Comment thread src/author-quickstart.adoc Outdated
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

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the abstract placeholder?

Comment thread src/author-quickstart.adoc Outdated
* `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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I edit these? is the contribors page contributors.adoc? same with bib database? bibliography.adoc and then the .bib? is that a database?

Comment thread src/author-quickstart.adoc Outdated
alone.
* `MAINTAINERS.md`, `CONTRIBUTING.md`, the contributors page, the bib database.

==== Mostly automatic -- don't do these by hand

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>
@wmat

Copy link
Copy Markdown
Collaborator Author

OK I've pushed changes to address your review items, mostly.

@wmat
Bill Traynor (wmat) merged commit 7efc639 into main Jul 16, 2026
5 checks passed
@wmat
Bill Traynor (wmat) deleted the author-quickstart branch July 16, 2026 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants