Docs review modular docs

Modular documentation review skill

Review AsciiDoc source files for Red Hat modular documentation compliance: module types, required sections, anchor IDs, and assembly structure.

Applies to: .adoc files only

For detailed module type guidance, templates, and structural rules, read asciidoc-reference.md. It contains full descriptions of each module type, required/optional parts, templates, and examples.

Concept checklist

• Title is noun phrase (NOT gerund) and uses sentence case (not Title Case)
• Anchor ID includes _{context}
• Introduction provides overview (what and why)
• No step-by-step instructions (those belong in procedures)
• Actions avoided unless highly context-dependent
• If subheadings used, first tried splitting into separate modules
• Standard subheadings (included in TOC) have anchor IDs with _{context}: [#anchor-id_{context}]
• Only valid admonition types used: NOTE, IMPORTANT, WARNING, TIP (CAUTION is not supported by the Red Hat Customer Portal)
• Additional resources focused on relevant items only
• All attribute references (e.g., {product-name}) are defined in the project

Procedure checklist

• Title uses imperative phrase (verb without -ing) and sentence case (not Title Case)
• Anchor ID includes _{context}
• Introduction explains why and where
• .Procedure section present with numbered steps
• Each step describes ONE action
• Steps use imperative form ("Click...", "Run...")
• Single-step procedures use bullet (*) not number
• No custom subheadings - only allowed sections used
• .Next steps contains links only, not instructions
• Prerequisites written as conditions, not instructions
• Only valid admonition types used: NOTE, IMPORTANT, WARNING, TIP (CAUTION is not supported by the Red Hat Customer Portal)
• Optional sections in correct order: Limitations, Prerequisites, Verification, Troubleshooting, Next steps, Additional resources
• All attribute references (e.g., {product-name}) are defined in the project

Reference checklist

• Title is noun phrase and uses sentence case (not Title Case)
• Anchor ID includes _{context}
• Introduction explains what data is provided
• Body uses tables or labeled lists
• Data logically organized (alphabetical, categorical)
• Consistent structure for similar data
• Standard subheadings (included in TOC) have anchor IDs with _{context}: [#anchor-id_{context}]
• Additional resources focused on relevant items only
• All attribute references (e.g., {product-name}) are defined in the project

Assembly checklist

• Title matches content (imperative if procedures included)
• Anchor ID does NOT include _{context}
• Context variable set: :context: my-assembly-name
• Introduction explains what user accomplishes
• Modules included with leveloffset= and appropriate level
• Next steps and Additional resources in correct order
• All attribute references (e.g., {product-name}) are defined in the project

Common violations

Issue	Wrong	Correct
Missing context	[id="my-assembly"]	[id="my-module_{context}"]
Standard subheading without anchor ID	== Subheading	[#anchor-id_{context}] then == Subheading
Procedure title	= Database Configuration	= Configure the database
Custom subheading in procedure	== Additional setup	Use allowed sections only
Instructions in Next steps	Numbered steps	Links only
Module contains module	include:: of module	Only snippets in modules
Missing leveloffset	include::mod.adoc[]	include::mod.adoc[leveloffset=+1]
Prerequisite as step	* Install JDK 11	* JDK 11 is installed.
Deep assembly nesting	Many levels of nested assemblies	Link to assemblies instead
Writers defining user stories	Writer creates user story	Product management defines user stories
Undefined attribute	{my-product} without :my-product: defined	Define in attributes file or document header

Attribute validation

Finding attribute references

Attribute references use the format {attribute-name}. Common patterns:

• {product-name} — product name
• {product-version} — version number
• {kebab-case-attr} — multi-word attributes
• {context} — built-in context variable (always valid)

Finding attribute definitions

Attributes are defined with the format :attribute-name: value. Check these locations in order:

1. Shared attributes files — typically:
   • common-attributes.adoc
   • attributes.adoc
   • _attributes.adoc
   • attributes/common-attributes.adoc
   • Files included with :includedir: or include:: at the top
2. Master/assembly files — parent files that include this module
3. Build configuration — attributes passed via command line (check build scripts)

Built-in attributes (always valid)

These AsciiDoc built-ins don't need definition checking:

• {doctype}, {backend}, {docname}, {docfile}, {docdir} — document metadata
• {author}, {email}, {revdate}, {revnumber} — revision info

Example check

File contains: Install {product-name} version {product-version}

✅ Valid if attributes file has:

:product-name: OpenShift sandboxed containers
:product-version: 1.12

❌ Invalid if no definition found — report: "Undefined attributes: {product-name}, {product-version}"

How to use

1. Verify file is .adoc format
2. Identify module type from content (concept, procedure, reference, assembly)
3. Check required parts are present using the checklists above
4. Verify anchor ID includes _{context} (except assemblies)
5. Check for common violations
6. Check for undefined attributes (see "Attribute validation" section)
7. Mark issues as required (modular violations) or [SUGGESTION]

Example invocations

• "Review this procedure module for modular docs compliance"
• "Check if this assembly follows Red Hat modular guidelines"
• "Verify the anchor IDs include context variable"
• "Do a modular docs review on modules/*.adoc"

Integrates with

• lint-with-vale: Run vale <file> for automated style linting

References

• Red Hat Modular Documentation Guide: https://redhat-documentation.github.io/modular-docs/
• Templates and detailed reference: asciidoc-reference.md