Content production pipeline · 2025
Scheduled editorial production
Shipped
- Role
- Independent engineer
- Stack
- Python, n8n, SEO
- Status
- Shipped
Problem
Several brand voices were publishing on a calendar that only existed in someone's head. Drafts moved by chat. SEO checks happened, or did not, depending on who was awake.
Constraint
The client keeps the voices. The pipeline keeps the queue. I am not a writing mill and this page is not a claim about word count.
Architecture
- Intake
- Voice routing
- SEO checks
- Ready
Decisions
Intake, route, check, ready
A piece has states. "Ready" is a state after SEO checks, not a feeling in a thread.
n8n plus Python
Scheduling and hand-offs in n8n. Checks in Python. Neither is a chatbot with a calendar plugin.
Do not read this as a content-writing offer. Read it as a production system for people who already have voices and a schedule that keeps slipping.
Outcome
Shipped. The calendar is the pipeline. Client name stays off this page.
What was handed over
- Queue states and who may move them
- Where the checks run
- How a brand voice is represented — the client still owns the voice