From a sentence to a deployed website

Getting started

1. 1

   Create an account

   Create an account with an email address and a password. A workspace is made for you on first use - everything you build belongs to it.
2. 2

   Describe the website you want

   On the dashboard, write a sentence or two about the business. One line is enough to start; more detail gives the generator more to work with.
3. 3

   Review what came back

   You get a complete multi-page site: pages, sections, written copy, images and a matching brand kit. Nothing is a placeholder you have to hunt down.
4. 4

   Refine it

   Edit any section by hand in the visual editor, or tell the copilot what to change in plain language. Both go through the same validated operations.
5. 5

   Deploy it

   Connect your Vercel account and publish. The site is yours, in your account, on your domain.

Generating a website

A prompt is a description of the business, not a description of a web page. You do not need to ask for a hero section or a testimonials grid - the generator decides the structure from what the business is.

Useful things to include:

• What the business does, and its name if it has one
• Who it is for - homeowners, agencies, patients, brides
• The tone you want: warm, clinical, editorial, playful
• Anything concrete - a short menu, three service tiers, five years in business

The editor

The left rail holds four panels:

• Pages - add, rename, reorder and set the URL path and SEO title of each page.
• Sections - the running order of the current page. Select one to edit its fields, drag to reorder, hide one without deleting it.
• Assets - the project’s image library.
• Theme - the brand kit: colours, typefaces, corner radius, button style, density, light or dark.

The canvas renders the real site, not an approximation of it. Switching to tablet or mobile loads the page in a frame at that actual width, so the layout you see is the layout a phone gets - media queries included.

Edits save automatically. Undo and redo cover every change, including the ones the copilot makes.

Section library

Every page is a list of typed sections. There are 14, each with its own fields and layout variants:

Header and footer are site-wide: there is one of each, and a new page inherits them so navigation stays consistent.

The AI copilot

The copilot panel sits to the right of the canvas. It works at two scopes: the whole site, or the section you have selected. Scoping to a section keeps a request like “make this shorter and warmer” from touching anything else.

It is not a text box that rewrites your site as HTML. It calls the same named operations the editor’s own buttons call, so every change it makes is validated, undoable, and visible in the section list:

Brand kit

A theme is one set of values - brand colour, heading and body typefaces, corner radius, button style, density, light or dark - applied through CSS variables. That is why a theme change is instant across every page, and why the exported site needs a single stylesheet.

9 starting points are included:

• Studio Indigo
• Editorial Noir
• Midnight Neon
• Warm Clay
• Clinic Blue
• Soft Pastel
• Court Lime
• Cobalt Press
• Ember Press

Every value stays editable afterwards. A preset is a starting point, not a lock-in.

Images

The asset panel searches stock photography and adds the result to the project library. Sections that take an image pull from that library, or from any image URL you paste. Generated sites arrive with photography already in place, chosen to match the business described.

Preview

Preview opens the site on its own isolated route, with no editor chrome and no studio navigation - the same markup that gets deployed. Use it to check a site the way a visitor sees it before publishing.

Deploying to your own Vercel account

A published site belongs to the person who made it, so it deploys into your Vercel account rather than ours. That is what lets you point a domain at it, read its analytics, and keep it if you ever stop using this studio.

Connecting your account

Open Deploy in the editor and choose Continue with Vercel. You approve the connection on vercel.com - for your personal account or for a team you belong to - and come straight back. If you have no Vercel account yet, creating one is free.

Your access credential is encrypted before it is stored and is never shown back to you or to anyone else in your workspace; the dialog displays only the account name it belongs to. Disconnecting removes it. Sites you already published stay live in your account, because they were never in ours.

What actually gets published

Plain HTML, one precompiled stylesheet, and nothing else. No framework, no build step, no server code. The only JavaScript is a short helper that turns the contact form into a mailto: compose window. The deploy dialog lists every file and its size before you publish.

Because there is no runtime, the site is fast by construction and cannot break in the ways a generated application can.

Build status and your URL

The dialog follows the build to completion and shows the production URL when it is live, along with a link to the deployment in your own Vercel dashboard. Every deployment is listed in the project’s history.

Custom domains

Domains are attached in your Vercel dashboard, against the project the deployment created. Because you own the project, you do not need us in that loop.

Current limits

Worth knowing before you plan around it:

• The contact form composes an email through mailto:. There is no form backend, so nothing is stored and nothing needs a server.
• No e-commerce, memberships or logins on generated sites.
• No custom code blocks. Sections are typed, which is what keeps a generated site safe to edit and safe to publish.
• Blog posts are pages, not a CMS with a feed.

Getting help

Support has the ways to reach us and what to include so we can help quickly. For questions about the account you deploy into, Vercel’s own documentation covers domains, analytics and billing.