Here is the workflow. I pull out my phone. Open Claude. Tap Code. Select the repo. And I start talking.
That is it. That is the entire publishing pipeline.
Two Modes, One Conversation
Claude Code on iOS gives you two entry points: Plan and Code. Plan is for when the idea is still forming — when I want to think out loud, sketch structure, test whether something holds together before I commit to building it. Code is for when I know what I want and I am ready to ship.
Most posts start in Plan. I will have a seed — a phrase, an observation, something that has been sitting in my head for a day or two — and I will talk it through. Not in a text editor. Not in a notes app. In a conversation with something that can push back, ask what I mean, and help me find the structure hiding inside the impulse.
When the shape is clear, I switch to Code. Same repo, same context, same conversation. Now we are writing — drafting the HTML, setting the frontmatter, matching the tone and cadence of what I have published before. Revising. Fact-checking claims. Tightening sentences. Then committing, pushing, and letting Cloudflare Pages do the rest.
The line between ideation and execution is not a handoff anymore. It is a mode switch inside the same thread.
From One Page to 1,100
The thing that still catches me off guard is the scale.
Before this workflow existed, making a change meant opening one file, editing it by hand, saving it, and repeating that for however many pages needed the same treatment. Updating a nav link across a site with hundreds of pages was not a technical challenge — it was an endurance test. The kind of work that made me close my laptop and go do something else.
Now I describe the change once. Claude applies it everywhere it needs to go. One conversation can touch a single blog post or ripple across 1,100 pages of a production site. The scope is not limited by my patience anymore. It is limited by my clarity — how well I can describe what I want.
That turns out to be a much better constraint.
Why Mobile Matters
People assume the serious work happens at a desk. And some of it does. But I have shipped posts from the couch, from bed at midnight when an idea would not let go, from a parking lot between errands. Not because I am addicted to productivity — because the friction dropped to zero.
When publishing a blog post requires the same effort as sending a text message, you publish more. You capture ideas when they are sharp instead of waiting until they dull. You stop treating writing as an event that requires a desk and a block of free time and start treating it as a thing you just do, whenever the thought is ready.
The phone is not a lesser device for this work. It is a different cockpit for the same aircraft.
The Conversation Is the Tool
What I keep coming back to is how natural this feels. There is no IDE to configure. No build step to remember. No deployment script to trigger. I talk. The code changes. The site updates. The feedback loop is so tight it barely registers as a loop at all.
And the conversation carries context. Claude knows the repo structure, the frontmatter format, the category taxonomy, the RSS feeds that need updating. I do not re-explain my site every time I sit down. I pick up where I left off — or start fresh and the CLAUDE.md file does the briefing for me.
This is what people mean when they talk about agentic workflows, but the phrase makes it sound more complicated than it is. It is just a conversation. You talk about what you want. It happens. You refine it until it is right. Then you ship.
What Actually Ships
Every post on this site — including this one — follows the same path:
- Idea. A seed lands. I open Claude on my phone.
- Plan. We talk through the structure. Is there a real thesis? Does it hold?
- Draft. Claude writes the HTML. I read it, push back, revise.
- Fact-check. Claims get verified. Links get validated. Style gets matched.
- Publish. Git commit. Git push. Cloudflare builds. The post is live.
Five steps. One conversation. No context switching between apps or environments. The repo is the CMS, the conversation is the editor, and the phone is the office.
From editing one page at a time to managing 1,100 — it never stopped being a conversation. The conversation just got a lot more capable.
The Protocol: The best publishing tool is the one that disappears. When the workflow is a conversation, the distance between thinking something and shipping it collapses to near zero. The phone is not the compromise. The desk was the bottleneck.
