Shipping a WordPress site in two hours with Cove.run and Claude
A simple path for small brochure sites.
It's possible to build WordPress sites faster than ever.
I was talking shop with Craig Hobson from LaunchPress this week, and he told me about his dev workflow. He uses a nifty command-line tool called Cove.run to spin up local development environments, and then he hooks Claude Code into the local site and has it build everything out in just native Gutenberg blocks, with a custom plugin added here and there for specific features or flair.
He said he can get a site out in about an hour. Plus, building this way makes it possible to continue editing the site in the Gutenberg editor.
That sounded like the best of both worlds: an AI-assisted build out with the ability to touch pages and make manual edits as needed. Not every client wants to go through an AI agent to make page changes, despite the hoards of people on LinkedIn flocking to Astro and saying WordPress is cooked.
So I decided to try it. I had Claude rebuild a website I originally built with Astra using the default Twenty Twenty-Five theme.
Claude says the total working time was 4 hours 1m, but the reality is that I was:
- recording Loom videos for another project while Claude worked in the background, and only checking in with Claude between videos
- putting my kids to bed and chatting with my wife for a good stretch of that
I'm estimating that my total focused time was about two hours, maybe less. Some of the lift was working with Cove.run for the first time. I expect that time to decrease as I explore this workflow further.
How to do it
- Install Cove.run via the command line with
bash <(curl -fsSLhttps://cove.run/install-cove.sh) - Spin up a new site with
cove add yoursitename - Navigate to the directory that Cove creates for your local site and run
claude. If you haven't set up Claude Code, do that first and then runclaude - Tell Claude what you want it to build. In my case, I was having Claude rebuild a site that I threw up last year, so I used a prompt like this:
Read [example.com]: the homepage, [services], and [contact] pages. Write a reference/current-site.md summarizing the structure, copy, and calls to action. This is what you'll use to build a new site with just vanilla WordPress and the [Twenty Twenty-Five] theme.
Claude went to work and pulled all of the colors, fonts, logos, images, and content from the original site. As it worked, I fed it more context from other Claude chats that I have in a Project so it would have more info for the service pages.
I also told Claude what form plugin I wanted, and it downloaded it and configured a basic contact form. It even updated the Privacy Policy based on the form configuration.
When everything was done, Claude walked me through the process of pushing the local site to a staging environment on Siteground via SSH. No FileZilla, no messy copy/paste. It was super easy.
Gotchas
As in all things AI, speed does not equal quality. It pays to know the features and capabilities of the platform you're working on so you can correct the AI when it does dumb things.
When I went into the block editor, I noticed that style values were manually set for every single element, which defeats the point of a block theme and makes the site styles a mess to maintain. I knew that theme.json allows block styles to be set as predefined options in the editor, so I told Claude to fix that.
Claude loves adding eyebrows to everything, which is becoming a bit of an AI tell. Just because something is conventional doesn't mean that it's necessary. I had Claude remove all the eyebrows. Design judgment still matters—even for basic sites.
I had to swap my form plugin selection from Fluent Forms to Forminator because Claude didn't pause when the phone field did not offer validation (available only on Pro). It's too easy for people to mistype a phone number. For a service-based business that hinges on calling people back, accurate phone numbers matter. Light QA of key functionality is still necessary.
Depending on where your site lives, it may be more difficult to use Claude for continued edits. Hosts that allow for SSH access and file navigation through VS Code (like Kinsta) will work. This site is on Siteground, so pushing live means that edits fall on me from now on unless I figure out a partial pushing workflow between my local environment and Siteground.
What's next
The tedious part of building with WordPress is the initial setup—defining palettes, adjusting layout settings, configuring fonts, etc. Those steps take the same amount of time whether it's a 5 page build or a 50 page build. Using Claude to build up some scaffolding and get something live means that I have more time to focus on other aspects of marketing this business.
I think this approach is nice for developers and clients. Developers can build in a open-source platform that they're familiar with. Clients end up with sites that are simple, editable, and backed by boatloads of documentation on WordPress.org, YouTube, and the broader web.
For massive-large scale builds, I still believe in a classic-theme-with-child-theme approach with easy access to functions.php and style.css and all other theme files. I think it makes sense to architect the style guide and customize the site from the ground up—especially for the purposes of scalability.
But for small businesses that need a quick brochure site, I think this is the way.