Restructure Solutions dropdown into 'By architecture' + 'By use case'#5082
Draft
dimitrieh wants to merge 4 commits into
Draft
Restructure Solutions dropdown into 'By architecture' + 'By use case'#5082dimitrieh wants to merge 4 commits into
dimitrieh wants to merge 4 commits into
Conversation
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.
d938902 to
e9ce2e8
Compare
34516bd to
15ed262
Compare
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.
503ca0b to
38c0b55
Compare
635c42d to
e5c0278
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
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.
Summary
Stacked on top of the Use Cases structure PR (#5079). Splits the existing flat Solutions dropdown into two labelled subgroups:
/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).