A block editor sounds simple and is not. The parts that make it usable are the parts that are expensive to build, which is why the React page builders that existed were not good enough to adopt.

Blocks reorder by dragging. Not a crude move-up and move-down, but a proper sortable list with drop indicators that show where a block will land before you release it, the placeholder shifting and the layout reflowing under the cursor. That is the interaction a person coming from Elementor expects and rarely gets from a builder someone rolled themselves, because doing it well in a browser is genuinely hard.

Every block has a settings panel, organized as accordions, so that a block with a dozen options is a set of labeled sections instead of an unreadable stack of controls. Color, spacing, shadow, alignment, link, each in its place, each editing the one block selected and nothing else.

What renders in the editor is the page itself. Every block draws with the same component the public site uses to draw it. What is being edited and what will ship are one and the same, edited in place, at full size.

And there are a lot of blocks. Not a starter set of five, but a library already deep and still growing, searchable because there are too many to scroll. It runs from the obvious ones, a hero, a heading, an image, a gallery, a button, a quote, a link, out to a long tail of more specific pieces a page turns out to need. Each is a typed block with its own settings. Even text is a block, edited as a structure and not as raw tags. Building the editor was half the work. Building enough blocks to make a real page with is the other half. That work does not end. It was built to be used, not to be shown once.

None of this was built for an AI. It was built for a person, because when it was built there was no AI, and a person had to be able to make a page.

When the model arrives, it will not get its own private way to make pages. It will write into the same blocks a person does, dropping a hero block a person can open and rewrite, revising a page a person laid out. One editor, one definition of what a page is, because the editor was there first and the model will be taught to speak its language. The common alternative, an AI that emits HTML a person then has to wrangle, is the worse one.

The builder is also the last gate before anything ships, and it is where the person stays in charge. Even once the AI can draft a whole page, that draft is a starting point and not the finished one. A person opens the builder to make the small changes, the fine-tuning, the adjustments a model will not think to make, because the page is theirs and they can see what it should be. The AI will do the heavy work of generating a page. The fine-grained control over what it finally becomes stays with the person. The builder is built for both, the science of the machine and the art of the human eye.

The same holds downstream. The block model the builder writes is the one that will render a page to both a website and an email. Whatever gets built on top will work on these same blocks. There is no second content system beside the first. There is the builder, and then there is whatever gets built to run through it.

The builder is the part that will end up least visible. The pitch will be the AI. What the AI will stand on is a hand-built block editor that came before it, the one I made because I wanted Elementor without WordPress and could not buy it.

That is usually how it goes. The part that draws the eye is rarely the part that took the most work, or the part everything else needs in order to exist. The AI will be the reason people look. The builder is the reason it will have somewhere to write, and the reason a person is never stuck with a page they cannot change. It came first. It was the hard thing. It will be underneath everything that follows, and in the person's hands whenever they want to adjust what they see. Replacing Elementor was the whole idea. Everything after will be built on that.