The brief said don't flatten the interactive sections. It didn't.

Twenty requirements, and one of them underlined: use my own content, not theirs.

The reference site’s best sections were the interactive ones — a pinned scroll switcher, a drag carousel, an autoplay slider. Flattening those into static blocks is the shortcut that makes an AI build look cheap, and it is the shortcut almost every tool takes. The brief explicitly forbade it.

WPOS opened the reference and actually looked at it, then said it needed a few details before it would build anything.

It planned a design system of tokens first, then built the interactive sections as interactive sections.

Rather than working from a description, it navigated to the reference and screenshotted it. Then it built, narrating as it went — the hero, the statement, the logo marquee, and the centrepiece: a services switcher pinned to the scroll, where the section holds while the image and text swap beneath you.

Eleven homepage sections run on one shared motion engine, and that engine degrades gracefully: with JavaScript off, or when a visitor has asked for reduced motion, the page still works.

It named what it could not do, rather than quietly working around it. The design wants video. WPOS cannot generate video, so it said so — and wired every media slot for one anyway. Until you drop a file in, the hero runs a slow push-in instead.

Then the part worth copying: it marked its own placeholders on the page itself. The statistics band — zero lost-time incidents, six hundred and thirty-eight projects — is invented, and it carries a printed note telling you to replace these figures before launch. Not a warning buried in a chat log. Printed, in the render, where anyone reviewing the page will see it.

The company name is invented too, for the same reason: the brief said use your own content.

• Six pages, built from one reference and a twenty-point brief
• Eleven homepage sections on a single shared motion engine
• The scroll-pinned services switcher built as specified, not flattened into static blocks
• Motion degrades gracefully with JavaScript off or reduced motion requested
• Every invented statistic labelled as a placeholder in the rendered page
• The one thing it could not do — video — stated plainly, with the slot wired for it

What this build actually used.

• Platform: WordPress with WPOS, native widgets across six pages
• Reference analysis: the reference navigated and screenshotted in a browser, rather than worked from a description
• Theme: a design system of tokens planned and laid before any section was built
• Motion: one shared motion engine driving all eleven homepage sections
• Interactive sections: a scroll-pinned services switcher where the section holds while image and text swap beneath you, plus a drag carousel and an autoplay slider — built as real interactions, not flattened to static blocks
• Accessibility: motion degrades gracefully with JavaScript disabled and when prefers-reduced-motion is requested
• Video: every media slot wired for video; a slow hero push-in stands in until a file is supplied, because WPOS cannot generate video
• Placeholder handling: invented statistics carry a printed replace-before-launch note in the rendered page

Will WPOS simplify complex interactive sections when it copies a reference?

Not when you tell it not to. Here the brief forbade replacing interactive sections with static ones, and the scroll-pinned switcher, carousel and slider were all built as working interactions on a shared motion engine.

Can WPOS generate video for a site?

No. It says so directly. In this build it wired every media slot for video and ran a slow push-in on the hero as a stand-in until a real file is supplied.

How do I know which figures on an AI-built page are real?

On this build, because it printed the answer on the page. The statistics band carries a note identifying the numbers as placeholders to replace before launch.

Start free for 30 days with 5,000 credits at wpos.ai. No card required, and nothing charges automatically. WPOS connects to any WordPress site, new or existing, on any host, and works alongside Gutenberg, Elementor, WooCommerce and Divi. Book a call with the founders at cal.com/algorismus/30min.