Skip to content

Use Cases: add Quality Validation - #5506

Draft
dimitrieh wants to merge 2 commits into
mainfrom
feat/use-case-quality-validation
Draft

Use Cases: add Quality Validation#5506
dimitrieh wants to merge 2 commits into
mainfrom
feat/use-case-quality-validation

Conversation

@dimitrieh

@dimitrieh dimitrieh commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Description

Targets main so Netlify builds a deploy preview. Carries #5498's layout commit ("Use case pages: add a How It Works section") because this page needs the howItWorks block the layout gains there. Once #5498 merges that commit drops out of this diff on the next rebase.

Adds /use-cases/quality-validation/, 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 review marker, so it wants a Showcase pass before it is treated as final.

Adapted to the current layout:

  • The architecture key moves inside a new howItWorks block, so it renders as a link to /use-cases/it-ot-middleware/ instead of being front-matter nothing reads.
  • howItWorks is newly authored for this page: the component breakdown, a design pattern assignment (Hardware pattern: Pipeline plus external configuration), an end-to-end diagram and docs links.
  • expertDock is dropped; nothing on main renders it.
  • Diagram is a placehold.co stand-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

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created (instructions)

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 Quality Validation 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 the quality gate from measurement through spec to operator prompt, 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
dimitrieh marked this pull request as draft August 4, 2026 22:04
@dimitrieh
dimitrieh force-pushed the feat/use-case-quality-validation branch from 3182d01 to c03a951 Compare August 4, 2026 22:05
@dimitrieh
dimitrieh changed the base branch from feat/use-case-how-it-works to main August 4, 2026 22:05
@netlify

netlify Bot commented Aug 4, 2026

Copy link
Copy Markdown

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit c03a951
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/6a72621ca67c970008342e35
😎 Deploy Preview https://deploy-preview-5506--flowforge-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 56 (🔴 down 14 from production)
Accessibility: 96 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant