Publish a site

Zinley can build a static web page and deploy it to a live HTTPS URL. Ask for the page, state whether it is public-ready, and review the returned link before sharing it.

Ask Zinley to build and publish

• "Build me a one-page site for my consulting business and publish it."
• "Make a landing page for the workshop on the 12th — headline, agenda, signup email — and give me the link."
• "Turn this outline into a simple docs page and put it online."

Zinley writes the page, packages the built output, deploys it, and replies with the address. Hosting provides HTTPS and CDN delivery.

Updating a live site

Ask for the change and include the existing project or URL. A deployment response may say that the existing project was updated. Do not assume the URL stayed the same: compare the returned URL with the one you previously shared.

• "Change the headline to 'Now booking spring projects'."
• "Add a contact section with my agent's email and republish."

Keep the deployment receipt

The current dashboard does not provide a published-sites manager. Keep the final URL and project identifier in the related conversation or Topic. If you need a deployment removed and Zinley cannot identify it from the receipt, contact support with the exact URL.

Where the work happens

Publishing can run from two places:

• On your device — when the project already lives on your machine, Zinley builds it there and deploys from there.
• On Zinley's Computer — for a cloud workspace on Plus or higher, without keeping your own computer on.

The deployment ZIP is capped at 100 MB. If a project is larger, reduce the built assets before retrying.

What kind of sites work

Sites that need a live backend — a database, logins, server-side code — aren't part of this. Zinley will say so rather than deploy something that half-works.