Legal Pages and Blank Pages
Two routes that skip the design thinking: formatted text, or an empty canvas.
Not every page is an argument. Some pages exist because they have to, and some exist to hold something you are putting together yourself. Two creation modes cover those.
Steps
Legal / Policy Page — paste the text
Set the page type, name and slug, then paste your text into the content area.
Formatting survives the paste: headings, lists and links are preserved, and you can paste straight from a word processor or a document editor. Webby formats it into a clean, readable page with proper sections.
It skips the narrative planning altogether, because there is no narrative to plan — the words are already decided. That makes it both quicker and cheaper than the full flow.
Use it for anything word-for-word
The mode is named for legal text, and privacy policies and terms of service are the obvious cases. It suits anything where the wording is fixed and must not be reinterpreted — a code of conduct, an accessibility statement, a regulatory disclosure.
If the words matter exactly as written, this is the mode. Any other route invites a rewrite you do not want.
Build Yourself — start empty
Set a name and a slug and you get a page with no blocks at all. No generation, nothing to approve, no charge.
You land in the editor with an empty canvas and add blocks one at a time, each described as you go.
Know when empty is the right start
Two cases make this the best choice rather than the slowest.
The first is a page that is mostly one embedded thing — a booking flow, an interactive tool, a search interface. There is no narrative to generate; you need a shell with your header and footer around it.
The second is a page you intend to assemble deliberately, section by section, because you know exactly what each one should be. Starting blank and adding four considered blocks can beat generating eight and deleting four.
Result
Either a formatted policy page ready to publish, or an empty page waiting for its first block.
