Build and publish a static site

Ask your agent to build a static page, review it, then publish when the audience and content are ready. A local preview and a deployed public URL are different outcomes.

Open it

On desktop or mobile, start in Home → Chat. Name the existing project and computer if the files are local, or ask to use Zinley's Computer for a cloud project.

Give a complete brief

Include the purpose, audience, sections, brand assets, content, and whether publication is authorized:

“Build a one-page workshop site with the agenda, venue, and contact email. Use these approved images. Show me the preview before publishing.”

Do not put private notes, credentials, unpublished customer information, or secrets into a public build. A static frontend cannot safely hide a secret merely because the source file is minified.

Review before publishing

Open the preview and test navigation, links, images, forms, and phone-size layout. Verify the exact contact address and dates. Ask for missing behavior to be explained; a visual form is not proof that submissions are stored or delivered.

Static HTML, CSS, JavaScript, and built static app output are supported by this publishing path. A live database, authentication service, or server runtime requires separate infrastructure. Do not treat a successful upload as proof those features exist.

Confirm the deployed result

When you authorize publishing, wait for a deployment result and open its returned HTTPS URL. Test a direct nested link if the site has multiple routes. Keep the project identifier and URL in the conversation for updates or removal.

If an archive is too large, reduce built assets and follow the size error shown. Do not retry an unchanged oversized package repeatedly.

Update or remove a site

Give the existing URL and project identifier, then state the change. Ask to update that project rather than create another one. Compare the returned URL and inspect the changed live page before sharing it again.

To remove a deployment, identify the exact project and ask for removal, then verify the URL's state. If the agent cannot resolve the project, contact support with the deployment receipt. Do not assume deleting a local folder takes a published site offline.