Website builder

The Sites tab builds small websites. You describe what you want, the files get written, and you can publish the result at its own address.

How it works

1. Create a site and give it an address. It starts as a draft — nothing is public.
2. Describe what you want in the builder. The HTML, CSS and JavaScript get written,

and the preview beside it updates.

1. Keep going. Each request rewrites the files it needs to and leaves the rest alone,

so "add a pricing section" does not throw away your header.

1. Publish when you are happy. The address starts working immediately.

You can also edit any file by hand. The builder and the editor write the same files — neither one is the "real" version.

What kind of sites

Static ones: HTML, CSS and vanilla JavaScript, with Tailwind available from its CDN. No build step, which is the constraint that makes everything else work — a site is a handful of text files, so it renders instantly and publishes instantly.

That is a real limit, not a temporary one for this version. No React, no Vue, no TypeScript, no npm packages. If the builder ever produces an import from a package, that file will not work and the preview will show you so.

What static sites are genuinely good for:

• Landing pages, one-page sites, coming-soon pages
• Portfolios, menus, event pages, price lists
• Documentation and reference pages
• Anything where the content matters more than the machinery

What they cannot do: store data, take payments, send email, or log anyone in. A form can look right, but there is nothing behind it. If you need a form that actually submits, host it elsewhere and link out.

Your site's address

Published sites live on their own domain, separate from this app. The builder shows you the exact URL.

That separation is deliberate and it is about your visitors' safety rather than tidiness: your site's JavaScript runs in its own security context, where it cannot touch anyone's Unizune AI session. It also means the address is short and does not have this app's name in the path.

Two things follow from it:

• Nothing on that domain is indexed by search engines. It is a shared subdomain

carrying many people's sites, so it asks crawlers to stay away. If you want a site to rank, point your own domain at it — which is not built yet.

• Addresses are first-come. Some names are reserved, including anything that could

be mistaken for a login or billing page.

Limits

• 3 published sites on the free plan. Drafts do not count, so you can experiment

as much as you like.

• 20 files per site, and a size limit per file. Plenty for a static site.
• A cap on builder requests per hour, because each one is the most expensive kind of

request the assistant handles.

Changing a published site's address makes the old one stop working immediately, and frees it for anyone else to take. Deleting a site does the same.

Templates

The builder offers templates as starting points. Picking one copies its files into your site — a copy, so editing yours never affects the template or anyone else's site, and a template being changed or removed later never touches what you built.

Getting good results

• One thing at a time. "Add a pricing section with three tiers" works far better

than a paragraph describing an entire site.

• Say what it is for. "A landing page for a dog-walking business in Bristol" gives

the builder something concrete; "a nice website" does not.

• Name the constraint you care about. "Readable at 360px wide", "dark by default",

"no images" — these get followed closely.

• Edit by hand for small fixes. Changing one word is faster in the editor than in

a request.