Skip to content

Document review and approval workflow; refresh docConfig, CLAUDE.md, README#118

Merged
AdamGohs merged 7 commits into
mainfrom
docs/dev/documentation-guide-review-workflow-updates
May 19, 2026
Merged

Document review and approval workflow; refresh docConfig, CLAUDE.md, README#118
AdamGohs merged 7 commits into
mainfrom
docs/dev/documentation-guide-review-workflow-updates

Conversation

@AdamGohs
Copy link
Copy Markdown
Collaborator

Description

Brings the Documentation Guide, README.md, and CLAUDE.md up to date with the review and approval workflow infrastructure that's been in place since PRs #107#117 (preview builds, lane labels, stage progression, per-individual reviewer gating, the review-workflow merge gate, the AI-assisted technical edit, and the src/docConfig.js central registry).

Auto-routed to lane:dev by content-based detection — every documentation file changed in this PR is under docs/dev/.

Affected documents

  • Documentation Guide chapters 09–15 (new)
  • Documentation Guide chapters 00, 01, 02, 03, 16 (updated)
  • README.md (rewritten — Skills + MCP sections removed; Review Workflow section added)
  • CLAUDE.md (path fix, missing npm scripts, src/docConfig.js doc, branching strategy, drop user-facing Skills section)
  • scripts/generateSidebars.js (mainIds and appendixIds updated for new chapter numbering)

Changes Made

New chapters (docs/dev/documentation-guide/)

  • 09. Review and Approval Process Overview — roles, lanes, merge gate, draft watermark
  • 10. Review Lanes — branch prefixes (docs/new/, docs/major/, docs/minor/, docs/fix/, docs/dev/) and what each lane requires
  • 11. Author Workflow — branching, opening PRs, responding to comments, the technical edit checkbox
  • 12. Reviewer Workflow — for peer reviewers and Lead Civils; how per-individual gating works
  • 13. Technical Edit — what the AI checks, severity levels, the human-editor fallback, and the full prompt verbatim so authors can see exactly what the AI is being asked to do
  • 14. Director Workflow — short, browser-only path for Director approval
  • 15. Site Admin Workflow — reviewer assignments, checkpoint deploys, merge prep, edge cases

Renames

  • 09-appendix-a-source-code-structure.mdx16-…
  • 10-appendix-b-build-process-overview.mdx17-…
  • 11-appendix-c-search-configuration.mdx18-…

URLs are unchanged because Docusaurus strips numeric prefixes.

Targeted fixes to existing chapters

  • 02-versioning-system.mdx Step 7: replaced the "commit to main / push origin main" instructions (which would fail against branch protection) with the proper branch-and-PR flow using docs/major/ / docs/minor/ prefixes
  • 03-project-structure.mdx: added src/docConfig.js to the tree as a Tier 1 contributor-edit file with full description of the active/draft flag semantics; clarified that src/draftDocs.js is now a shim
  • 16-appendix-a-source-code-structure.mdx: rewrote the draftDocs.js section to describe docConfig.js as the source of truth; replaced the outdated DocItem code example with the current version-aware watermark implementation (uses useLocation() and latestVersions.json)
  • 00-introduction.mdx: added the seven new chapters to the guide organization; rewrote the Common Contribution Workflows section to reference branch prefixes
  • 01-getting-started.mdx: updated the Appendix B cross-link for the rename

README.md

Removed the user-facing Claude Code Skills section and the MCP Servers section. The skills are still in .claude/skills/ for team members who use Claude Code, but they're not surfaced to the broader team. Added a "Review and Approval Workflow" section showing the five branch prefixes, their lanes, and the CI Build + review-workflow merge gate.

CLAUDE.md

  • Fixed docs/00-documentation-guide/docs/dev/documentation-guide/ path
  • Added missing npm run commands (report-map, image-dims, generate-toc) and noted the DOCS_MODE environment variable
  • Documented src/docConfig.js as the central active/draft registry
  • Added a branching strategy table mapping the five prefixes to their lanes
  • Dropped the duplicate "Claude Code Skills" section (the system reminder already lists available skills)
  • Replaced the "QC Reviews & Technical Edits" section with a manual prompt-template description that doesn't depend on /qc-review or /build (the latter doesn't exist as a skill)

Commits

  1. Update CLAUDE.md for review workflow and docConfig.js — also includes the appendix renames (they were staged from git mv before this commit)
  2. Fix Documentation Guide gaps for branching and docConfig.js
  3. Add seven review-process chapters to Documentation Guide
  4. Refresh README for review workflow and remove skill references

Testing Performed

  • npm run sidebars succeeds — all seven new chapters and the renamed appendices appear in the sidebar in the expected order
  • npm run build succeeds with no errors or warnings related to the changes (only the pre-existing latestVersions warning for rmc-totalrisk/verification-report which is unrelated)
  • Cross-references between renamed appendices verified — all updated to the new file numbers

Breaking Changes

  • Yes (describe below)
  • No

URLs for the renamed appendices are unchanged.

Pre-submission checklist

  • I have previewed these changes locally
  • My branch name uses one of the expected prefixes: docs/dev/
  • I have updated 00-version-history.mdx if this change warrants a version entry — N/A, the Documentation Guide does not maintain a version-history table
  • I have assigned a specific peer reviewer via the Reviewers sidebar (if known) — N/A for Lane 5 (dev docs)

Technical edit (Lane 1 only)

N/A for Lane 5.

Notes for reviewers

  • The biggest single piece of new content is chapter 13 (Technical Edit) which includes the full AI prompt verbatim. If the prompt evolves, that chapter should be updated alongside .github/ai-review/technical-editor-prompt.md.
  • Item 5 from the audit (rewriting the generic docs/dev/github-workflows/ chapters to reflect the RMC-specific workflow) was deferred for a separate discussion — those chapters appear to be intended as repo-agnostic guidance.

AdamGohs added 4 commits May 19, 2026 10:15
- Fix docs/00-documentation-guide/ -> docs/dev/documentation-guide/
- Add missing npm scripts (report-map, image-dims, generate-toc) and DOCS_MODE note
- Document src/docConfig.js as central active/draft registry
- Add branching strategy table mapping prefixes to review lanes
- Drop the user-facing Claude Code Skills section
- Replace the QC section with a manual prompt-template description
- 02-versioning-system Step 7: replace direct-to-main push with the
  branch-and-PR flow that branch protection on main requires; explain
  docs/major and docs/minor branch prefixes
- 03-project-structure: add src/docConfig.js as a Tier 1 contributor-edit
  file with full description of active/draft flag semantics; note that
  src/draftDocs.js is now a shim
- 16-appendix-a (Source Code): rewrite the draftDocs section to describe
  docConfig.js as the source of truth; replace the outdated DocItem code
  example with the current version-aware watermark implementation
Adds chapters 09-15 covering the review and approval workflow:

  09. Review and Approval Process Overview
  10. Review Lanes
  11. Author Workflow
  12. Reviewer Workflow
  13. Technical Edit (includes the full AI prompt verbatim)
  14. Director Workflow
  15. Site Admin Workflow

Companion changes:
- Update generateSidebars.js mainIds/appendixIds for new chapter numbering
- Update 00-introduction guide-organization and Common Contribution
  Workflows sections to reference new chapters and branch prefixes
- Update appendix B cross-link in 01-getting-started for the rename

The three appendices were renamed 09/10/11 -> 16/17/18 in the prior commit
because the renames were already staged via git mv. URLs are unchanged
since Docusaurus strips numeric prefixes.
- Drop the Claude Code Skills and MCP Servers sections (not everyone on
  the team uses Claude; skill listing belongs in .claude/skills/ only)
- Add a Review and Approval Workflow section showing the five branch
  prefixes, their lanes, and required reviews
- Note that branch protection requires CI Build and review-workflow
  status checks before merge
- Point at Documentation Guide chapters 09-15 for full workflow details
@AdamGohs AdamGohs requested a review from a team as a code owner May 19, 2026 14:16
@github-actions
Copy link
Copy Markdown

📋 Assigned reviewers for this PR

  • Peer reviewer(s): not assigned
  • Lead Civil reviewer(s): not assigned
  • Technical editor(s): not assigned
  • Director reviewer(s): not assigned

The first approval from any assigned reviewer at the current stage advances the PR. Approvals from non-assigned reviewers are logged but do not advance the stage.

@github-actions github-actions Bot added lane:dev Dev docs (docs/dev/**) — admin self-merge, no review required stage:ready-to-merge All reviews complete, ready for final merge labels May 19, 2026
@github-actions
Copy link
Copy Markdown

📋 Lane: Dev Doc

No formal review required.

@usace-rmc/docs-admin please review, merge, and approve the deploy.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 19, 2026

📄 Preview deployed for commit 54ebe42

https://usace-rmc.github.io/RMC-Software-Documentation-Previews/pr-118/

This preview updates automatically when new commits are pushed. Deleted when the PR closes.

AdamGohs added 2 commits May 19, 2026 11:46
The chapter is now structured around the eight steps an author takes to
publish a brand-new document via Lane 1:

  1. Create a branch (new)
  2. Determine folder location
  3. Create folder structure
  4. Add supporting assets
  5. Create MDX files
  6. Register the document in src/docConfig.js (new)
  7. Test locally
  8. Open a pull request (replaces the old 'Contact Site Administrator'
     step — the PR is now the coordination point and the workflow
     handles the deploy)

The two surviving examples are trimmed to the new workflow. Example 3
(new version of existing document) was removed because new versions
go through Lane 2 or Lane 3 in docs/dev/documentation-guide/02-versioning-system.mdx, not this chapter.
- Convert every 'you' to third-person voice describing role behavior
  (e.g., 'The author addresses each comment' rather than 'You address
  each comment'). The chapters now read as reference material for any
  team member, not as instructions addressed to the role-holder.
- Replace markdown tables with TableVerticalNoRef so styling matches
  the rest of the site (zebra striping, alt text, responsive scroller).
- Replace ordered/numbered procedure lists with ProcessList components
  so visual treatment matches existing chapters.
@github-actions
Copy link
Copy Markdown

⚠️ New commits pushed after PR reached stage:ready-to-merge

@usace-rmc/docs-admin please eyeball the new changes before merging — the bot has re-set the review-workflow status to success, but this bypasses any incremental review of the latest push.

Add a tip admonition in Step 1 pointing readers to Review Lanes so they
can see all five branch prefixes available and pick the right one. Also
redirects readers who actually want to do a revision (not a new doc)
to the Versioning System chapter.
@github-actions
Copy link
Copy Markdown

⚠️ New commits pushed after PR reached stage:ready-to-merge

@usace-rmc/docs-admin please eyeball the new changes before merging — the bot has re-set the review-workflow status to success, but this bypasses any incremental review of the latest push.

@AdamGohs AdamGohs merged commit 41122ac into main May 19, 2026
4 checks passed
@AdamGohs AdamGohs deleted the docs/dev/documentation-guide-review-workflow-updates branch May 19, 2026 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lane:dev Dev docs (docs/dev/**) — admin self-merge, no review required stage:ready-to-merge All reviews complete, ready for final merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant