blog-publish

Blog Publish

Push a completed blog article to the CMS -- upload images, create CMS item, sync components. Final step in the blog production pipeline.

Trigger

User invokes /blog-publish [slug] or says "publish the blog", "push to CMS", "upload the article"

Examples:

• /blog-publish how-we-built-our-first-feature
• /blog-publish product-launch-announcement

Prerequisites

• Copy: {{CONTENT_OUTPUT_DIR}}/blog/[slug]/copy.html
• Metadata: {{CONTENT_OUTPUT_DIR}}/blog/[slug]/metadata.json
• Exports: {{CONTENT_OUTPUT_DIR}}/blog/[slug]/exports/*.png
• QA report should show READY status

If any are missing, report which and stop.

CMS Configuration

• Collection ID: {{CMS_COLLECTION_ID}}
• Field IDs (map to your CMS schema):
  • Title: {{CMS_FIELD_TITLE}}
  • Content: {{CMS_FIELD_CONTENT}}
  • Cover: {{CMS_FIELD_COVER}}
  • Date: {{CMS_FIELD_DATE}}
  • Author: {{CMS_FIELD_AUTHOR}}
  • Excerpt: {{CMS_FIELD_EXCERPT}}
  • Category: {{CMS_FIELD_CATEGORY}}

Steps

0. Staging Preview Gate

Before any publish work, confirm the staging HTML exists at staging/blog/[slug]-blog.html.

If the file does not exist, prompt and exit without publishing:

Staging HTML not found at staging/blog/[slug]-blog.html. Run /blog-assets [slug] first to build the staging page, then review it in your browser before publishing.

If the file exists, ask:

Have you reviewed the staging page at staging/blog/[slug]-blog.html? (yes/no)

Only proceed to Step 1 if the user answers yes. Otherwise, stop.

0b. Clean Export (strip internal drawer)

Before uploading the staging HTML content to the CMS, produce a clean export with the internal version drawer stripped:

mkdir -p staging/exports
bash scripts/export-staging.sh \
  staging/blog/[slug]-blog.html \
  staging/exports/[slug]-blog.html

Use staging/exports/[slug]-blog.html as the source for CMS upload — NEVER upload the staging file directly (it contains the internal review drawer). The clean export has all data-internal elements removed.