Use Cases: add System Diagnostics - #5509
Draft
dimitrieh wants to merge 2 commits into
Draft
Conversation
Use case pages carried only what and why. This adds a howItWorks block to the layout covering the component breakdown, the design pattern chosen, an end-to-end architecture diagram and the hand-off into the product docs. Filled in for production monitoring and shop floor communication, with placehold.co stand-ins until the real diagrams are drawn. Two supporting fixes: section eyebrow numbers now derive from the nav array instead of being hardcoded, so they no longer drift when a page omits a block; and the architecture front-matter key on shop floor communication, which the layout never read, now renders as a link to the architecture page the use case sits on.
Restores the System Diagnostics page written in the earlier three-lens IA work and dropped when that work was cut back. Copy is recovered as written and still carries its template-copy marker for a Showcase pass. Adapted to the current layout: the architecture key moves inside a new howItWorks block covering diagnostics from a shared emitter through to one triage view, and expertDock is dropped since nothing renders it. Diagram is a placehold.co stand-in. Links it from the homepage Operational Application System entry and the footer use case list.
dimitrieh
marked this pull request as draft
August 4, 2026 22:04
dimitrieh
force-pushed
the
feat/use-case-system-diagnostics
branch
from
August 4, 2026 22:05
9ed9089 to
9f5af6a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds
/use-cases/system-diagnostics/, one of the use case pages defined in the earlier three-lens IA work and dropped when that work was cut back. The page copy is recovered as it was written and still carries its#placeholder: template copy for reviewmarker, so it wants a Showcase pass before it is treated as final.Adapted to the current layout:
architecturekey moves inside a newhowItWorksblock, so it renders as a link to/use-cases/it-ot-middleware/instead of being front-matter nothing reads.howItWorksis newly authored for this page: the component breakdown, a design pattern assignment (Software pattern: Packaged application), an end-to-end diagram and docs links.expertDockis dropped; nothing onmainrenders it.placehold.costand-in pending an art request.Wiring: adds the
url:to this page's existing entry in the homepage Operational Application System list, where it was previously unlinked text, and adds it to the footer use case list. The Solutions nav still points at the/use-cases/hub rather than listing every page.Sibling PRs add the other six pages the same way. They each touch the same homepage list and footer list, so expect a one-line rebase as they land.
Related Issue(s)
None.
Checklist