Create release blog article - #5647
Conversation
|
@sumitshinde-84 tests fail because the meta title is too long |
| --- | ||
| metaTitle: "FlowFuse 3.0: Edge/Hub/Fleet, Industrial AI & Dashboard Themes" | ||
| title: "FlowFuse 3.0: Build, deploy, and govern — matched to how you run" | ||
| subtitle: |
There was a problem hiding this comment.
@KristopherLeads @sumitshinde-84 @allthedoll the doc didn't have a subtitle
There was a problem hiding this comment.
👋 could we please add a subtitle?
There was a problem hiding this comment.
Added, please review
| tldr: | ||
| cta: | ||
| type: | ||
| title: | ||
| description: |
There was a problem hiding this comment.
@sumitshinde-84 will you take care of these?
Maybe the last section needs some rework so it complements the CTA section instead of duplicating it.
There was a problem hiding this comment.
I added the Book a Demo CTA and kept the existing “how to get started” section because I think it’s important to show users how they can actually get started with Expert. This way, we now have all three CTAs covered.
|
@FlowFuse/marketing I've added GitHub review comments on the lines where things are missing from the doc (e.g. the subtitle), plus inline visible placeholders in the code for the items flagged as pending in the doc's own notes. |
ae95025 to
6d89559
Compare
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…me it for any AI agent
No additional FlowFuse Expert news exists for 3.0 yet to justify its own heading, per Dimitrie's review comment.
c0e126f to
dc4e269
Compare
|
Thanks for the copy edits @dimitrieh ! merged the single-line Expert into the Build intro and merged main |
Pipelines do not ship. There are 35 platform tools on main and none of them are pipeline tools; those come from a branch with no milestone. Replaced with what the tools actually cover, including reading FlowFuse Tables data. The agent set now matches /ai: the enterprise assistants and a local model first, command-line and editor agents as a trailing sentence. Gemini the app and local models were missing entirely, and coding agents had equal billing. Bounded "the same capabilities Expert does": true of the platform tools, not of the assistance built into the editor, which stays first-party. "Only your own authenticated agent can connect to a session" replaced with what is actually enforced: the teams and the access level you granted, a browser session you point the agent at from the header, and the audit entry marked via MCP. Points at /ai alongside the docs. Ordering there is still open, see the review comment.
dimitrieh
left a comment
There was a problem hiding this comment.
FlowFuse/flowfuse#8241 for docs PR on connecting external agents

Description
New blog article based on https://docs.google.com/document/d/1qfw-0CxupYStKrrJ5QhPT0teICfVvn2mzTHxDbag8UE/edit?usp=sharing
This is just the starting point so the team can finalize it.
Related Issue(s)
Checklist