Why I built PageHub

For years I built client sites on WordPress. Every project meant plugins fighting plugins, updates that broke things, and clients afraid to touch their own site.

I tried going headless. I tried Contentful and a handful of others. Each one fixed one problem and added two more: a separate front end to maintain, a content model the client couldn't follow, or a bill that grew with every seat.

So I started building the tool I wanted: a visual editor that produces clean, fast sites, with hosting included and nothing to patch.

AI changed how I build sites. Most of my client work now starts in a conversation with Claude. I describe what the client needs, and Claude builds it on PageHub through the MCP server, section by section. I review it, adjust it in the editor, and publish it to the client's domain.

So I rebuilt PageHub around that workflow. Everything I do on a client site day to day, an AI agent can do through MCP, and a person can do in the editor. You don't have to pick one.

• 25 minutes, start to finish. The Goalposts site went from nothing to published in 25 minutes.
• Clients editing their own sites. After I handed a site over to a home-exteriors contractor in the DC area, he started adding to it himself, and was surprised how easy it was.
• No AI required. Joel was impressed by how complete the editor is. He works on his site in it without touching AI at all.

PageHub is an independent project. It's me, building it and using it for real client work every week. If something's broken or missing, you're talking to the person who can fix it. Find me on Discord or X, or use the contact form.