platform: add /platform/, the page between the homepage and the docs - #5769
Draft
dimitrieh wants to merge 3 commits into
Draft
platform: add /platform/, the page between the homepage and the docs#5769dimitrieh wants to merge 3 commits into
dimitrieh wants to merge 3 commits into
Conversation
The website says what FlowFuse does and why it matters, but never what the platform is made of or how the pieces fit together, so there is nowhere to send a technical evaluator after the homepage. Sales frames the goal as two takeaways: how FlowFuse distributes application code, and what the major components are. The page is built around those. Its spine is the Application Guide's, not a feature list, so the journey reads homepage (industry terms) to platform (our terms) to docs (depth), and every entry on the page links into the guide or the docs page that owns it. - Hero, then the two takeaways: the Foundations architecture rendered live by ArchDiagram off the same node data the guide uses, so the two cannot drift, and the component roll-call as labelled tiles. - Five stages behind a sticky contents list: Build, Deliver, Run, Connect, Govern. Deliver draws both code-distribution paths, whole app by snapshot and pipeline, or pieces by package and Team Library. - Build what's next: documentation, application guide, blueprints, services. ScrollSpySections gains a boxed nav variant (icon per row, whole active row inked) and a fallback `item` slot, so a caller whose stages render identically writes one template instead of five named slots. /product and /integrations/opcua keep the rail variant and their per-id slots unchanged. /platform is added to legacy.ts as an exact route, not a prefix, so /platform/dashboard/, /platform/device-agent/, /platform/security/ and /platform/why-flowfuse/ keep falling through to 11ty.
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
The link check failed with 1346 bad links, all of them /platform, one per page that carries the nav. The route is only linked from 11ty-generated HTML, which the Nuxt prerender crawler never parses, so it has to be listed in nitro.prerender.routes or it is missing from nuxt/dist entirely. That is the same reason /ai is listed there, and its comment now covers both. Also from the first look at the rendered page: the hero statement takes an explicit type scale rather than the site's 2.75rem h1, and the three hairline grids get a border on the wrapper so their outer rules close the box the way the interior gap-px rules already did.
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
1 participant
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.
Description
The site says what FlowFuse does and why it matters, but never what the platform is made of or how the pieces fit together, so there is nowhere to send a technical evaluator after the homepage. This adds
/platform/, wired into the top nav and the footer under Platform > Overview, ahead of Product.Sales frames the goal as two takeaways: how FlowFuse distributes application code, and what the major components are. The page is built around those, and its spine is the Application Guide's rather than a feature list, so the journey reads homepage (industry terms) to platform (our terms) to docs (depth). Every entry links into the guide or the docs page that owns it.
ArchDiagramoff the same node dataapplication-guide/foundations.mduses, so the two cannot drift. Then the component roll-call as labelled tiles.ScrollSpySectionsgains a boxed nav variant (icon per row, whole active row inked) and a fallbackitemslot, so a caller whose stages render identically writes one template instead of five named slots./productand/integrations/opcuakeep the rail variant and their per-id slots, unchanged./platformis added tolegacy.tsas an exact route, not a prefix, so/platform/dashboard/,/platform/device-agent/,/platform/security/and/platform/why-flowfuse/keep falling through to 11ty.Draft: the copy is a first pass and wants a sales read on the stage names and the component groupings. Expect a one-line conflict in
src/_data/chrome.jsonagainst #5765.Related Issue(s)
None.
Checklist