A minimal static site
<!doctype html>
<html lang="en">
<meta charset="utf-8">
<title>My first site</title>
<h1>Hello from WEBDANGER</h1>
</html>Your first site.Published with confidence.
Start with a static website, inspect its verified files, publish it on your WEBDANGER address and keep a version you can return to.
The same workflow from your terminal
The CLI uses the same account, quotas and deployment history. The package is currently available from the authorized project checkout; it has not been published to npm. Create a personal token in Consol → Security and pass it through WEBDANGER_API_TOKEN.
pnpm webdanger login
pnpm webdanger init --name "My first site" --slug my-first-site
pnpm webdanger preview --dir dist
pnpm webdanger deploy --dir dist --json
pnpm webdanger status --json
pnpm webdanger deployments --json
pnpm webdanger logs --json
pnpm webdanger rollback --to 1 --jsonUnderstand the result
201 creates a project or verified version. 200 confirms an accepted publication or rollback request; confirm the actual website too. 401 means sign in or replace an expired/revoked CLI token. 403 means your workspace role cannot perform this action. 409 means a quota, state or address conflict. 422 means invalid input or archive.
Paid checkout and registrar purchases stay closed until their separate launch checks are accepted. Template previews are available; cloning depends on the template rights and your accepted plan.
Create a free workspaceCreate your workspace
Register, confirm your email and sign in to Consol. Free publication does not require a purchase or a custom domain.
Create a free workspacePrepare a ZIP
Place index.html at the archive root, with your CSS, images and other static files. Keep ZIPs under 50 MB, extracted files under 200 MB and the file count under 2,000. Executables, hidden files and symbolic links are rejected.
Inspect the verified version
In Sites, create a ZIP project, upload the archive and open Preview. This is a five-minute read-only view: scripts and forms are blocked; use relative asset URLs. An invalid upload preserves the published version.
Publish, change and roll back
Publish the verified version, then open your WEBDANGER address. Upload a changed archive to create another version. Rollback to this version returns to a previous ready deployment. If publication fails, keep the current version and contact Support from your account.