Homepage: say what an app platform means - #5500
Conversation
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.
The homepage asserts that FlowFuse is a platform and then moves straight to capabilities, so a visitor never learns what the platform is made of or why the word applies. The next step offered was the Expert, which is the wrong place to send someone who does not yet understand the components. Adds a section after the solution statement that states the claim, backs it with the two ways FlowFuse distributes and manages code, lists the major components grouped by what they do, and hands off to /platform/ for detail.
Main moved the header nav and footer out of base.njk into src/_data/chrome.json, so the Platform nav entry moves with it: added to the Platform > Overview column (and the matching footer group) instead of the hardcoded lists.
The Platform nav entry uses it, and Nuxt needs an explicit import per icon.
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
So this is a great start! but IMO the homepage should sit one level above the platform detail page. Homepage in terms visitors already recognize, platform page for our specifics. Right now both pages carry the same five groups with the same product names, so the homepage is the platform page with the explanations removed. "Instances · Devices · Groups" and "Snapshots · Pipelines · Environment Variables" are our vocabulary, not the visitor's. Anyone who can parse them is already headed to /platform. Suggested values: |
2 participants
Description
The homepage asserts that FlowFuse is a platform and then moves straight to capabilities, so a visitor never learns what the platform is made of or why the word applies. The next step offered is the Expert, which is the wrong place to send someone who does not yet understand the components.
Adds one section after the solution statement that:
/platform/for the detail instead of dead-ending at the Expert.No existing homepage content is removed or reordered.
Related Issue(s)
None.
Checklist