Skip to content

Add a Platform page under Platform > Product - #5499

Draft
dimitrieh wants to merge 1 commit into
mainfrom
feat/platform-page
Draft

Add a Platform page under Platform > Product#5499
dimitrieh wants to merge 1 commit into
mainfrom
feat/platform-page

Conversation

@dimitrieh

Copy link
Copy Markdown
Contributor

Description

The website explains what FlowFuse does and why it matters, but never what the platform is made of or how the pieces fit together. That leaves no page to send a technical evaluator to after the homepage, and the current next step offered is the Expert, which does not answer "what are the major components".

Adds /platform/, wired into the top nav and the footer under Platform > Product, ahead of Features. Sections:

  1. How code moves. The two distribution models, shipping a whole application by pipeline versus shipping building blocks via a library. This is the reason the word "platform" applies.
  2. Major components. Everything FlowFuse does, in five groups: where applications run, how they get built, how code is distributed and managed, what they connect to, how it is governed.
  3. How it fits together. End-to-end architecture diagram, currently a placehold.co stand-in pending an art request.
  4. Design patterns. The three hardware and three software patterns.
  5. Where Node-RED fits. Platform first, then Node-RED.

Every component links to an existing product page or docs page; no new docs are assumed.

Content is a first pass and needs a sales sign-off on the pattern names and the component groupings.

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)

The website explains what FlowFuse does and why it matters, but never what
the platform is made of or how the pieces fit together, so there is no page
to send a technical evaluator to after the homepage.

Adds /platform/ covering the two ways FlowFuse distributes and manages code,
the major components grouped by what they do, an end-to-end architecture
diagram, the six design patterns, and where Node-RED actually sits. The
diagram is a placehold.co stand-in pending an art request.

Wires it into the top nav and the footer under Platform > Product, ahead of
Features.
@dimitrieh

Copy link
Copy Markdown
Contributor Author

@dimitrieh
dimitrieh marked this pull request as draft August 4, 2026 20:19
@netlify

netlify Bot commented Aug 4, 2026

Copy link
Copy Markdown

Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit da8d2f3
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/6a7247115a269e0008d297d9
😎 Deploy Preview https://deploy-preview-5499--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: 65 (🟢 up 5 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.

@ZJvandeWeg

Copy link
Copy Markdown
Member

@dimitrieh If we're changing these pages, can we move them to Nuxt?

@dimitrieh

Copy link
Copy Markdown
Contributor Author

@ZJvandeWeg yes, I will follow up with a refactor into nuxt so as to keep the scope out of this and us being able to merge things faster.

I see two separate migrations:

  • /platform/ has four Eleventy siblings (dashboard, device-agent, features, why-flowfuse, security)
  • /use-cases/** as one dedicated PR covering all ten pages and the layout

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.

2 participants