Skip to content
MightyBuilder docs

Documentation

How to build, edit and publish a website by talking to it — every screen in MightyBuilder, in plain language.

Getting started

  • Welcome What MightyBuilder is, who it is for, and the one idea that makes the rest of these pages make sense: you describe the site and the AI writes it.
  • How editing works The AI writes drafts and publishes nothing. Understanding that one rule explains the Publish button, the badge beside it, and why your change is not live yet.
  • Create an account Signing up takes a minute and asks for no card. Three ways in, why everybody confirms an address, and the free credits a new account starts with.
  • The dashboard Where your sites live and what every screen inside one is for: the rail, the top bar, the Publish badge, and the AI panel that follows you around.
  • Your first site From an empty account to a site somebody can visit: describe what you want, let it build, look at the pages, and press Publish once.

Editing with AI

  • What it can change Where the builder's reach starts and stops: it writes pages and settings, moves addresses, looks things up — and deletes nothing and publishes nothing.
  • The brief The highest-leverage field in the whole product. What to put in it, what to keep out of it, and why the AI reads it on every single turn.
  • Undo a change Every turn that writes to a page takes a checkpoint first, so asking for the last change to be undone restores the words without moving the address.

Pages and blocks

  • Pages Making a page, nesting it inside another, and choosing the homepage. Where a page sits in the tree is what gives it its address.
  • The date on a page Every page has a publication date. On most it does not matter; on anything that appears in a list it decides the order, and backdating is how you fix that.
  • Blocks A piece of a page kept as its own document, so one header or one card design can appear in many places and be changed in exactly one.
  • Passing something into a block What lets one card design serve a blog index, a homepage strip and a section page without becoming three near-identical copies of each other.
  • Hiding and deleting Enabled, disabled and trashed: taking a page off the live site without losing it, and the single action in the product that really destroys something.

Content that fills itself in

  • A page's own details Show a page's title, date, summary or picture without typing any of them twice.
  • Why a list goes stale Nine hand-written cards, a tenth article, and nothing to notice. The problem stated before the tool, and the test for whether a list needs one at all.
  • A blog index, start to finish The worked example: a parent page, its children, a card written once, and the loop that lists them newest first without anybody maintaining it.
  • What a page knows about another page Every field a listing can use, what each is for, and why a list can show you a page's summary but never a paragraph out of its middle.
  • Sorting and filtering where, sort, reverse and limit — and the one mistake that makes a list quietly wrong: filters written on the for line are ignored entirely.
  • Articles The second kind of thing a site holds, and the one question that tells it from a page. An article belongs to nothing, so the page listing it owns nothing.
  • Collections Portfolio pieces, team members, products: a kind of thing with a page each. Fields every item has, a list that keeps itself, and one layout around them all.
  • An item's fields The types a collection's fields can have, how a page prints them, and why a phone number, a link and a picture each get a little more care than the rest.
  • Site fields Data the whole site shares, like opening hours or a row of badges, kept once and looped over by any page: a change is one edit, and no page is rewritten.
  • Tags The other way of grouping things: a word on a post that a list can filter by. What a tag is, what it deliberately is not, and how to build a page for one.
  • Your feed Every site has one, at /feed.xml, listing your newest articles. Who reads it, how they find it without being told, and what a rename does to it.
  • Visitors The card on your Overview: page views counted as your pages are served, with no script and no cookie, what is left out, and why visitors is an estimate.
  • Dates Publication date against last changed, why fixing a typo should not move an article to the top of the blog, and how to backdate one you are importing.
  • When not to use a loop Most lists should stay written out. One test decides it: if adding a page elsewhere should change this list, loop it — and if not, do not.
  • When something is wrong What publishing refuses and why, in the validator's own words — the three messages you are most likely to meet, and what each one is telling you.

Forms

  • Adding a form Ask for a contact form and get one that works, on Pro. The fields in the markup are the fields — there is nothing to configure and nothing to connect first.
  • Where submissions go Each form's own Submissions tab: emails to you and back to the sender, webhooks to everything else, and why a form with nowhere to send will not publish.

Design and pictures

  • Colours, fonts and CSS The theme holds your colours and fonts by name, every stylesheet reads them as CSS variables, and there is no hidden stylesheet underneath.
  • Pictures Upload one, generate one from a description, or import one the AI can see. Sizes, formats and descriptions are handled for you.

Domains

  • Your address and your domain Every site works from the moment you publish. Connecting a domain you own comes with Pro, takes two DNS records, and rebuilds nothing.

Publishing

  • Drafts and Publish Every record has two versions: the draft you are editing and the one the internet can see. Publish promotes all of them at once, and never a page alone.
  • Addresses and redirects How a page gets its address, what happens to the old one when you rename it, and why the homepage lends no segment to the pages beneath it.

Your account

  • Credits What spends them, what keeps a site online, and what happens at zero. Credits are bought once, never expire, and belong to a site rather than an account.
  • Signing in Three ways in and one account, why signing in with a different address makes a second one, and why there is a sign-in link instead of a password reset.