@inditextech/docouture-cli 0.1.0-SNAPSHOT.40.1

package/build/templates/agent-support/.opencode/skills/writing-docs-pages/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: writing-docs-pages
+description: "How to author AsciiDoc content in this Antora documentation site — the content tree, xref: references, nav.adoc, admonitions, code blocks, and this site's own custom blocks (tabs, cards, accordion, feature-tabs, cta, label:/mono: macros). USE WHEN writing or editing a .adoc page, adding a page to the nav, fixing a broken xref, or reaching for a block like tabs/cards/accordion. EXAMPLES: 'add a page', 'my xref doesn't resolve', 'the build fails on a warning', 'add tabs for pnpm/npm/yarn commands', 'group these FAQ items', 'add a card grid'."
+---
+
+# Writing docs pages
+
+Every page here is AsciiDoc, parsed by **Asciidoctor** and orchestrated by **Antora**.
+Antora restricts and reinterprets parts of the language (includes, xrefs, image paths);
+where this skill and the upstream Asciidoctor docs differ, follow this skill.
+
+- `reference/language-basics.md` — the AsciiDoc language itself: document structure,
+  blocks, text formatting, lists, links/xrefs, images, source blocks, admonitions, tables,
+  includes, conditionals, substitutions, attributes — plus a URL index into
+  `https://docs.asciidoctor.org/asciidoc/latest/` for anything not covered.
+- `reference/docouture-blocks.md` — this site's own custom blocks, registered via
+  `@inditextech/docouture-asciidoc-extensions` (see `antora-playbook.yml`'s
+  `asciidoc.extensions`): `[tabs]`, `[cards]`, `[accordion]`, `[feature-tabs]`, `[cta]`,
+  `label:`/`mono:` inline macros, and a few table/video sizing attributes.
+
+For the home page vs. content page patterns, mono- vs. multi-module sites, and the
+playbook/component-descriptor mechanics, see the `docs-internals` skill.
+
+## Where content lives
+
+```
+docs/src/
+  antora.yml                  component descriptor: name, title, version, nav
+  modules/
+    ROOT/                     the default module; its name is omitted from resource IDs
+      nav.adoc                the navigation tree for this module
+      pages/*.adoc            one page per file — these become site URLs
+```
+
+Only `pages/` exists in a freshly scaffolded site. The other family directories are
+created when first needed, with these exact names — Antora keys off them and ignores
+anything else:
+
+| directory      | family        | referenced as                  |
+| -------------- | ------------- | ------------------------------ |
+| `pages/`       | `page$`       | `xref:name.adoc[]`             |
+| `partials/`    | `partial$`    | `include::partial$name.adoc[]` |
+| `examples/`    | `example$`    | `include::example$name.json[]` |
+| `images/`      | `image$`      | `image::name.png[]`            |
+| `attachments/` | `attachment$` | `xref:attachment$file.pdf[]`   |
+
+## Resource IDs
+
+Antora addresses content by resource ID, not by relative path:
+
+```
+version@component:module:family$relative/path.adoc#fragment
+```
+
+Everything left of the filename is optional and defaults to the current page's context.
+Inside the same module:
+
+| reference                        | means                                                                        |
+| -------------------------------- | ---------------------------------------------------------------------------- |
+| `xref:index.adoc[Home]`          | a page in the same module                                                    |
+| `xref:guide/setup.adoc[]`        | a page in a subdirectory of `pages/` — empty text uses the target's title    |
+| `xref:other-module:index.adoc[]` | a page in another module — only in a multi-module site, see `docs-internals` |
+| `xref:index.adoc#install[]`      | a fragment on another page                                                   |
+| `include::partial$intro.adoc[]`  | a partial from the same module                                               |
+
+`../` path traversal between pages is not how this works — a page one directory deep
+still addresses its sibling as `xref:guide/other.adoc[]`, module-relative, never
+file-relative.
+
+## Where a change goes
+
+| you want to                    | do                                                                                                                                             |
+| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| add a page                     | create `docs/src/modules/<module>/pages/name.adoc` **and** add an `xref:` to that module's `nav.adoc`                                          |
+| add a section to the nav       | edit `nav.adoc` — nesting is list depth (`*`, `**`, `***`); a bare, unlinked list item can group xrefs under a heading with no page of its own |
+| reuse a chunk of prose         | `docs/src/modules/<module>/partials/name.adoc`, included as `partial$name.adoc`                                                                |
+| add an image                   | `docs/src/modules/<module>/images/name.png`, referenced as `image::name.png[Alt]`                                                              |
+| set a site-wide attribute      | `asciidoc.attributes` in `antora-playbook.yml`                                                                                                 |
+| set a component-wide attribute | `asciidoc.attributes` in `docs/src/antora.yml`                                                                                                 |
+| set a page-scoped attribute    | an attribute entry in the page header, above the first blank line                                                                              |
+
+## Constraints that fail silently
+
+- **A warning is a build failure.** `antora-playbook.yml` sets
+  `runtime.log.failure_level: warn`. A broken xref, a missing include target, an
+  undefined attribute reference or a bad image path exits non-zero.
+- **A page missing from `nav.adoc` still builds.** It publishes at its URL, renders with
+  an empty navigation context and is reachable only by direct link. Nothing warns.
+- **`include::` cannot read arbitrary paths.** Antora installs its own include processor
+  that resolves targets against the content catalog, so only the family forms
+  (`partial$`, `example$`, page IDs) work. A filesystem path fails at build time.
+- **Attribute references are not substituted inside verbatim blocks.** `{version}`
+  inside `----`/`....` renders literally unless the block carries `subs=attributes+`.
+- **Unconstrained formatting needs doubled marks.** `**bold**` mid-word, `__italic__`
+  mid-word. The single-mark form adjacent to a word character is not formatting at all.
+- **A cross-module xref only resolves inside a multi-module site**, and only once both
+  modules are listed under `docs/src/antora.yml`'s `nav:` — see `docs-internals`.
+
+## Page attributes the UI reads
+
+| attribute                                             | effect                                                                                                                                                  |
+| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `description`                                         | hero excerpt (below the title) AND `<meta name="description">`                                                                                          |
+| `page-tags`                                           | comma-separated; one label pill each in the hero                                                                                                        |
+| `page-action` / `page-action-url`                     | primary hero button — renders only when BOTH are set                                                                                                    |
+| `page-action-secondary` / `page-action-secondary-url` | secondary hero button, same rule                                                                                                                        |
+| `page-hero-image` / `page-hero-image-alt`             | hero illustration                                                                                                                                       |
+| `page-nav-module`                                     | which module's nav tree the side menu shows for this page — set on `ROOT`'s own landing page in a multi-module site, since `ROOT` has no nav of its own |
+| `page-layout: home`                                   | the marketing home-page layout — see `docs-internals`'s page-patterns reference                                                                         |
+| `page-role: -hero`                                    | suppresses the hero entirely                                                                                                                            |
+| `page-role: -toc`                                     | suppresses the right-hand table of contents                                                                                                             |
+| `page-pagination`                                     | enables the previous/next footer links                                                                                                                  |

package/build/templates/agent-support/.opencode/skills/writing-docs-pages/reference/docouture-blocks.md

@@ -0,0 +1,170 @@
+# This site's custom blocks
+
+Registered by `@inditextech/docouture-asciidoc-extensions`, listed under
+`antora-playbook.yml`'s `asciidoc.extensions`. Everything below is authored content with
+no plain-AsciiDoc equivalent — the extension only emits markup, all styling comes from
+the UI bundle's CSS. Every block here degrades to plain, readable HTML with JavaScript
+off (sequential sections for tabs, `<details>` for accordions, real `<a href>`s).
+
+## Tabs
+
+A switcher for equivalent alternatives — package-manager commands, config formats, etc.
+
+```adoc
+[tabs]
+--
+[tab,label="pnpm"]
+****
+[source,bash]
+----
+pnpm add some-package
+----
+****
+
+[tab,label="npm"]
+****
+[source,bash]
+----
+npm install some-package
+----
+****
+--
+```
+
+`[tabs]` is an open block (`--`); each `[tab,label="…"]` child is its own sidebar block
+(`****`), never an example block (`====`) — this lets a tab hold anything, including a
+titled source block or another nested block, without a delimiter-nesting trap.
+
+## Cards
+
+A grid of entry-point cards — landing "Get started" rows, or a content page pointing at
+related pages.
+
+```adoc
+[cards,type=image-square,columns="1 s:2 m:4",width=container]
+====
+[card,subheader="Category"]
+.xref:module:page.adoc[Card title]
+--
+image::card-image.png["Alt text"]
+
+Card description.
+--
+
+[card]
+.xref:module:other.adoc[No-image card]
+A card with just a title and description — no image, no open block needed.
+====
+```
+
+- `type`: `no-image` (default), `image-landscape`, `image-square`, `image-portrait`.
+- `columns`: base count, then breakpoint-prefixed overrides (`s:`, `m:`, `l:`), e.g.
+  `"1 s:2 m:4"` — max 4.
+- `width`: `content` (default) or `container`.
+- The block title (`.xref:...[Title]`) carries the link — the whole card is that link.
+- A card with an image needs the open-block form (`--`/`--`); a text-only card can be a
+  plain paragraph under `[card]`.
+
+## Accordion (grouped FAQ)
+
+Groups a run of `[%collapsible]` blocks with proper `role=group` semantics and,
+optionally, single-open behaviour — the native `[%collapsible]` on its own (see
+`language-basics.md`) still works for one-off collapsibles; group them with `[accordion]`
+when several belong together, e.g. an FAQ section.
+
+```adoc
+[accordion%single-open,aria-label="Frequently asked questions"]
+--
+.Question one?
+[%collapsible]
+====
+Answer one.
+====
+
+.Question two?
+[%collapsible]
+====
+Answer two.
+====
+--
+```
+
+- `%single-open` (an option, like `%collapsible`'s own) makes opening one item close the
+  others; omit it and items are independent (the default).
+- Give the group an `aria-label=` (or a block `.Title`) — a `role=group` with no
+  accessible name is flagged.
+- `[accordion]` is an open block (`--`) so its `[%collapsible]` children stay ordinary
+  `====` blocks, unchanged from how they'd read standalone.
+
+## Feature tabs
+
+A media-plus-prose switcher for a handful of top-level capabilities — used on the home
+page (see the `docs-internals` skill's `reference/page-patterns.md`).
+
+```adoc
+[feature-tabs]
+====
+[feature,label="Capability one"]
+--
+image::feature-one.png[Alt text]
+
+Prose describing this capability.
+
+[.cta]
+xref:module:page.adoc[Learn more]
+--
+
+[feature,label="Capability two"]
+--
+image::feature-two.png[Alt text]
+
+Prose describing this capability.
+--
+====
+```
+
+## CTA
+
+A single call-to-action block — prose plus one prominent link.
+
+```adoc
+[cta]
+====
+Prose making the case for the action.
+
+[.primary]
+https://example.com/signup[Get started]
+====
+```
+
+## Inline macros: `label:` and `mono:`
+
+```adoc
+label:red[Blocked]        a coloured pill — variants: white, grey, red, orange, green,
+                           blue, purple, pink, teal (grey is the default, label:[Text])
+mono:[className]          plain monospaced text with no code-chip styling — for a
+                           table cell whose entire content is a bare name/token
+```
+
+`` `backtick code` `` (see `language-basics.md`) keeps its usual code-chip styling;
+`mono:[]` is the deliberate opt-out for a column where every cell is a token and the chip
+would just be noise.
+
+## Table and video sizing attributes
+
+```adoc
+[table-width=720px,cols="1,1"]        |=== an absolute CSS width, bypassing Asciidoctor's
+|===                                   own width= (which is percentage-only, clamped 1-100)
+
+[cols="1,3,2",nowrap-cols="1,2"]      pins white-space: nowrap to specific columns
+|===
+...
+|===
+
+video::demo[youtube,640,360]          sets both dimensions and locks the aspect ratio
+                                        at any narrower viewport (no CSS-only fix exists
+                                        for an iframe/video the way there is for <img>)
+```
+
+These aren't new blocks, just extra attributes Asciidoctor's own table/video macros don't
+support natively — safe to ignore if you never need an absolute width or a nowrap column.

package/build/templates/agent-support/.opencode/skills/writing-docs-pages/reference/language-basics.md

@@ -0,0 +1,402 @@
+# AsciiDoc language basics
+
+Ordered by how often it comes up, not by upstream nav order. Antora-specific behaviour is
+called out inline; everything else is plain AsciiDoc as Asciidoctor implements it.
+
+Upstream base URL for every link below: `https://docs.asciidoctor.org/asciidoc/latest/`
+
+## Document structure
+
+A page is a header (optional), then blocks. The header is everything above the first
+blank line.
+
+```adoc
+= Page Title
+:description: Shown in the meta description and in search results.
+:page-tags: one, two
+
+Preamble paragraph — content before the first section title.
+
+== First Section
+
+Body.
+
+=== Nested Section
+```
+
+- **One level-0 title per page.** `=` is the document title; `==` is the first real
+  section. A second `=` is an error in `doctype: article` (the default).
+- Section levels must not skip: `==` then `====` is a warning, and a warning fails the
+  build here.
+- Attribute entries (`:name: value`) in the header apply to the whole page. Placed in the
+  body they apply from that point on.
+- `page-*` attributes are Antora's convention: they are lifted onto the UI model and are
+  available to templates rather than to the content.
+
+`document-structure/`, `document/header/`, `sections/titles-and-levels/`
+
+## Blocks
+
+A block is delimited by four or more repeated characters, or implied by a blank line
+(paragraph).
+
+| delimiter | block                                   |
+| --------- | --------------------------------------- |
+| `----`    | listing / source                        |
+| `....`    | literal                                 |
+| `====`    | example (and, with a style, admonition) |
+| `****`    | sidebar                                 |
+| `____`    | quote                                   |
+| `--`      | open (exactly two hyphens)              |
+| `\|===`   | table                                   |
+| `++++`    | passthrough                             |
+| `////`    | comment                                 |
+
+Metadata sits directly above the delimiter, no blank line between:
+
+```adoc
+.A block title
+[#custom-id.role-one.role-two%option,attr=value]
+----
+content
+----
+```
+
+- `.Title` — block title.
+- `#id` — the ID, in the attribute list shorthand.
+- `.role` — a CSS class. Repeatable.
+- `%option` — an option, e.g. `%collapsible`, `%header`, `%autowidth`.
+- The first positional attribute is the **block style**, which can make one delimiter
+  behave as another (`[quote]` on `====`, `[source]` on `----`). This is _block
+  masquerading_.
+
+`blocks/`, `blocks/delimited/`, `attributes/element-attributes/`, `blocks/masquerading/`
+
+## Text formatting
+
+| markup                          | result                  | note                               |
+| ------------------------------- | ----------------------- | ---------------------------------- |
+| `*bold*` / `**bold**`           | bold                    | double form required mid-word      |
+| `_italic_` / `__italic__`       | italic                  | same                               |
+| `` `mono` ``                    | monospace               | subs still apply inside            |
+| `` `+literal+` ``               | monospace, no subs      | use for anything with `{}` or `<>` |
+| `#highlight#` / `##highlight##` | mark                    |                                    |
+| `[.role]#text#`                 | span with a class       | the general escape hatch           |
+| `~sub~` / `^sup^`               | subscript / superscript |                                    |
+
+The single-mark ("constrained") form only applies when the marks sit at a word boundary.
+`hard*coded*text` is literal asterisks; `hard**coded**text` is bold. This is the single
+most common formatting surprise.
+
+`text/`, `text/troubleshoot-unconstrained-formatting/`
+
+## Lists
+
+```adoc
+* first
+* second
+** nested
++
+Attached paragraph — the `+` continuation binds it to the item above.
+
+. ordered
+. ordered
+
+term:: definition
+another term:: definition
+
+* [ ] unchecked task
+* [x] checked task
+```
+
+- Nesting is marker repetition (`*`, `**`, `***`), not indentation.
+- A blank line alone does not end a list; adjacent non-list content does. Two adjacent
+  lists that should stay separate need `//-` (an empty comment line) between them.
+- Anything other than a plain paragraph attached to an item needs `+` on its own line
+  before it — including nested blocks, source blocks and admonitions.
+
+`lists/unordered/`, `lists/ordered/`, `lists/description/`, `lists/continuation/`,
+`lists/checklist/`, `lists/separating/`
+
+## Links and cross references
+
+```adoc
+https://example.com[Link text]
+https://example.com[Link text^]              open in a new tab
+link:https://example.com[Text]               explicit macro; needed when the URL is not bare
+mailto:a@example.com[Mail us]
+
+xref:page.adoc[Text]                          Antora resource ID — see writing-docs-pages SKILL.md
+xref:page.adoc#section-id[Text]
+xref:#local-section[Text]                     same page
+<<local-section,Text>>                        same page, alternate form
+```
+
+- Empty xref text (`xref:page.adoc[]`) renders the target page's title. Prefer it — it
+  stays correct when the title changes.
+- A URL containing `[`, `]` or a trailing `.` needs the `link:` macro or attribute
+  wrapping.
+- Antora validates every xref. An unresolved one fails the build.
+
+`macros/links/`, `macros/xref/`, `macros/inter-document-xref/`
+
+## Images and icons
+
+```adoc
+image::name.png[Alt text,640,480]             block image
+image:name.png[Alt text,24,24]                inline image (single colon)
+image::name.png[Alt,link=https://example.com]
+icon:check[]                                  font icon — icons=font is set
+kbd:[Ctrl+C]                                  requires experimental (it is set)
+btn:[Save]
+menu:File[Save As]
+```
+
+Antora resolves `image::name.png[]` against the module's `images/` directory. Do not
+write `../images/name.png` and do not set `:imagesdir:` — Antora manages it.
+
+`macros/images/`, `macros/icons/`, `macros/keyboard-macro/`, `macros/ui-macros/`
+
+## Source blocks
+
+```adoc
+[source,typescript]
+----
+const answer = 42
+----
+
+[source,json,highlight=2..3]
+----
+{ "a": 1 }
+----
+```
+
+- `source-highlighter=highlight.js` is Antora's default and is in force here. The
+  language token must be one highlight.js knows.
+- `[,typescript]` (empty first positional) is shorthand for `[source,typescript]`.
+- Callouts mark lines with `<1>` and are explained in a following colon list:
+
+```adoc
+[source,js]
+----
+const x = 1 // <1>
+----
+<1> Explanation.
+```
+
+- Attribute references are **not** substituted inside a source block unless the block
+  carries `subs=attributes+`.
+
+`verbatim/source-blocks/`, `verbatim/callouts/`, `verbatim/highlight-lines/`
+
+## Admonitions
+
+```adoc
+NOTE: One-line form.
+
+[WARNING]
+====
+Multi-line form. Any blocks can go inside.
+====
+```
+
+Five types only: `NOTE`, `TIP`, `IMPORTANT`, `WARNING`, `CAUTION`. A custom type needs a
+role plus CSS.
+
+`blocks/admonitions/`
+
+## Tables
+
+```adoc
+.Optional title
+[cols="1,2,1",options="header",%autowidth]
+|===
+|Column A |Column B |Column C
+
+|cell
+|cell
+|cell
+|===
+```
+
+- `cols` takes proportional widths (`1,2,1`), percentages (`25%,50%,25%`), or a repeat
+  (`3*` = three equal columns).
+- A column or cell specifier prefixes the width: alignment `<` `^` `>` (horizontal),
+  `.<` `.^` `.>` (vertical), and a style suffix:
+
+| suffix | cell content treated as                          |
+| ------ | ------------------------------------------------ |
+| `a`    | AsciiDoc — the only way to nest blocks in a cell |
+| `l`    | literal                                          |
+| `m`    | monospace                                        |
+| `h`    | header                                           |
+| `s`    | strong                                           |
+| `d`    | default (prose)                                  |
+
+- Spans: `2+|` spans two columns, `.3+|` three rows, `2.3+|` both. `3*|` duplicates a
+  cell across three columns.
+- A cell containing a `|` needs it escaped as `\|`.
+
+`tables/build-a-basic-table/`, `tables/format-column-content/`, `tables/span-cells/`,
+`tables/table-ref/`
+
+## Includes
+
+```adoc
+include::partial$intro.adoc[]
+include::example$config.json[]
+include::partial$file.adoc[tag=setup]
+include::example$app.ts[lines=10..20]
+include::partial$chapter.adoc[leveloffset=+1]
+include::example$snippet.js[indent=0]
+```
+
+Tagged regions are marked in the _included_ file with comments in that file's own comment
+syntax:
+
+```js
+// tag::setup[]
+const app = createApp()
+// end::setup[]
+```
+
+- `leveloffset=+1` demotes every section title in the included file — required when
+  including a file that has its own `=` title.
+- `indent=0` normalises leading whitespace, so a tagged region extracted from indented
+  code renders flush left.
+- Antora restricts targets to the resource families. `include::../other.adoc[]` and
+  `include::https://…[]` do not work.
+
+`directives/include/`, `directives/include-tagged-regions/`,
+`directives/include-lines/`, `directives/include-with-leveloffset/`
+
+## Conditionals
+
+```adoc
+ifdef::experimental[]
+Shown when the attribute is set.
+endif::[]
+
+ifndef::backend-html5[]
+Shown when it is not set.
+endif::[]
+
+ifeval::[{sectnumlevels} > 2]
+Shown when the expression is true.
+endif::[]
+```
+
+`ifdef::attr-one,attr-two[]` is OR; `ifdef::attr-one+attr-two[]` is AND. The single-line
+form `ifdef::attr[content]` exists for one line of content.
+
+`directives/conditionals/`, `directives/ifdef-ifndef/`, `directives/ifeval/`
+
+## Substitutions
+
+Applied to normal blocks in this fixed order:
+
+1. `specialchars` — `<`, `>`, `&` escaped
+2. `quotes` — the formatting marks above
+3. `attributes` — `{name}` references resolved
+4. `replacements` — `(C)`, `--`, `...` and friends
+5. `macros` — link, image, icon, xref
+6. `post_replacements` — the `+` line break
+
+Verbatim blocks (`----`, `....`) get `specialchars` and `callouts` only. Passthrough gets
+nothing.
+
+Override per block or per inline span:
+
+```adoc
+[subs="attributes+"]                incremental — add to the defaults
+[subs="+macros,-callouts"]          add one, remove another
+[subs="verbatim,quotes"]            absolute — replaces the defaults entirely
+```
+
+Escape a single substitution with a leading backslash (`\{attr}`, `\*not bold*`), or use
+an inline passthrough:
+
+```adoc
++literal text+                       no subs
+pass:[<b>raw</b>]                    no subs, raw output
+pass:attributes[{version}]           only the listed subs
+```
+
+`subs/`, `subs/apply-subs-to-blocks/`, `subs/prevent/`, `pass/`
+
+## Attributes
+
+```adoc
+:name: value
+:name!:                              unset
+:!name:                              unset, alternate form
+:name: {other} suffix                references resolve at definition time
+```
+
+Precedence, highest first: CLI/API → playbook `asciidoc.attributes` → `antora.yml` →
+page header. A playbook attribute ending in `@` becomes _soft-set_ and can be overridden
+by a page; without `@` it cannot.
+
+`attributes/document-attributes/`, `attributes/assignment-precedence/`,
+`attributes/document-attributes-ref/`
+
+## Other blocks worth knowing
+
+```adoc
+[%collapsible]
+====
+Rendered as a <details> element.
+====
+
+[quote,Author,Source]
+____
+Quotation.
+____
+
+[sidebar]                            or ****
+****
+Aside content.
+****
+
+--
+An open block — groups content with no semantics of its own. The usual way to
+attach several blocks to one list item.
+--
+
+toc::[]                              macro TOC; needs :toc: in the header
+```
+
+`blocks/collapsible/`, `blocks/blockquotes/`, `blocks/sidebars/`, `blocks/open-blocks/`,
+`toc/`
+
+## URL index — the long tail
+
+Not summarised above; fetch when needed.
+
+| topic                                                         | page                                    |
+| ------------------------------------------------------------- | --------------------------------------- |
+| Syntax quick reference                                        | `syntax-quick-reference/`               |
+| Document attributes reference (every built-in)                | `attributes/document-attributes-ref/`   |
+| Character replacements (`(C)`, `->`, …)                       | `attributes/character-replacement-ref/` |
+| Text span and built-in roles                                  | `text/text-span-built-in-roles/`        |
+| Quotation marks and apostrophes                               | `text/quotation-marks-and-apostrophes/` |
+| Footnotes                                                     | `macros/footnote/`                      |
+| Audio and video                                               | `macros/audio-and-video/`               |
+| SVG images                                                    | `macros/image-svg/`                     |
+| Image sizing / positioning reference                          | `macros/image-ref/`                     |
+| STEM (equations, formulas)                                    | `stem/`                                 |
+| Docinfo files                                                 | `docinfo/`                              |
+| Book parts, chapters, appendix, glossary, bibliography, index | `sections/styles/`                      |
+| Special section titles and numbering                          | `sections/special-section-titles/`      |
+| Verses                                                        | `blocks/verses/`                        |
+| CSV / TSV / DSV table data                                    | `tables/data-format/`                   |
+| Nested tables                                                 | `tables/nested/`                        |
+| Hard line breaks                                              | `blocks/hard-line-breaks/`              |
+| Discrete headings                                             | `blocks/discrete-headings/`             |
+| Preamble and lead style                                       | `blocks/preamble-and-lead/`             |
+| AsciiDoc vs Markdown                                          | `asciidoc-vs-markdown/`                 |
+| Glossary of terms                                             | `glossary/`                             |
+| FAQ                                                           | `faq/`                                  |
+
+Antora's own layer — resource IDs, families, nav, page attributes, the content catalog —
+is documented separately at `https://docs.antora.org/antora/latest/`.