Help Center

Spaces

Create a Space

Deploy a static frontend from the Author Dashboard. The creation screen uses a deploy-first first stage, then opens operational controls after the first Release is ready.

Before you start

Prepare one ZIP archive containing your static frontend. The archive needs an entry HTML file, normally index.html, and the CSS, JavaScript, images, fonts, and other assets it references.

The current Dashboard upload accepts a ZIP archive up to 100 MB. The archive is validated before its contents become a Release.

Tips and limits

  • Use relative asset paths that work from the hosted URL.
  • Open the ZIP before uploading to make sure the entry HTML file is in the expected project root.
  • The standalone CLI also accepts a ZIP only; it does not package a folder for you.

Create and deploy

Open Spaces, then choose Create new. This opens the full editor on Source, with Domain, Analytics, and Advanced also available.

  1. In the summary, enter the Space title. The title is separate from the website address.
  2. On Source, choose ZIP package, Files & folders, or HTML. A new Space needs a deployment source unless you save it as a draft.
  3. On Domain, a new Space receives a generated per-Space subdomain when address routing is enabled. Verified account owners can choose an address after creation; this does not activate Dedicated mode.
  4. On Analytics, leave Collect visit analytics enabled to receive reporting, or disable it for this Space.
  5. On Advanced, configure SPA fallback, SEO noindex, and any password protection details you need.
  6. Deploy the Space. HTMLSpace creates Release 1 and, unless you explicitly save it as a draft, publishes it.

Manage the Space

The same editor remains available after the first deployment. Use its tabs to manage the current website, address, analytics, settings, and Releases.

  1. Copy or open the stable hosted URL from the summary.
  2. Change the website address separately in Domain. An address change does not deploy files, create a Release, or move stored bytes.
  3. Click the Space name or Settings to open its editor. Choose Deployed Releases for the dedicated Releases and Activity page, or Deploy new version for a quick source-only deployment.
  4. Use the Live Workspace only for supported mutable file work; it is distinct from Release history.

Tips and limits

  • A ZIP upload from the edit screen creates a new immutable Release.
  • A draft needs a Release before it can be published.
  • Creating or selecting Dedicated opens Account Plans; the mode changes only when Premium or Advanced is active.