Skip to main content
FlowFn
IntegrationsTemplatesPricingDocsBlogSign inStart free
All documentation

v1.25.0

UpdatedJun 6, 2026Reading time1 min read

Released 2026-06-05. A single playground can now be a multi-page, SEO-indexable site — like a real marketing or store site with a home page plus /contact, /about, and more, each individually findable on Google.

Added

  • A new Pages tab in the playground editor (on plans that include multi-page sites). Add, rename, reorder, and delete pages; your main page is the site home and each extra page lives at /<slug>.
  • Shared base + per-page content: your playground's CSS and JS apply to every page, and each page adds its own HTML (plus optional per-page CSS/JS). Write your site styles and nav once.
  • Edit a page with AI: the AI assistant is available right on the Pages tab — it edits the page you're on (and knows your other pages and components) so you can build a page by chatting.
  • Per-page SEO: every page has its own title, description, and keywords, rendered server-side into that page's head so search engines and social cards pick them up.
  • Site root: in an app's settings, bind one of your assets as the site root so it owns the app's subdomain or custom domain. A playground serves its home at the root and each page at /<slug> (no /p/ prefix); a form, visualizer, or agent can instead serve as the single page at the root.
  • Nav menu: a per-page "show in menu" toggle, label, and order produce a derived navigation list, and the AI assistant knows your pages so it can build navigation that links across them.
  • Sitemap: a site on a subdomain/custom domain publishes its own sitemap.xml listing every published page, so crawlers discover the whole site.

Spotted an issue or have feedback?

support@flowfn.com
Back to docs hub →