Skip to content

Use Cases section (structure only)#5079

Draft
dimitrieh wants to merge 1 commit into
mainfrom
feat/use-cases-structure
Draft

Use Cases section (structure only)#5079
dimitrieh wants to merge 1 commit into
mainfrom
feat/use-cases-structure

Conversation

@dimitrieh
Copy link
Copy Markdown
Contributor

Summary

Skeleton structure for a new Use Cases content shape on the marketing site. Structure only; page content is intentionally placeholder.

  • /use-cases/ hub + per-pattern pages, sharing a new use-case.njk layout.
  • Floating FlowFuse Expert dock pinned to every use-case page, reusing the existing AI Expert chat.
  • Reusable related-resources.njk block (case studies / white papers / blog) wired to a usecase:slug tag namespace using existing collection logic.

No nav changes in this PR. Follow-up PRs will target this branch and fill each use case with content from sales.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 28, 2026

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit 13298a4
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/6a18599fc1ed5b00082efcd1
😎 Deploy Preview https://deploy-preview-5079--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: 90 (🟢 up 18 from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 91 (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.

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.
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