Stage 7: Publishing and Distribution
Session 8.8 · ~5 min read
The Pipeline Does Not End at "Final Draft"
A piece of content exists to be read. Until it is live on a platform where your audience can find it, the pipeline is incomplete. Publishing is a distinct stage with its own tasks, its own automation opportunities, and its own failure modes.
Stage 7 covers: uploading to platforms, setting metadata, scheduling, cross-posting, and archiving. Each of these steps can be partially or fully automated.
The Publishing Workflow
Platform-Specific Requirements
Every publishing platform has its own format requirements, metadata fields, and quirks. What works on your self-hosted website does not paste cleanly into Medium or LinkedIn. WordPress wants categories and tags. Email platforms want a subject line and preview text. Each platform is a distinct output target.
| Platform | Required Format | Key Metadata | Automation Method |
|---|---|---|---|
| Self-hosted (WordPress) | HTML or WordPress XML | Title, excerpt, categories, tags, featured image, slug | WP REST API or XML-RPC import |
| Medium | Markdown or HTML | Title, tags (up to 5), canonical URL | Medium API (limited) |
| Plain text (posts) or HTML (articles) | None (metadata auto-generated from link) | Manual or scheduled via third-party tool | |
| Email (newsletter) | Email-safe HTML | Subject line, preview text, sender name | Platform API (Mailchimp, ConvertKit, etc.) |
| Static site | Markdown or HTML file | Front matter (title, date, description) | File copy + build command |
| Amazon KDP | EPUB or DOCX | Title, description, keywords, categories, price | Manual upload (no public API) |
Metadata Generation
Metadata should come from your single source file, not from manual entry at publish time. Your conversion script from Stage 6 can extract or generate:
- Title: from the document's H1 or YAML front matter
- Meta description: from a summary field or AI-generated from the first paragraph
- Keywords/tags: from a predefined list or extracted from content
- Slug: generated from the title (lowercase, hyphens, no special characters)
- Publication date: the date the pipeline completes, or a scheduled date
- Canonical URL: your primary platform's URL, set on all cross-posts
The canonical URL matters for SEO. If the same content lives on your website and Medium, the canonical URL tells search engines which version is the original. Set it on every cross-post. If you skip this, you compete with yourself in search results.
The Pre-Publish Checklist
Before hitting publish, run through a final checklist. This is not a quality gate for the content itself (that happened in Stages 4 and 5). This is a technical verification of the publishing setup.
| Check | Why |
|---|---|
| Preview renders correctly | Formatting errors are visible only in preview, not in the editor |
| All links work | Internal and external links must resolve |
| Images load | Broken image paths are common after format conversion |
| Metadata fields populated | Missing titles or descriptions affect SEO and social sharing |
| Canonical URL set on cross-posts | Prevents duplicate content issues |
| Analytics tracking active | You need data to evaluate content performance |
Archiving
Every published piece gets archived: the source Markdown, all generated formats, the research brief, the outline, and the final published URLs. This archive serves three purposes.
First, it is your audit trail. You can trace any published piece back through every pipeline stage to the original research.
Second, it is your reuse library. Research briefs from previous content can feed future content. Outlines become templates. Published pieces become few-shot examples.
Third, it is your recovery mechanism. If a platform goes down or deletes your content, you have the source files to republish anywhere.
The quality gate for Stage 7: content is live on all target platforms, metadata is correct, links and images work, canonical URLs are set, analytics are tracking, and the source files are archived. The pipeline is complete.
Further Reading
- WordPress REST API Handbook, WordPress.org
- Pandoc User's Guide, John MacFarlane
- Building a Scalable Content Pipeline for Global Success, Oban International
Assignment
Map your publishing workflow for each platform you use. For each platform, document:
- Required format
- Metadata fields
- Upload process (manual vs. API)
- What can be automated
Identify at least one step that could be replaced by a script. Build that script (or write a specification for your AI coding assistant to build). Run the pre-publish checklist on your most recent publication. Did it pass all checks?