Today I went from a parked domain to two live WordPress sites, working almost entirely through Claude. Here’s the honest log, including the part that broke.
What shipped
- aarontudor.com: this site, where I learn Claude in public and share project ideas, each with a one-click LinkedIn share link.
- aviation.aarontudor.com: a Customer Success field guide to Veryon’s aviation maintenance software, built from 70 public sources.
How the work was split
- Research: Claude searched the web and built a ranked source list for the aviation project.
- Build: Claude wrote two custom block themes (no page builder) and checked every template before packaging.
- Deploy: Claude drove my browser to create the subdomain, install WordPress, upload the themes and take the sites live. I stepped in for anything involving passwords.
- Audit: a separate agent reviewed SEO, accessibility and CSS. A third agent tuned plugins and caching.
What broke, and the fix
Midway through, the whole domain stopped resolving. The cause was old name servers left over from an expired hosting package. They were still assigned to the domain but no longer answered for it. Switching to my host’s current default name servers brought everything back within minutes. Lesson: when a site “won’t load,” check DNS before touching WordPress.
Takeaways on vibe coding
- Describe the outcome, not the steps. “Make the aviation site about Customer Success for Veryon” was enough to restructure a whole site.
- Use a second agent to check the first one’s work. The audit caught real accessibility issues.
- Keep a human on anything irreversible: name servers, passwords, publishing.
Building something similar? Connect with me on LinkedIn. I’m happy to compare notes.
Leave a Reply