AI progress is usually measured with grand-sounding benchmarks.
First it beat humans at chess, which was unsettling for chess people. Then it began acing advanced maths and medical exams, which is all very impressive. Then it started writing code, which felt rather more existential for developers.
I think WordPress has a benchmark like this too.
I call it the Screenshot Test.
Here it is: take a screenshot of a website, upload it to an AI system, and ask it to turn that design into a clean, editable WordPress page made of native blocks.
Not a pile of code that technically works but looks like it was assembled during a small electrical fire.
Not a fake demo.
A real WordPress page. Something you can open in the editor, tweak, move around, and carry on working with like a normal human being.
We are not quite there yet.
And that is interesting, because AI can already do some pretty dazzling things. Tools like Lovable, v0, Claude, and Cursor can spit out attractive websites in HTML, Tailwind, or React faster than most of us can find the right font pairing and wonder whether we are more of an Inter person.
But WordPress is a different beast.
Because this is not just about making something that looks right in a browser. It is about translating design into structure. The AI has to work out what is a heading, what is a paragraph, where groups begin and end, how spacing should behave, and how the whole thing should be built in blocks so it stays editable.
That is a much fussier job.
And that is why I think the Screenshot Test matters.
Not because screenshots are some magical new future. They are not. The screenshot is just the test.
What we are really asking is something bigger: can WordPress AI remove the grindy bit between having an idea and actually building the thing?
Because right now that gap is still full of fiddling. You see a design, open the editor, add blocks, move blocks, nest blocks, un-nest blocks, adjust spacing, wonder why one bit is 24 pixels off, and eventually get there through a mixture of patience, experience, and low-level resentment.
But once that gap starts to disappear, all sorts of new workflows open up.
Designers can go from mockup to editable page in seconds. Creators can turn inspiration into a working layout without rebuilding everything block by block. Teams can prototype much faster. Beginners can get somewhere good without first needing a minor in container hierarchy.
If anyone reading this is getting close to passing the Screenshot Test, I’d love to see what you’re building.
Leave a Reply