content-publisher

Handles the publication workflow for AndesRC blog articles. Creates markdown files, triggers builds, submits to Google Search Console, and initiates promotion. Use as the final step in the content pipeline.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026⬇️2downloads

When & Why to Use This Skill

The Content Publisher skill automates the end-to-end workflow for blog article publication, bridging the gap between content creation and live distribution. It handles technical tasks such as markdown generation, WebP image optimization, and CI/CD deployment via Git, while simultaneously managing SEO requirements by submitting URLs to Google Search Console. This skill ensures a standardized, error-free publication process that includes automated social media snippet generation for multi-platform promotion.

Use Cases

  • Automating the deployment of blog posts for static site generators (SSGs) by managing file structures, assets, and Git commits.
  • Streamlining SEO workflows by automatically requesting indexing in Google Search Console immediately after a new article is published.
  • Enhancing content distribution efficiency by generating platform-specific social media copy for Twitter, LinkedIn, and WhatsApp.
  • Maintaining high quality standards through automated pre-publish checklists, including image compression and build verification.
namecontent-publisher
descriptionHandles the publication workflow for AndesRC blog articles. Creates markdown files, triggers builds, submits to Google Search Console, and initiates promotion. Use as the final step in the content pipeline.
authorAndesRC
version"1.0"

Content Publisher

Purpose

Execute the final publication workflow: file creation, build verification, search engine submission, and social promotion.

Publication Workflow

Step 1: File Creation

Directory Structure:

src/features/blog/content/
├── en/
│   └── {slug}.md
└── es/
    └── {slug}.md

Filename Convention:

  • Use the slug from frontmatter
  • Lowercase, hyphen-separated
  • Example: plan-10k-principiantes.md

Step 2: Asset Preparation

Cover Image:

  • Format: WebP (with JPG fallback)
  • Dimensions: 1200x630 (16:9 ratio, OG-optimized)
  • Size: <150KB
  • Location: public/images/blog/{slug}/cover.webp

Inline Images (if any):

  • Location: public/images/blog/{slug}/
  • Alt text: Include keyword naturally

Step 3: Build Verification

# Run local build to verify no errors
npm run build

# Check for:
# - Markdown parsing errors
# - Missing images
# - Broken internal links

Step 4: Deploy

# Commit and push to trigger Netlify deploy
git add .
git commit -m "blog: add {slug} article"
git push origin main

Step 5: Search Engine Submission

Google Search Console:

  1. Go to GSC → URL Inspection
  2. Enter the new article URL
  3. Request indexing

Sitemap:

  • Verify sitemap.xml includes new URL (auto-generated on build)

Step 6: Social Promotion

Prepare snippets for:

Twitter/X:

🏃 Nuevo artículo: [Título]

[Hook de 1 línea]

[Link]

#running #runners #correr

LinkedIn:

[Título del artículo]

[Párrafo de contexto - por qué es relevante]

Lee más: [Link]

WhatsApp Status:

  • Use cover image
  • Short caption: "[Título] - ¡Nuevo en el blog!"

Step 7: Monitoring Setup

Add to tracking:

  • Google Analytics goal/event for the page
  • GSC performance tracking
  • CTA click tracking

Quality Checklist

Pre-Publish

  • Frontmatter complete and valid
  • Cover image optimized and in place
  • All internal links work
  • Schema.org markup validated (schema.org validator)
  • Spelling/grammar checked
  • Preview on mobile

Post-Publish

  • URL accessible and rendering correctly
  • GSC indexing requested
  • Social posts scheduled/published
  • Added to internal tracking sheet

Output

A published, indexed, and promoted article with:

  1. Live URL on andesrunners.com
  2. GSC indexing requested
  3. Social promotion initiated
  4. Performance tracking enabled