OpenAssistantAPI
→

Website Builder

Describe the site you want in plain language — your assistant builds and publishes a real, live one.

You don't need to know how to code, or hire anyone, to get a real website online. Just tell your assistant what you want — a landing page for your business, a portfolio to show off your work, a simple site for a project you're starting — and it builds it for you. No templates to wrestle with, no settings to configure.

How it works

Describe the site in your own words. You can be as specific or as loose as you like:

  • "Build me a landing page for my dog-walking business, with my phone number and a photo gallery"
  • "Make a simple portfolio site with a bio, my resume, and links to my work"
  • "Create a one-page site announcing my new podcast"

Your assistant takes it from there. It builds the site in your cloud computer, the same workspace it uses for all its other hands-on work, and checks its own work in a real browser before showing you.

Previewing and going live

While your assistant works, it can give you a preview link that updates as it makes progress, so you can see the site before anyone else can. Publishing is a separate step: your assistant only publishes once you've asked for it to go live.

Publishing follows your supervision settings. Depending on how you've set things up, the publish either goes through right away or waits in your dispatch cart for your approval, with a preview of the site shown alongside it. This applies even when you explicitly asked for the site to be published, so don't be surprised if it shows up as pending. Once it goes through, publishing is instant: the site is made of static files, so there's no build to wait for.

Every site gets a real, working web address you can share right away, with a customer, a friend, or on social media. Sites are static (plain HTML, CSS and JavaScript, or a framework app exported to static files), so features that need a server running behind the page, like logins or a database, aren't supported.

Making changes

Your site isn't locked in once it's published. Just keep talking to your assistant:

  • "Make the header a different color"
  • "Add a contact form"
  • "Swap out that photo for this one"
  • "Add a page for testimonials"

Edits are made on a separate working copy (a branch), so the live site isn't touched until you approve the next publish. Your assistant then republishes at the same address, so any links you've already shared keep working. Experiments you don't like can be discarded without affecting the live site.

Managing your sites

Sites belong to your team, so teammates can see and continue each other's sites. From the Websites page (once it's enabled for your account) you can see each site's branches, preview any of them, publish one, and browse version history. Earlier versions that were once live can be previewed or reverted to. You can also connect your own custom domain (you'll be given a DNS record to add at your domain provider to verify ownership), and delete a site, which also goes through your approval settings. You can ask your assistant for a downloadable copy of a site's files at any time, for example to back it up or host it yourself.

Tips for good results

Be as descriptive as you'd like — mention colors, the mood you're going for, what sections you want, and who the site is for. The more your assistant understands about what you're trying to say to your visitors, the better a first draft it can give you. And if the first version isn't quite right, that's what the changes are for — you can ask for as many tweaks as you like.