Publish a page or site

Zinley can build a web page and put it on a live URL for you — no hosting account, no deploy step, no files to move around. Ask, and you get a link you can share.

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, deploys it, and replies with the address. The site is served over HTTPS on a global CDN, so it's fast wherever the person opening it is.

A chat where Zinley built a site and returned a live URL after deploying it.
Ask for a site — Zinley builds it and hands you a live URL.

Updating a live site

Ask for the change and Zinley redeploys in place — the URL stays exactly the same, so anything you've already shared keeps working.

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

Checking on a project

  • "What sites do I have published?"
  • "What's the URL for the workshop page?"

Taking it down

  • "Take the workshop page offline."

The site stops serving immediately. Ask Zinley to build it again later if you change your mind.

Where the work happens

Publishing works from two places, and Zinley picks the sensible one:

  • On your device — when the project already lives on your machine, Zinley builds it there and deploys from there.
  • On Zinley's Computer — when you're asking by email, by phone, or from a chat app, or when the build is long enough that you'd rather not tie up your laptop. Nothing of yours needs to be switched on.

Either way the upload is capped at 100 MB per site, which is plenty for a static site with images and fonts. If a project is bigger than that, Zinley will tell you what to trim.

What kind of sites work

Works well Notes
Plain HTML / CSS / JS pages Images, fonts, and assets all come along
Single-page apps (React, Vite, Next.js static exports) Deep links resolve correctly — a shared /pricing link opens the right view
Anything static Documentation, landing pages, portfolios, one-pagers, demos

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.

Related