Sites built with AI tools: one guide per stack
Every tool and framework that builds websites with AI ends up somewhere slightly different: a client-rendered app, a server-rendered page, a template, a theme. Each guide below covers why sites built that way converge, what the IntentGrid demo can and cannot read from them, and fixes you can make yourself without any product. One rule holds on all of them: IntentGrid changes the words for each visitor and never the design, and adaptation on your own domain is early access.
Last updated 2 October 2026.
Lovable
Client-rendered React apps, one stack for every project, and why the demo may see an empty page.
Read the guidev0
shadcn/ui and Next.js defaults, how to retheme them, and what a deployed v0 site serves.
Read the guideBolt.new
Apps built in the browser, what their HTML actually contains, and what to fix first.
Read the guideReplit
Apps built by Replit Agent, single-page versus server-rendered, and separating the marketing page from the app.
Read the guideCursor
Rules files, one content module, and a hand-rolled variant per channel.
Read the guideClaude Code
CLAUDE.md, real source material, and a one-pass audit of every headline.
Read the guideFramer
Templates, built-in AI features, and why animations do not play in the preview.
Read the guideWebflow
Template copy, interactions, CMS fields, and when to run a test instead.
Read the guideNext.js
The AI-generated Next.js site: what renders where, and per-channel copy done by hand.
Read the guideReact + Vite
Client-rendered by default, three ways to get the copy into the HTML, and broken deep links.
Read the guideAstro
Static by default, and the one client-only trap that hides your copy.
Read the guideWordPress
AI page builders, security plugins, and why page caching breaks hand-rolled personalization.
Read the guide
What holds on every stack
IntentGrid works on the HTML a page serves, not on the tool that generated it. If the copy is in that HTML, as it is on server-rendered and static sites, the demo can rewrite it. If the page is built in the browser, the demo receives an almost empty shell, and so does any crawler that does not run JavaScript.
On every stack it changes headlines, body copy and button labels, and leaves design, layout, prices and product claims alone. It measures nothing and it is not a traffic source. Today the working part is a sandboxed demo; adaptation on your own domain is early access, set up by hand.