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.
Stage 1: configure and deploy
Open Boxes, then choose Create Box. The first stage has General, Domain, Analytics, and Advanced tabs.
- On General, enter a name and select the ZIP archive. The ZIP is required for a new Box.
- On Domain, review the generated slug. New author-created Boxes start with an opaque free-path slug; Dedicated selection requires active account Premium capability before the Box mode changes.
- On Analytics, leave Collect visit analytics enabled to receive reporting, or disable it for this Box.
- On Advanced, configure SPA fallback, SEO noindex, and any password protection details you need.
- Deploy the Box. HTMBox creates Release 1 and, unless you explicitly save it as a draft, publishes it.
Stage 2: operate the Box
After the first deployment, the Dashboard redirects to the same Box with Stage 2 open. This is where URLs, Releases, versions, usage, and upgrade entry points are available.
- Copy or open the stable hosted URL.
- Use Releases to inspect deployment history, deploy another ZIP, or make a ready historical Release current.
- 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 account Premium is active.