Blog publishing

Long-form ships to your own site, not a hosted subdomain. ReachPill writes SEO-conscious articles with a 16:9 hero image and delivers them into your existing pipeline — as git commits or a webhook.

Topic in, article out

Give it a topic (or let a blog campaign pick one from the arc): ReachPill drafts the article in your voice, grounded in Brand DNA and remembered facts, generates an on-palette hero image, and holds it for review like any other post.

The git publisher

Connect a GitHub repository from Settings → Connections. On publish, the article lands as a markdown file with frontmatter — a clean commit your static site or CMS build picks up like any human-authored post:

content/blog/why-we-killed-the-calendar.md

---
title: Why we killed the content calendar
slug: why-we-killed-the-calendar
seo_description: The calendar was never the asset — the pipeline is.
date: 2026-08-15
---

The calendar was never the asset...

The body is markdown (raw HTML also supported). The hero image is committed alongside and referenced from the frontmatter, so your build needs no ReachPill-specific code.

Webhook alternative

If your CMS isn't git-based, register a webhook instead: on publish, ReachPill POSTs the full article payload (frontmatter fields + body + hero URL) to your endpoint and your side decides where it goes.

This documentation site's own blog is published exactly this way — articles arrive as commits to the site repo and deploy with the site.

Next: Slack →