Publishing

Deployment

What happens when you press Publish, and how the result reaches visitors.

What a publish does

  1. Checks the policy
    If the workspace scans on publish, the project is scanned, and a blocking finding stops the publish.
  2. Renders the site
    Every page is rendered to static HTML, with your theme, photographs and forms.
  3. Records a version
    The rendered site is saved as a snapshot, with a record of the deployment.
  4. Goes live
    The address — and any active custom domain — serves the new version straight away.

How it is served

  • Pages are static files, delivered through Cloudflare’s network.
  • A strict content security policy: published pages run no scripts except Webforgia’s own 3D scene, when a hero uses one.
  • Forms post to Webforgia, which stores and delivers the submission.
  • With search indexing off, every page is published with a no-index tag. Sites already published change on their next publish.

Taking a site down

Removing a custom domain takes that address offline at once. Deleting a project removes it from your workspace, but its published copy at the webforgia.com address is not removed yet — if you need that address taken down, ask support. Search results can take a while to disappear even after a page is gone.