essay-publishing-pipeline
Publish essays and long-form content through a structured pipeline from draft to distribution. Covers markdown-to-HTML conversion, metadata management, cross-posting strategies, and RSS/Atom feed generation. Triggers on essay publishing, content pipeline, or blog deployment requests.
What this skill does
# Essay Publishing Pipeline
Move written content from draft through editing, formatting, and multi-platform distribution.
## Pipeline Architecture
```
Draft → Edit → Format → Metadata → Build → Publish → Distribute
↑ │
└──────────── Feedback Loop ───────────────────────────┘
```
### Stage Definitions
| Stage | Input | Output | Tools |
|-------|-------|--------|-------|
| Draft | Ideas, notes | Raw markdown | Editor, voice notes |
| Edit | Raw markdown | Polished markdown | Linter, peer review |
| Format | Polished markdown | Structured content | Frontmatter, templates |
| Metadata | Structured content | Enriched content | Tags, categories, SEO |
| Build | Enriched content | HTML/PDF output | SSG, Pandoc |
| Publish | Built output | Live content | Deploy, CMS API |
| Distribute | Published URL | Cross-posts | RSS, social, newsletter |
## Content Structure
### Markdown with Frontmatter
```markdown
---
title: "On the Architecture of Automated Systems"
subtitle: "Why eight organs beat one monolith"
author: "Author Name"
date: 2026-03-20
updated: 2026-03-20
status: published
tags: [architecture, automation, organvm]
category: systems-thinking
series: "Orchestration Essays"
series_order: 3
abstract: >
A 2000-word exploration of why modular organ-based
architecture outperforms monolithic automation.
canonical_url: "https://example.com/essays/architecture-of-automated-systems"
---
# On the Architecture of Automated Systems
Opening paragraph that hooks the reader...
```
### Essay Taxonomy
| Field | Purpose | Example |
|-------|---------|---------|
| `status` | Workflow state | draft, review, published, archived |
| `tags` | Topic classification | [architecture, automation] |
| `category` | Primary category | systems-thinking |
| `series` | Multi-part grouping | "Orchestration Essays" |
| `canonical_url` | SEO canonical | Primary publication URL |
| `abstract` | Summary for feeds/cards | 1-2 sentence summary |
## Markdown Processing
### Conversion Pipeline
```bash
# Markdown → HTML with Pandoc
pandoc essay.md \
--from markdown+yaml_metadata_block \
--to html5 \
--template template.html \
--highlight-style tango \
--toc \
--toc-depth=2 \
--output essay.html
# Markdown → PDF
pandoc essay.md \
--pdf-engine=weasyprint \
--css style.css \
--output essay.pdf
```
### Static Site Generator Integration
```python
# Build script for essay collection
from pathlib import Path
import yaml
import markdown
def build_essays(source_dir: str, output_dir: str):
essays = []
for md_file in sorted(Path(source_dir).glob("*.md")):
text = md_file.read_text()
frontmatter, content = text.split("---\n", 2)[1:]
meta = yaml.safe_load(frontmatter)
if meta.get("status") != "published":
continue
html = markdown.markdown(content, extensions=["fenced_code", "tables", "toc"])
essays.append({"meta": meta, "html": html, "slug": md_file.stem})
for essay in essays:
output = Path(output_dir) / f"{essay['slug']}/index.html"
output.parent.mkdir(parents=True, exist_ok=True)
output.write_text(render_template(essay))
build_index(essays, output_dir)
build_rss_feed(essays, output_dir)
```
## RSS/Atom Feed Generation
```python
from datetime import datetime
import xml.etree.ElementTree as ET
def build_rss_feed(essays: list[dict], output_dir: str):
rss = ET.Element("rss", version="2.0")
channel = ET.SubElement(rss, "channel")
ET.SubElement(channel, "title").text = "Essay Collection"
ET.SubElement(channel, "link").text = "https://example.com/essays"
ET.SubElement(channel, "description").text = "Long-form writing on systems and culture"
for essay in essays[:20]:
item = ET.SubElement(channel, "item")
ET.SubElement(item, "title").text = essay["meta"]["title"]
ET.SubElement(item, "link").text = f"https://example.com/essays/{essay['slug']}"
ET.SubElement(item, "description").text = essay["meta"].get("abstract", "")
ET.SubElement(item, "pubDate").text = essay["meta"]["date"].strftime(
"%a, %d %b %Y 00:00:00 GMT"
)
tree = ET.ElementTree(rss)
tree.write(f"{output_dir}/feed.xml", xml_declaration=True, encoding="utf-8")
```
## Cross-Posting Strategy
### POSSE (Publish on Own Site, Syndicate Elsewhere)
```
Own site (canonical) → Medium → Dev.to → LinkedIn → Newsletter
↗ ↗
RSS feed triggers automation
```
### Cross-Post Formatting
| Platform | Format | Limits | Notes |
|----------|--------|--------|-------|
| Own site | Full HTML | None | Canonical URL |
| Medium | Markdown import | None | Set canonical URL |
| Dev.to | Markdown + frontmatter | None | Use API for automation |
| LinkedIn | Plain text + link | 3000 chars | Excerpt + link to full |
| Newsletter | HTML email | Images inline | Adapt layout for email |
### Automated Cross-Posting
```python
async def cross_post(essay: dict):
canonical = essay["meta"]["canonical_url"]
# Dev.to
await devto_api.create_article(
title=essay["meta"]["title"],
body_markdown=essay["content"],
canonical_url=canonical,
tags=essay["meta"]["tags"][:4],
published=True,
)
# Newsletter
await newsletter_api.create_campaign(
subject=essay["meta"]["title"],
html=render_email_template(essay),
)
```
## Quality Gates
### Pre-Publish Checklist
- [ ] Spell check and grammar review
- [ ] Links verified (no 404s)
- [ ] Images optimized and alt-text present
- [ ] Frontmatter complete (title, date, tags, abstract)
- [ ] Canonical URL set
- [ ] Open Graph / social card metadata present
- [ ] RSS feed validates
- [ ] Mobile rendering verified
### SEO Metadata
```html
<meta property="og:title" content="Essay Title">
<meta property="og:description" content="Abstract text">
<meta property="og:type" content="article">
<meta property="og:url" content="https://example.com/essays/slug">
<meta name="twitter:card" content="summary_large_image">
```
## Anti-Patterns
- **Publishing without canonical URL** — Leads to duplicate content SEO penalties
- **Manual cross-posting** — Automate with APIs and RSS triggers
- **No RSS feed** — Essential for syndication and discoverability
- **Draft content leaking** — Always check `status` field before building
- **No versioning** — Track `updated` date for revised essays
- **Platform-first publishing** — Always publish on own domain first (POSSE)
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".