Scrocle

Content production pipeline · 2025

A publishing queue for more than one brand voice

ShippedIndependent engineer

Several brand voices published on a calendar held in one person's memory. Drafts moved by chat, and quality checks were inconsistent.

The constraint

The client keeps the voices. The pipeline keeps the queue. I do not produce the writing; the work is the queue and the checks.

Built with

  • Python
  • n8n
  • SEO

How it works

Intake into a queue. Draft routing by brand voice. SEO checks. Ready is a gate the pipeline enforces.

  1. Intake
  2. Voice routing
  3. SEO checks
  4. Ready
Intake into a queue. Draft routing by brand voice. SEO checks. Ready is a gate the pipeline enforces.

The calls that shaped it

Each decision with the pressure that forced it and the price it keeps costing.

  1. Intake, route, check, ready

    "Ready" is a state produced by completed SEO checks, not a judgment call in a group chat.

  2. n8n plus Python

    Scheduling and hand-offs in n8n. Checks in Python. Neither is a chatbot with a calendar plugin.

This is for teams that already have brand voices and a publishing calendar that keeps slipping. The writing stays with the authors; the queue and the checks are the work.

Where it stands

Shipped. Publishing is now driven by the queue, and the quality checks run on every piece.

What was handed over

  1. Queue states and who may move them
  2. Where the checks run
  3. How a brand voice is represented. The client still owns the voice.
Next project Sales email to ShipStation Parse a sales email, hold it or build a label