Manage several websites across WordPress, Astro and Eleventy

The poster uses OpenClaw, alongside Claude Code and Codex, to manage and work across about five websites.

What They Did: The poster says they use OpenClaw to manage about five websites spanning WordPress, Astro, and Eleventy, alongside Claude Code and Codex so they can pick different coding agents for different tasks. The thread adds one concrete workflow around upkeep: people wait on updates, back up first, and in one case use Claude Code to clone the OpenClaw install on the same server, test and troubleshoot the upgrade there, then only update the real system if it passes.
How It Went: The poster says the setup has become genuinely useful for working across several sites, but updates are the weak point. They report that almost every update breaks something, and another commenter said it took Claude four update-and-rollback attempts to get from 5.28 to 7.1-2 working.
Worth Knowing: The main catch is upgrade risk: commenters describe treating updates like production deployments, with backups, snapshots, or a test replica before touching the live setup.

Try it yourself with OpenClaw

Look at the site projects in [folder paths] built with [WordPress, Astro, Eleventy, etc.] and do [task, such as update dependencies, fix broken links, or add a new page]. Work on one site at a time and run each site's build to confirm it still works. Summarize what changed per site, and ask me before deploying, pushing to production, or deleting anything.

Read the original ↗