Skip to content

/ai: one agent picker in the hero, Expert first - #5670

Open
dimitrieh wants to merge 7 commits into
mainfrom
ai/connect-your-own-agent
Open

/ai: one agent picker in the hero, Expert first#5670
dimitrieh wants to merge 7 commits into
mainfrom
ai/connect-your-own-agent

Conversation

@dimitrieh

@dimitrieh dimitrieh commented Aug 24, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Description

Rebuilds /ai around a single agent picker instead of a page that asked the visitor to choose twice.

Hero carries a tabbed picker: FlowFuse Expert, Microsoft Copilot, ChatGPT, Claude, Gemini, Local and Custom Agents. Three steps per tab. Expert's are "sign in / or use the Device Agent / ask for what you need"; the rest are "copy the URL / add it in your agent / sign in and choose scopes". Expert has no endpoint box, the others do.

Then a showcase well alternating between two schematics on a timer, AI Governance, and the capability band.

Removed: the two path sections, the fork cards, the use-cases section, and the hero CTAs. All were saying what the picker now says.

Notable

  • Agent marks from official sources only: OpenAI brand kit, Anthropic press kit, adoption.microsoft.com, Google's CDN. Sources and the trademark position are in src/images/ai/agents/README.md. Microsoft still needs a legal check. A tab with no mark falls back to its name as text.
  • Showcase schematics are drawn, not placeholders: Expert nested inside the platform, an external agent overlapping it from outside. Containment versus overlap carries the distinction in one glance. No external image requests on the page.
  • Capability items say when behaviour differs for external agents, on the three where it does. Everything else applies either way and carries no note.
  • Governance tiles are path-neutral, which is what lets that section sit above the picker. The old approval-cards tile was Expert-only and would have been false for a connected agent.
  • Capability media wells are still empty, fillable via media: in frontmatter.

Fixes to my earlier revision on this branch

  • The disabled Expert widget was still shipping its modal and a 1,565-line script, and logging a console error. Nunjucks executes {% include %} inside an HTML comment; only {# #} prevents it.
  • The bespoke copy button gave no feedback. Replaced with the existing ff-command component, which has the non-secure-context fallback and also stops the URL truncating.
  • CTAs now use sign-up-url.njk and house capture() names rather than hardcoded URLs and invented events.

Related Issue(s)

FlowFuse/flowfuse#8192

Depends on

/docs/user/expert/third-party-agents/ lands with FlowFuse/flowfuse#8241 (green). The link check fails until it merges; Netlify's build does not run it, so the preview builds. Changelog and catalog entry are #5672, blog post #5671.

Checklist

  • I have read the contribution guidelines
  • I have considered the performance impact of these changes
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
  • For blog PRs, an Art Request has been created (instructions)

@dimitrieh
/ai: disable the Expert prompt widget and add a connect-your-own-agen…
320f901 
…t section

Splits the Connect capability group into inbound and outbound so the two MCP
directions cannot be confused, scopes the approval-card governance claim to
Expert and Platform Automations, and replaces the hero prompt widget with a
two-path chooser. The widget's components and script are left in place.
This was referenced Aug 24, 2026
Draft
Open
@netlify

netlify Bot commented Aug 24, 2026 •
edited
Loading

Copy link
Copy Markdown

✅ Deploy Preview for flowforge-website ready!

Name Link
🔨 Latest commit cbc62c2
🔍 Latest deploy log https://app.netlify.com/projects/flowforge-website/deploys/6a8c69397f3de8000872ed3e
😎 Deploy Preview https://deploy-preview-5670--flowforge-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse		 1 paths audited
Performance: 65 (🟢 up 13 from production)
Accessibility: 96 (no change from production)
Best Practices: 100 (no change from production)
SEO: 85 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@dimitrieh

dimitrieh commented Aug 24, 2026

Copy link
Copy Markdown
Contributor Author

Preview affected pages:

test_website / Build and check fails, and it is only the expected dependency. Hyperlink reports 4 bad links and 0 bad anchors, all four the same target:

/docs/user/expert/third-party-agents

from the changelog, /ai, and the handbook features table that the catalog docsLink feeds. That page lands with FlowFuse/flowfuse#8241, which is green, so all four clear on merge. Nothing else in the build is broken.

@dimitrieh
/ai: lead with what AI can do, then a real fork into Expert or your o…
d6fe87d 
…wn agent

Restructures the page so the reader understands the capabilities before being
asked to choose. Adds a FlowFuse Expert section built the same way as the
connect section, so both paths have a destination and a CTA. Also fixes the
diagram rendering at zero height, and stops the disabled Expert modal and its
script from shipping: an HTML comment does not prevent Nunjucks executing an
include.
@dimitrieh dimitrieh mentioned this pull request Aug 24, 2026
Open
5 tasks
@dimitrieh
dimitrieh force-pushed the ai/connect-your-own-agent branch from dbad24d to d6fe87d Compare August 24, 2026 12:07
@dimitrieh dimitrieh changed the title /ai: connect your own AI agent, plus the 3.0 changelog entry /ai: lead with what AI can do, then fork into Expert or your own agent Aug 24, 2026
@dimitrieh
/ai: rebuild the page around one agent picker in the hero
777b614 
Replaces the two path sections and the fork cards with a single tabbed picker in
the hero, FlowFuse Expert first, so the choice is made once. Adds the five agent
marks, an auto-rotating showcase well with per-tab timing, and media wells on the
capability items. Moves AI Governance directly below the hero as shared ground.

Also drops a bespoke copy button in favour of the existing ff-command component,
which has the non-secure-context fallback the bespoke one lacked.
@dimitrieh dimitrieh changed the title /ai: lead with what AI can do, then fork into Expert or your own agent /ai: one agent picker in the hero, Expert first Aug 24, 2026
@dimitrieh
/ai: draw the showcase schematics instead of using placeholders
f0deea7 
Expert nested inside the platform, an external agent overlapping it from outside.
Replaces the placehold.co images, so the page makes no external image requests.
@dimitrieh
/ai: give the showcase band room above the tabs
625d102
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cstns cstns Awaiting requested review from cstns
@Steve-Mcl Steve-Mcl Awaiting requested review from Steve-Mcl
@andypalmi andypalmi Awaiting requested review from andypalmi

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@dimitrieh