Website builder

Steve is your software engineer. Tell him what you want in plain language and he writes the site — HTML, CSS and JavaScript — live in a code panel that opens by itself. Seconds after the last character lands, the site is running in a real preview you can click around in. Then you change it by talking to him.

No page builder. No drag and drop. No template gallery. Real code, in a real workspace, that you can read, download and host anywhere you like.

What Steve builds — and what he doesn't

This is the first thing to know, because it decides whether Steve is the right tool for your job.

He builds static front-end sites. Landing pages, portfolios, one-pagers, menus, event pages, small interactive tools and prototypes — calculators, quizzes, little games. Styling loads from a CSS CDN plus web fonts; interactivity is plain JavaScript. Multi-file is supported: index.html, css/style.css, js/app.js, and so on.

Build your first site

1. Open a new conversation with Steve from the sidebar.
2. Describe the site in one message. Be specific about the sections you want, the mood, and the colours — Steve builds the whole thing in one pass, so detail up front beats corrections later.
3. Watch. Steve opens with one short sentence, then the workspace panel opens by itself and the code starts appearing character by character, with a blinking caret and the file being written marked in the file tree.
4. When the last file closes, the preview spins up and the site appears under the Preview tab.
5. Click around it. Then tell Steve what to change.

The workspace: Code | Preview

The panel that opens next to the chat is a real code workspace, not a screenshot.

Code tab

• A file tree on the left — folders, files, an image icon for imported images, and a pulsing dot on whichever file Steve is writing right now.
• A read-only editor with line numbers and syntax highlighting. Read-only is intentional: Steve owns the files, and you drive him by chat. It means you and he never fight over the same buffer.
• While a build is streaming, the editor auto-scrolls and keeps pace with the caret.

Preview tab

• The site, running, in a sandboxed frame you can interact with. Reload it, or pop it out into its own browser tab from the panel header.

What you see in the panel is loaded from the durable copy of your project, so it is identical whether you are watching it stream live or reopening the conversation next month.

Editing by chat

Tell Steve what to change. He edits the file rather than rebuilding the page.

Every edit leaves a receipt in the transcript: a compact chip like ✎ index.html +12 −3. Click it and the change opens inside the workspace as a red/green diff — added lines green, removed lines red — instead of dumping a wall of code into your chat. Steve's transcript reads like a terminal: ⏺ create_site(index.html) ✓, foldable results, no marketing prose. You can see the site; he doesn't recap it at you.

Click an element to target it

The most useful trick in the workspace. Rather than describing which headline you mean:

1. Go to the Preview tab.
2. Turn on element select — the cursor button above the preview.
3. Hover — elements outline as you go. Click the one you want.
4. It becomes a chip on your message box.
5. Type what you want changed and send.

Steve now edits that exact element instead of guessing, and instead of rebuilding the page around it.

Clone a URL — for inspiration, not for copying

Give Steve a reference and he'll read its shape.

Steve extracts structure only: the title, the headings, a colour palette, a text sample, the internal links. He then builds your version from that blueprint.

Use your own images

Attach an image to your message and say what it's for. Steve imports it into the project and wires it into the HTML — you never have to deal with file IDs or URLs.

Images are capped at 3 MB each. Need a picture you don't have? Ask Tyron to generate one in his own conversation, then bring it to Steve as an attachment — Steve doesn't generate images himself.

Export a ZIP

Say "export my site as a ZIP" and you get a download card with the whole project in it: your HTML, your CSS, your JavaScript, your images. Host it on any static host on earth. There is no lock-in and no proprietary format — it's just files.

The download lands in a private, owner-only bucket and is fetched with your own logged-in session. No public link to your site is ever created or stored.

The preview that comes back from the dead

The live preview runs in a sandbox that expires after about 10 minutes. That would normally mean reopening a month-old project shows you an error where your site used to be.

It doesn't. Open the Preview tab and the preview quietly rebuilds itself from the saved copy of your files — a couple of seconds — and there's your site. You'll see "Restarting the preview…", never a raw error, and never an infinite spinner.

The preview is temporary; a published site is permanent. If you want a URL that's up at 3am whether or not you're looking at it, publish it → Publishing your website.

Limits worth knowing before you start

And three things that don't exist yet, so you can plan around them:

• No version history. Only your project's current state is stored — there is no snapshot list, no rollback and no undo. If you love a version, export the ZIP.
• No custom domains. Published sites live at <your-slug>.unyo.site.
• Published sites are snapshots. Editing does not update your live site until you say "republish". The workspace flags this for you with an amber badge.

What it costs

Priced in credits, per action:

Building your bakery landing page costs 25 credits — two and a half cents — plus the model's real usage cost for the run. Anything that errors is refunded automatically. A build that fails costs you nothing.

Tips

• Front-load the detail. One rich first message beats six corrections at 15 credits each.
• Name your sections. "Hero, three-card feature row, testimonials, FAQ, footer with hours" gives Steve a blueprint.
• Use click-to-select for anything fiddly. "This button" beats "the button in the second section, the blue one, not the other blue one".
• Reading is free. Ask "show me the current index.html" as often as you like; it never costs a credit.
• Export before big rewrites. There's no undo, and a ZIP is 10 credits' worth of insurance.
• One conversation per site. Rename the conversation after the site — future you will thank you.

FAQ

Troubleshooting

"He said he changed it, but nothing looks different." Reload the preview from the panel header. If it's genuinely unchanged, check the transcript for a diff chip — no chip means no edit landed. Ask again, quoting the exact text you want replaced.

An edit didn't land. Ask Steve to read the file first ("show me the current index.html", free) so his rewrite matches the real current code, then quote the exact wording you can see on screen. If an edit genuinely errors, you're refunded.

A build stopped before it finished. If a build is cut off part-way, the project can be incomplete — files that finished are saved, but the file being written when it stopped isn't. Ask Steve to finish or rewrite the missing part (15 credits), or start over with a simpler first version you then extend.

The Preview tab shows "Restarting the preview…" then a retry card. The sandbox failed to come back. Hit retry. Your files are safe — they live in the durable project record, not in the sandbox, which is why the preview can be rebuilt at all.

My live site doesn't show my latest edits. Expected. Published sites are snapshots. Say "republish" (25 credits) and it updates at the same URL. The workspace shows an amber "unpublished changes" badge when the two have drifted apart.

A second site overwrote my first. Both were in the same conversation. Start a new conversation per site. If the first one is gone, there's no version history to restore it from — export ZIPs as you go.