Use staging to review a current website build, production to update the live site, Domain settings for a custom hostname, or export paths for ZIP, widget, PDF, WordPress, and supported full-stack outputs.
Where: f0 Website → top bar → Publish
Key ideas
- Staging and production are separate: Staging creates or updates a review URL; production updates the public site. Preview inside the editor is neither one.
- Domain and metadata: A custom domain, title, description, Open Graph image, favicon, and injected head/body/footer code have separate configuration and validation.
- Static export choices: Download a standalone ZIP, widget snippet, or desktop PDF when the project type and plan support that output.
- CMS and app outputs: WordPress project types publish themes/content according to their push policy; supported full-stack apps use a different backend deployment path.
Steps
- Open Preview and verify pages, links, responsive breakpoints, fonts/media, CMS data, and interactions before creating a hosted artifact.
- Open Publish and use Publish/update staging to create a review build. Share and test that staging URL.
- Open publish metadata and set the site title, description, Open Graph image, favicon, and any required injected code.
- Connect or manage a custom domain, follow the displayed DNS steps, and wait for verification before treating it as live.
- Choose Publish/update production only when the tested build should replace the public site. Recheck the returned URL after the operation finishes.
- For portable delivery, choose Download ZIP, widget snippet, or Export PDF where available. Importing or editing later does not update an older download automatically.
- For WordPress, confirm the project type and credentials, review the content-push policy, wait for server readiness, and then publish the theme/content.
- Use the full-stack path only when the project actually includes its supported backend; a static website publish does not provision arbitrary server logic.
Output map
- Preview: local editor inspection.
- Staging: shareable review build.
- Production: public hosted site update.
- Custom domain: DNS-connected address for the hosted site.
- ZIP/widget/PDF: downloadable or embeddable artifacts.
- WordPress: project-type-specific theme and optional content push.
- Full-stack: supported application and backend delivery.
Embedded Flowgen website nodes
An embedded document node has a synthetic scene id, not a normal Firebase project id. On first publish, the editor asks Flowgen to mint or reuse a hidden real site project and publishes through that target.
Pricing and watermark boundaries
Plan and hosting rules are evaluated at publish time. The current UI is authoritative for charges, export eligibility, domains, and watermark removal; a saved old setting cannot bypass the current rule.
Failed and no-op publish reporting
Current publishing checks HTTP status before claiming success. A failed upload, deploy, update, custom-domain, delete, or release request reports the operation and response detail. An already-current no-op may return the existing live URL, but it does not create a false creator-completion event.
Tips
- Treat staging as a release candidate and test the real URL, not only the canvas.
- Keep a downloaded export when handing off code; hosted production and local files are independent artifacts.
Limitations and important notes
- ZIP and PDF can be plan- or desktop-gated.
- Local-link media cannot be resolved by cloud publishing until it is uploaded.
- Publishing source changes does not update marketplace snapshots or prior exports.
- WordPress and full-stack outputs have credentials/runtime requirements beyond a simple static site.
Troubleshooting
The live site still shows an older version
Confirm you published production rather than only staging, then open the returned production URL and allow caches to refresh.
Domain verification fails
Compare every DNS record with Domain settings, remove conflicting records, and wait for DNS propagation before retrying verification.