Skip to content

Restructure Solutions dropdown into 'By architecture' + 'By use case'#5082

Draft
dimitrieh wants to merge 4 commits into
feat/use-case-equipment-process-monitoringfrom
feat/use-case-nav
Draft

Restructure Solutions dropdown into 'By architecture' + 'By use case'#5082
dimitrieh wants to merge 4 commits into
feat/use-case-equipment-process-monitoringfrom
feat/use-case-nav

Conversation

@dimitrieh
Copy link
Copy Markdown
Contributor

Summary

Stacked on top of the Use Cases structure PR (#5079). Splits the existing flat Solutions dropdown into two labelled subgroups:

  • By architecture — the existing six architecture solution links, unchanged.
  • By use case — links to the seven use-case pattern pages + an "All use cases" link to the /use-cases/ hub.

Adds the supporting subgroup divider CSS so the two columns sit side by side with a single full-height divider between them.

Base: feat/use-cases-structure. Use-case links resolve as the per-pattern content PRs land. No other nav changes in this PR (Industries dropdown / nav reorder ship separately).

Skeleton structure for a new Use Cases content shape on the marketing site:
- /use-cases/ hub (renders an empty grid until use-case pages land).
- New use-case layout with the canonical page anatomy (hero, operational gap,
  why existing systems did not solve it, the operational workflow, how it is
  operationalized with FlowFuse, outcomes, related resources).
- _template.njk (non-rendered) as a copy-and-rename starting point for
  per-pattern content PRs.
- Reusable related-resources block wired to a usecase:slug tag namespace
  using existing collection logic.

Structure only. No use-case pages yet. No nav changes. No Expert dock.
Follow-up PRs targeting this branch will add the dock, the nav entry, and
the per-pattern pages with content from sales.
@dimitrieh dimitrieh force-pushed the feat/use-case-nav branch from d938902 to e9ce2e8 Compare May 28, 2026 15:17
@dimitrieh dimitrieh changed the base branch from feat/use-cases-structure to feat/use-case-equipment-process-monitoring May 28, 2026 15:17
@dimitrieh dimitrieh force-pushed the feat/use-case-equipment-process-monitoring branch from 34516bd to 15ed262 Compare June 1, 2026 17:43
Splits the existing flat Solutions dropdown into two labelled subgroups:
- 'By architecture' keeps the existing six architecture solution links
  unchanged.
- 'By use case' currently lists only the use-case links that resolve in
  this PR's tree: 'Equipment & Process monitoring' and 'All use cases'.
  Additional use-case links are added by future content PRs (each adds
  its own nav entry).

Adds the supporting subgroup divider CSS so the two columns sit side
by side with a single full-height divider between them.

Stacked on top of the Equipment & Process monitoring content PR.
@dimitrieh dimitrieh force-pushed the feat/use-case-nav branch from 503ca0b to 38c0b55 Compare June 1, 2026 17:44
@Yndira-E Yndira-E force-pushed the feat/use-case-equipment-process-monitoring branch from 635c42d to e5c0278 Compare June 3, 2026 14:57
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