Content

The content loop writes one long-form article per run, commits it directly to your connected website repo as a new blog post, and opens a pull request. You review the actual diff on GitHub and merge — there's no separate "publish" step. Articles are written for GEO (Generative Engine Optimization): structured to be quoted verbatim by LLMs like ChatGPT, Claude, Perplexity, and Gemini when someone asks about the topic.

Prerequisites

• GitHub connected for the product. If it isn't, the loop skips and tells you to connect it in Integrations.

• A blog directory in the connected repo. The loop looks for one in this order (first match wins):

  Directory	Common frameworks
  content/blog/	Next.js + Contentlayer / Velite, Astro, Hugo
  content/posts/	Astro Starlight, Eleventy
  src/content/blog/	Astro
  src/content/posts/	Astro
  app/blog/	Next.js app-router blog
  posts/	Hexo, raw Markdown sites
  articles/	Custom convention

  If none exists, the loop skips with a comment explaining what it looked for, so you can set one up.

Run it

Ask the dispatcher, optionally with a topic or angle:

write a blog post about migrating from spreadsheets to our app

With no topic, it scouts trending, relevant topics and picks the highest-value angle itself. It also runs on its own roughly every 7 days.

What happens

1. Resolves your repo — using the repository you selected in Integrations if you've picked one.
2. Finds the blog directory and reads existing posts (and your Brand.md voice guide) so the new piece matches your conventions and tone.
3. Drafts the article to GEO structure and commits it as a new post on a branch.
4. Opens a pull request — that PR is the deliverable.

What you get

A pull request adding one new article to your blog directory, matching the repo's existing frontmatter and file conventions. Draft-only: merging the PR is what publishes it. Review the prose and structure on GitHub like any other change.

Notes & limits

• One article per run — depth over volume.
• If the repo has no blog wired up, the loop won't scaffold one — it skips and tells you what's missing.
• Uses your selected repo verbatim when set; otherwise it prefers the website/marketing repo (one whose name contains site, web, marketing, or docs) over the app backend.
• Tune the cadence from Cadence.