Getting started pages

[KristopherLeads]

Description

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	90d1195
🔍 Latest deploy log	https://app.netlify.com/projects/flowforge-website/deploys/6a91fac078189f0008114c6c
😎 Deploy Preview	https://deploy-preview-5710--flowforge-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 62 (🟢 up 19 from production) Accessibility: 96 (no change from production) Best Practices: 100 (no change from production) SEO: 85 (🔴 down 7 from production) PWA: - View the detailed breakdown and full score reports

---

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

[netlify]

✅ Deploy Preview for flowforge-website ready!

Name	Link
🔨 Latest commit	e0f47a8
🔍 Latest deploy log	https://app.netlify.com/projects/flowforge-website/deploys/6a97359b9272d300089d4c8b
😎 Deploy Preview	https://deploy-preview-5710--flowforge-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 66 (🟢 up 23 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.

[Yndira-E]

@KristopherLeads there's no description on this PR, would you mind sharing the rationale behind these changes?

[Yndira-E]

Thanks for putting this together. A couple of things before I can review this properly:

No PR description / rationale. I don't have context on why this page needs to exist, who it's for, or what problem it solves that /docs or the existing product pages don't already.

On the design: going through the code, a lot of visual patterns here don't match anything else on the site: colored left-borders on cards, six different pill/badge treatments, custom eyebrow styling, a teal accent that isn't in our brand palette (handbook/design/branding), and bold weights heavier than our fonts guidance allows. None of it reuses the CTA button system, the pill pattern, or the cards component from other pages. With this many new patterns stacked on one page it ends up feeling crowded — at this point it feels easier to start the design from scratch than to fix what's here.

Could you share the doc this was built from? With the rationale and that copy, I could put together a design that's aligned with the rest of the site and its visual language.