How I use AI to build your site
AI writes code and runs checks with me. It never writes your words, and a person tests every page.
In this guide
I use AI to build Rosette sites. This page says what it does, what it never does and why that matters to you. Pop Pop Studio's position on AI across everything we make is on our AI statement.
What AI does
It writes most of the code, with me. I describe each page type, what goes on it and the standards it has to meet. The AI writes the code and I read it. This is why a Rosette costs what a DIY site costs and not what an agency costs.
It runs the checks. Every page goes through automated accessibility, speed and code standard tests before I look at it. The AI runs them, reads the results and fixes what they find, then I check the fixes.
It looks at your site the way different visitors would. With a screen reader, with a keyboard only, in high contrast mode, on a slow phone, in dark mode. Before I do the same by hand.
It helps me move your words across. When you already have a website, the AI copies your pages into the new site exactly as they are, so nothing is lost or retyped.
What AI never does
Write or rewrite your words. Your pages say what you wrote, as you wrote it, unless you ask me to change something. Where a sentence is hard to read, Dawn, our plain English checker, flags it, and Dawn uses no AI at all.
Choose how your site looks. Your colours, your photos and your way of talking come from you and from our conversation. Each design is drawn for you, and I decide what is right, not a model.
Decide a page is finished. I test every page with a keyboard and a screen reader, and I read it, before it goes live. Nothing goes on your site that a person has not checked.
See anything private. Your website is public, and that is what the AI works on. Your passwords, your email and your clients' details are not part of it.
Why this is different from a site a model made in a minute
AI website builders make a whole site from a prompt and it looks fine. Then someone using a screen reader finds buttons with no names. Someone using a keyboard gets stuck in a pop-up with no way out. A parent on an old phone waits for a page that never finishes loading. I have reviewed sites like this that carry an accessibility statement saying they meet the standard, and it fails on the first page.
The difference is not the tool. It is a person who knows the standards, reading everything that comes out of it, and testing it the way your visitors will use it.
Ready to talk? Book a chat