How to publish a site from a chat with AI

Steps

1. Ask the AI for a folder, not a snippet

   Say what the site is for, and ask for plain files. No build step means nothing to install. Name the file: hosts look for index.html.

   Make a one-page site for my bakery in Lisbon.
   Plain HTML and CSS, no build step, no frameworks.
   Put everything in a folder called site, with index.html
   at the top. Use relative links for CSS and images.

2. Check it on your own computer

   Start a small local server, open the address in a browser and click through every page. Fix what is wrong by telling the AI, not by editing the files by hand.

   $ python3 -m http.server 8000 --directory site
   Serving HTTP on 0.0.0.0 port 8000 …

   Then open http://localhost:8000/.

3. Pick a host

   All three are free for a static site. The folder and the result are the same; the table shows what differs.

   	GitHub Pages	Netlify	Cloudflare Pages
   Publish with	git push, then a setting	one command	one command
   Address	https://<username>.github.io/<repository-name>/	draft and main addresses from Netlify	<project-name>.pages.dev
   Free plan	on GitHub Free the repository must be public	a Free plan with no time limit	a Free plan: 20,000 files per site and 25 MiB per file
   Watch for	a delay before changes show	a draft deploy first, then --prod	create the project once

4. Publish the folder

   GitHub Pages. Put the files in a repository and push. Then open the repository: Settings, Pages, Build and deployment, Source: Deploy from a branch, then pick the branch and the / (root) or /docs folder. The site needs an index.html at the top level of the source folder, so put index.html in the root, or in docs/ and choose /docs.

   $ cd site
   $ git init -b main && git add . && git commit -m "first version"
   $ git remote add origin https://github.com/you/bakery.git
   $ git push -u origin main

   Netlify. Install the command line tool, sign in, deploy a draft, then deploy to the main address.

   $ npm install -g netlify-cli
   $ netlify login
   $ netlify deploy --dir=site
   $ netlify deploy --dir=site --prod

   Cloudflare Pages. Create the project once, then deploy the folder. The dashboard also takes a folder by drag and drop.

   $ npx wrangler pages project create
   $ npx wrangler pages deploy site

5. Change it from the same chat

   Tell the AI what to change, check it locally again, and run the same publish command. The address stays the same. On GitHub Pages the new version appears after the push; it can take up to 10 minutes for changes to publish.

Check that it works

Request the page the way a visitor does, or open the address in a private window. You should see status 200 and your title.

$ curl -sI https://your-site.example/ | head -1
HTTP/2 200
$ curl -s https://your-site.example/ | grep -o "<title>.*</title>"
<title>Lisbon Bakery</title>

In Uno: the agent does steps 3 to 5

In Uno Work you skip the host's account, the commands and the settings page. You talk to an agent that has the folder on its computer and is allowed to publish it.

1. Ask

   "Publish the folder site as a website." the agent calls site_publish on a folder with index.html (or one HTML file).

2. Get the address

   The site goes to https://<name>.uno4.me/, free. Ask for the same name again and publishing under the same name again updates the site.

3. Protect or extend

   "Put a password on it." site_set_password: you give a password, or the agent generates a readable one and tells you. Add a form and a new site with a form sends every entry to your account's email.

A form needs no backend. The page posts to /__forms, and Uno delivers the answers to your email, Telegram, or a webhook:

<form action="/__forms" method="POST">
  <input name="email" type="email" required>
  <button>Send</button>
</form>

From a project folder Uno publishes the built pages only: from a project folder Uno publishes dist/ or public/; keys, .env files and source files stay out. Uno hosts the published copy, so a static site stays up while your computer sleeps. A custom domain is connected in the Uno console.

What a static site cannot do

• It does not run server code. a backend (server code, or a package.json without a build) cannot be a site: run it as an app instead.
• The AI does not check facts on the page. Read the prices, phone numbers and opening hours it wrote.
• Uno publishes a plain static site without asking; taking a site off the internet waits for your Allow. If the page is not meant for everyone, ask for a password in the same sentence.

Common problems