O1 / Website builder

From a clear brief to a website draft.

Describe the idea, inspect the preview, and refine the work before publishing.

Explore the public preview. Live AI requires a verified account; supported workflows depend on enabled tools and account limits.

See how it works

Website builderWORKFLOW WALKTHROUGHExample

EXAMPLE REQUEST

Build a two-page website for a fictional ceramics studio: a homepage and a workshop page. Use a quiet black-and-cream style, readable type, and strong mobile spacing. Show workshop dates as sample content. Add an inquiry form with validation; do not claim inquiries are delivered until a real destination is connected. Include an accessible menu and clear empty, loading, success, and error states.

Illustrative website brief

Pages: Homepage: studio introduction, selected work, and workshop link. Workshop page: schedule, details, and inquiry form.
Interaction: Validate the inquiry fields, keep entered text on failure, and explain where submissions go.

More example details

Preview review: Check the menu and form on a narrow screen. Confirm focus order, labels, and readable contrast.
Before publishing: Replace sample dates, connect the real submission destination, and test the complete form flow.

01 / THE WORKFLOW

What can o1 help you do?

The o1 AI website builder turns a project brief into a site draft in the signed-in Build workspace. Describe the purpose, audience, pages, and interactions you need. Build keeps the project and its preview together so you can inspect the result and request another focused change.

A useful first project might be a portfolio, a service business site, or an event page. Define what visitors should be able to do rather than asking only for a visual style. A contact form, for example, needs a destination for submissions and clear success and error states, not just an attractive field.

02 / THE BRIEF

Start with a specific prompt

Use this as a starting point. Replace the example details with your own task and constraints.

YOUR REQUEST
Build a two-page website for a fictional ceramics studio: a homepage and a workshop page. Use a quiet black-and-cream style, readable type, and strong mobile spacing. Show workshop dates as sample content. Add an inquiry form with validation; do not claim inquiries are delivered until a real destination is connected. Include an accessible menu and clear empty, loading, success, and error states.

This prompt is an example. Its outcome depends on the tools enabled in your workspace and the information you provide.

03 / GET STARTED

How to use the website builder

01
Open Build and create a project
Sign in, choose the Build workspace, and provide a project name and brief. Include the pages and the main task a visitor should finish.
02
Run the builder
Review your request and start the build. Inspect the actual progress and resulting preview; a proposed change in chat does not mean the files have already changed.
03
Request one focused revision
Point to a section or behavior: 'make the mobile menu keyboard accessible' or 'keep form values after an error'. State the desired outcome so the next preview is easy to compare.
04
Check the site, then publish
Review content, links, mobile layout, forms, and any connected services. Publishing is a separate action; use the workspace's publication controls when the draft is ready.

04 / YOUR CONTROL

A working preview needs a working checklist

Replace sample content

Remove placeholder contact details, invented quotes, sample dates, and claims you cannot support. Use your own images and copy where you have permission.

Test the complete interaction

Submit each form, follow the response to its destination, and test an error. A visual success state by itself does not prove data was saved or delivered.

Inspect mobile and accessibility

Use keyboard navigation, check focus indicators and field labels, and verify that headings and buttons remain readable on a phone.

05 / CURRENT SCOPE

Know the limits before starting

The public demo previews the chat and planning workspace. It does not edit files, produce a live website preview, or publish a website.
Build requires a signed-in account. Build and publication depend on the available service, your account limits, and the project's configuration.
Generated code and content need review. A draft does not guarantee accessibility, secure integrations, search rankings, or a successful launch.

Check the workspace's current availability and account limits before starting a job. Your chat and connected tools may have different capabilities from the public demo.

06 / QUESTIONS

Before your first task

Can the public demo build and publish my website?

The public demo previews the workspace and example briefs. To generate files, inspect a website preview, and publish, sign in with a verified account and open Build.

Can I revise an existing o1 Build project from chat?

The signed-in chat can prepare a handoff to one of your Build projects. You review the requested edit and start it in Build. A handoff card alone does not change or publish the project.

What should I include in a website prompt?

Include the audience, purpose, pages, visual references, required interactions, available assets, and how you will check success. Explain which content is sample and which services need a real connection.

GUIDES & TEMPLATES