Skip to content

[Content] Show review-stage draft wording in PR previews - #148

Merged
AdamGohs merged 1 commit into
mainfrom
fix/preview-draft-notice-wording
Oct 15, 2026
Merged

AdamGohs merged 1 commit into
mainfrom
fix/preview-draft-notice-wording

Conversation

@AdamGohs

Copy link
Copy Markdown
Collaborator

Description

The draft strip and the printed-page draft band always read "This document is pending final approval by the RMC Director." That is accurate for a draft published to the main site, which is waiting on the Director stage. PR previews, though, show drafts that are still in peer, Lead Civil, and technical review, so the message tells reviewers the document is past their stage.

Preview builds now show:

Draft for review. This document has not been approved for publication.

The main site keeps the Director wording.

  • docusaurus.config.js exposes the existing DOCUSAURUS_IS_PREVIEW build flag as customFields.isPreview.
  • src/components/DraftNotice.js chooses the strip and print-band text from that flag.

This applies to every draft document on the site, not just one.

Document scope

  • Document: None — site/code change.
  • Document location (doc_location, or -): -

Related issue(s)

None.

Validation

  • I previewed the change locally or through the PR preview
  • I ran the checks appropriate to this change
  • I updated version history when the document revision warrants it (not applicable)

Built the site both ways and checked a draft document (LifeSim Applications Guide). The production build shows only the Director wording; a preview build (DOCUSAURUS_IS_PREVIEW=true with a preview base URL) shows only the review wording, on all of that document's pages. npm run test:review passes.

Review notes

Code-only: /review classify code -. This PR's own preview shows the new wording on existing drafts such as the LifeSim Applications Guide.

The draft strip and print band always said the document is pending RMC
Director approval. That is true for a draft published to the main site,
but PR previews show drafts still in peer, Lead Civil, and technical
review, where the message misleads reviewers. Preview builds now read
"Draft for review. This document has not been approved for publication."
while the main site keeps the Director wording.
@AdamGohs
AdamGohs requested a review from a team as a code owner October 15, 2026 18:41
@AdamGohs
AdamGohs deployed to review-control October 15, 2026 18:41 — with GitHub Actions Active
@AdamGohs

Copy link
Copy Markdown
Collaborator Author

/review classify code -

@usace-rmc-docs-review

usace-rmc-docs-review Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Review workflow

Purpose: content · Classification: code
Document: not selected

Stage Reviewer Status

Next: Administrator: inspect and merge after CI passes

Completed stages persist until an administrator restarts them. Replies and resolved threads are not approval requirements. Use /review ready to request re-review within an active stage.

This PR has merged. Production deployment follows the main approval process.

@usace-rmc-docs-review usace-rmc-docs-review Bot changed the title Show review-stage draft wording in PR previews [Content] Show review-stage draft wording in PR previews Oct 15, 2026
@usace-rmc-docs-review usace-rmc-docs-review Bot added purpose:content stage:ready-to-merge All reviews complete, ready for final merge lane:code labels Oct 15, 2026
@usace-rmc-docs-review

Copy link
Copy Markdown

@USACE-RMC/docs-admin — review requirements are satisfied. Inspect the changes, fill document attribution manually, and merge when CI passes.

@AdamGohs
AdamGohs merged commit 729fee6 into main Oct 15, 2026
4 checks passed
@AdamGohs
AdamGohs deleted the fix/preview-draft-notice-wording branch October 15, 2026 18:54
@AdamGohs
AdamGohs deployed to review-control October 15, 2026 18:54 — with GitHub Actions Active

This branch was successfully deployed

1 active deployment
review-control — 4acb3f62 Deployed Oct 15, 2026 by AdamGohs via control #439
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lane:code purpose:content 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