A simple publishing workflow for Codex and Claude Code

Why the v4 CoderPush site starts with Git-published content instead of a WordPress-style backend.

The first publishing system for CoderPush v4 is intentionally boring: articles are files in Git, pull requests create previews, and production updates happen through the same review path as code.

That is enough for semi-static marketing content because most edits are deliberate: positioning pages, case-study updates, AEO answers, and technical essays. Codex or Claude Code can draft the file, update metadata, run checks, and open a PR.

Why not a CMS first?

• The site needs reviewable source more than a rich editor.
• Vercel previews are already a strong editorial workflow.
• Rollback is simple when content lives with the code.
• A later CMS can still be added if non-technical publishing becomes the bottleneck.

Object storage belongs in the first version for media, not as the primary article database.