Content Pipeline Automation

Building an audience while working full-time runs into a coordination problem: ideas surface during project work and disappear if not captured at the moment they happen; manual posting cadence drifts; engagement data doesn't loop back to shape what gets written next. The bottleneck isn't writing quality — it's capture, sequencing, and feedback. A content 'system' only works if those three are automated together.

Analyzed posting patterns and engagement data on prior posts. Found that technical 'learning journey' content outperformed announcements and opinion takes by a wide margin. Tracked where ideas were getting lost — most surfaced during commits, debugging sessions, or post-incident reflection, none of which had a capture surface. Mapped the workflow end-to-end: idea capture → spec/outline → draft → approval → schedule → publish → analytics → loop back to ideas.

Built an end-to-end pipeline anchored on a central content hub that holds ideas, specs, and historical posts. Content queue (JSON) syncs to Google Calendar so the cadence is visible and reviewable. Slack approval flow for pre-publish review. Post-commit hooks capture content-worthy learnings automatically from session journals and commits — closing the 'ideas disappear' loop at the source. n8n orchestrates scheduling reminders and post-publish analytics.

• Markdown hub + JSON queue over a database-backed CMS — keeps content under version control alongside the code that generated it; no separate auth surface, no SaaS dependency
• Slack approval flow over direct-publish — deliberate review gate between draft and live without slowing cadence; mirrors the same review pattern I'd want for any external-facing artifact
• Post-commit hook auto-capture over manual idea tracking — the failure mode of any content pipeline is 'I forgot to write down the insight'; capturing from commits closes that loop at the source
• Milestone-driven cadence over weekly calendar — posts go live when something real shipped, not because it's Wednesday; quality of post depends on quality of underlying work

• 18,272 impressions on latest technical post
• Central content hub holds ideas, specs, and post history under version control with the code that generated them
• Quarterly post calendar scheduled and synced to Google Calendar with Slack approval gating
• Post-commit hooks capture content-worthy learnings automatically from session journals
• n8n orchestrates scheduling reminders and post-publish analytics; engagement data loops back to shape what gets written next