pro-seo-publish
Turns an approved draft into a live page. Site-specific: it is wired to a particular repository and deploy pipeline.
Requires Site-specific wiring. Bound to one repository and deploy pipeline. Adapt before reuse.
Run it
/pro-seo publish [draft-file or slug]When to reach for this
Publish SEO content to theprocoders.com. Converts approved content drafts into Next.js article components, registers them in the site's blog system, creates a publish branch, merges to main, and pushes so the automatic pipeline deploys. Handles new posts, page upgrades, and post-publish indexing.
What you get back
- A branch per publish, merged to main so the deploy pipeline ships it
- Article components registered in the site's blog system
- Post-publish indexing submission
Reading the result
Site-specific: it is wired to one repository and one deploy pipeline, so adapt it before reuse elsewhere. It enforces hard gates before publishing — no unresolved placeholders, a clean working tree, a fresh main, and a build that passes — because the failure mode it exists to prevent is shipping a draft with brackets still in it.
What it covers
- Hard gates
- The site's content architecture
- Publish workflow
- Rollback
- Related skills