Experiment/url replacement

[Yndira-E]

Description

This PR replaces all references to https://app.flowfuse.com/account/create with the onboarding page URL /get-started/, as part of the experiment and as stated in the previous related PR.

Although that URL has been replaced, there are still other ways to access the sign-up page:

• The Sign in button in the navigation bar on every page links to https://app.flowfuse.com/
• https://app.flowfuse.com/ includes a link to Sign up
• The FlowFuse Expert invites users to continue the chat in FF Cloud, which links to https://app.flowfuse.com/
• Blueprints include a CTA that links to https://app.flowfuse.com/
• This section of the handbook includes the URL https://app.flowfuse.com/account/create, although it is plain text
• This PR only covers the website — /docs and /blueprints should be checked as well
• CTAs vary across the website (e.g., Try it out, Free trial, Try for free, Get started). I’m not sure we should change those, especially when they appear inline in paragraphs. If we decide to standardize them, we should agree on the new CTA first, and I can address it in a follow-up PR.

I might be missing a few others, but these are the ones I came across while making the changes.

Related Issue(s)

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)

[netlify]

✅ Deploy Preview for flowforge-website ready!

Name	Link
🔨 Latest commit	e8f4190
🔍 Latest deploy log	https://app.netlify.com/projects/flowforge-website/deploys/69693758b7c66d0008b8822e
😎 Deploy Preview	https://deploy-preview-4404--flowforge-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 84 (🟢 up 27 from production) Accessibility: 80 (no change from production) Best Practices: 100 (🟢 up 8 from production) SEO: 92 (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.

[Yndira-E]

Building on the notes above, the hero AI chat still nudges users to self-serve and continue in the app. If we’re aiming for a more sales-led flow with this experiment, should we realign that journey so the chat helps qualify and route to sales?

Also, is there an epic or doc that outlines the experiment’s goal, success metrics, and timeframe? I want to keep any follow-ups aligned with what we’re measuring.

[Yndira-E]

We could keep links to https://app.flowfuse.com/ for existing users, and swap “Sign up” for “Get started” with a short microcopy (“New to FlowFuse? Start here — we’ll guide you through the next steps.”) linking to /get-started/. WDYT?

[ZJvandeWeg]

@Yndira-E I start to think we need a CTA partial to remove this from happening again, 125 or so files with the same change.

Can you do a follow up PR and get Claude to make it a small partial?

[Yndira-E]

Will do. Although I don't have a Claude subscription, I've been testing the copilot agent and I'd say it's not as good as Claude