Shapes, not blank pages
A blank editor asks the writer to remember the format. A declared shape tells them — and tells search engines at the same time.
The blank canvas problem
Every documentation tool opens a blank page and hopes. The result is predictable: eight guides in eight formats, and the ninth writer copies whichever one they found first.
What a shape is
A shape declares the parts of a piece. A how-to guide has a goal, prerequisites, steps and a check. A job posting has a location, a salary band, responsibilities. An incident has a severity and a state.
The editor opens as that outline. The page says which required parts are still empty. Neither blocks you — a shape is a scaffold, not a gate.
The part that surprised us
Once a page knows what its parts mean, the published HTML can say so. A role written through the careers shape emits JobPosting with its responsibilities and salary as fields — the things Google needs to show it in the jobs experience. An FAQ emits FAQPage. The author wrote a page; the structured data came along for free.
And because a shape is JSON Schema, an agent can ask what a piece needs before it writes one, then be told what it left out. Same declaration, three audiences: the writer, the crawler, and the machine.
0 comments