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.
|
Preview affected pages: |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@dimitrieh If we're changing these pages, can we move them to Nuxt? |
|
@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:
|
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.
|
@dimitrieh This page is AWESOME! I would add some more color on the code sharing patterns. It doesnt connect well to the "How code is distributed and managed" so some work to do here. |
|
@dgatti0213 @dimitrieh maybe we go with this for now then add more color in another iteration or.... |
|
This page reads the way im recommending the use case pages to read: https://flowfuse.com/application-guide/flowfuse/worked-example/ |
|
cc: @KristopherLeads |
4 participants
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:placehold.costand-in pending an art request.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