PageMotorPro
I’m working out how to use PageMotor and Claude Code together to build and manage real websites. This is where I document what I find — the wins, the dead ends, and everything in between.
PageMotorPro / 2025
About this site
PageMotorPro is my learning-in-public space. I use PageMotor — a powerful plugin-first CMS — combined with Claude Code to design, build, and iterate on websites faster than I could by hand. The goal right now is to understand what’s possible. Over time this site will become a resource for anyone curious about PageMotor and what AI-assisted CMS management actually looks like.
The workflow combines PageMotor’s block-and-instance CMS architecture with Claude Code’s ability to read, write, and reason about the whole system at once. No context-switching between a visual editor and a code editor — it’s one continuous conversation with the site.
I.
I describe what I want — a new section, a design change, a content type. Claude reads the existing codebase and PageMotor’s MCP tools to understand the current state before touching anything.
II.
Using PageMotor’s API via MCP, Claude can create blocks, write templates, deploy CSS, and update content — all without leaving the conversation. I review and approve before anything goes live.
III.
What works gets written up here as an article. What doesn’t gets noted in the failures log. Both inform the next session. The site itself is the record of how this process evolves.
How I got Claude to redesign this site in a single session — and what broke along the way
A complete walkthrough of using the design-generation skill and PM_Design_Conversion to produce a new theme from a brief, deploy it to PageMotor, and debug the things that inevitably went wrong.
PageMotor’s block-and-instance model, explained for developers used to WordPress
The mental model shift you need to make when coming from a post-and-page CMS to PageMotor’s nested container architecture.
Why PageMotor’s SCSS compilation times out via MCP — and the workaround that actually works
The _save-css timeout problem, how the static file and database diverge silently, and why an HTML_Box in the HTML_Head block solves it.
See it in action
The Demo page walks through a complete session: from an empty CMS install to a designed, deployed site. No editing in code files, no admin panel juggling — just one conversation.
The newsletter
When I figure something out — or when something breaks in an interesting way — I write it up. Subscribers get it first. No noise, no schedule pressure. Just honest notes from someone learning in public.
No spam. Unsubscribe any time.