Skip to content

[Content] Turn on web application home cards and nav links once a product has an active document - #147

Merged
AdamGohs merged 1 commit into
mainfrom
fix/web-app-links-follow-registry
Oct 15, 2026
Merged

AdamGohs merged 1 commit into
mainfrom
fix/web-app-links-follow-registry

Conversation

@AdamGohs

Copy link
Copy Markdown
Collaborator

Description

The Web Applications and Services home cards and header nav entries (DST, System Response Library, LST, RRFT) were hard-coded as Coming Soon. That left a product's page unreachable even after one of its documents went active, including in PR previews: the previews for #145 and #146 have no way to reach the System Response Library page.

They now follow src/docConfig.js. A new hasActiveDocs(category, software) helper turns a product's card and nav link on as soon as any of its documents is active; otherwise the product stays Coming Soon.

Production is unchanged by this PR, since no Web Applications and Services document is active on main yet.

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)

DOCS_MODE=prod npm run build passes and npm run test:review passes. Checked hasActiveDocs against main (all four products off) and against the BEP branch's registry (System Response Library on, the rest off).

Review notes

Code-only: /review classify code -. After it merges, main will be merged into #145 and #146 so their previews link through.

…n active document

The Web Applications and Services cards and nav entries were hard-coded as
Coming Soon, so a product's page was unreachable even after one of its
documents went active (including in PR previews). They now follow
src/docConfig.js: a product links to its page as soon as any of its
documents is active.
@AdamGohs
AdamGohs requested a review from a team as a code owner October 15, 2026 18:15
@AdamGohs
AdamGohs deployed to review-control October 15, 2026 18:15 — with GitHub Actions Active
@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 Turn on web application home cards and nav links once a product has an active document [Content] Turn on web application home cards and nav links once a product has an active document Oct 15, 2026
@usace-rmc-docs-review usace-rmc-docs-review Bot added purpose:content stage:needs-lane Awaiting admin to assign a review lane labels Oct 15, 2026
@usace-rmc-docs-review

Copy link
Copy Markdown

@USACE-RMC/docs-admin — classify this PR with /review classify <lane> <document|->. Builds run while classification is pending.

@AdamGohs

Copy link
Copy Markdown
Collaborator Author

/review classify code -

@usace-rmc-docs-review usace-rmc-docs-review Bot added stage:ready-to-merge All reviews complete, ready for final merge lane:code and removed stage:needs-lane Awaiting admin to assign a review lane 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 472e210 into main Oct 15, 2026
4 checks passed
@AdamGohs
AdamGohs deleted the fix/web-app-links-follow-registry branch October 15, 2026 18:21

This branch was successfully deployed

1 active deployment
review-control — e4615f9b Deployed Oct 15, 2026 by AdamGohs via control #410
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