Repository navigation
app-guide: link component call-outs to the docs - #5723
dgatti0213 wants to merge 1 commit into
Conversation
On Foundations and App delivery methods, the components we name (Snapshot, Pipeline, Instances, Team Broker, Tables, Dashboards, Device Agent, Team Library, Bill of Materials, Subflow, Custom node) were plain bold text. Link each to its docs page so readers can jump straight to the reference. - Dashboards -> the Dashboard 2.0 docs (dashboard.flowfuse.com) - Subflow -> a new /docs/user/packaging-subflows/ page (added separately in flowfuse/flowfuse); this PR stays draft until that doc lands. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVTs4TWBz2sVJ3k55ZHUg8
🔎 What changed — pages to reviewLive on the Netlify Deploy Preview once it builds: Updated pages
Docs-only content change (no component/logic changes).
|
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
📎 Docs dependency is now open: FlowFuse/flowfuse#8355 (adds |
|
@dgatti0213 Upstream docs PR is merged, but looks like this one has got a little out of sync with the website. Let me know if you can't fix it and I'll see if I can have a look |

What & why
On the Application Guide's Foundations and App delivery methods pages, the components we name (Snapshot, Pipeline, Instances, etc.) were plain bold text. This links each call-out to its docs reference so a reader can jump straight from the concept to the details.
Changes
/docs/user/packaging-subflows/page.