Published: 03/02/2026
Building a technical audience is a marathon, but the “grind” of manually cross-posting content across platforms is a sprint that nobody wants to run every week.
As a senior engineer, I want to spend my time architecting systems, not fighting web editors. Today, I finished building the Sovereign Publisher— a “Software 3.0” pipeline that handles my distribution while I sleep.
The Problem: The Content Context Switch
When you finish a deep technical post, the last thing you want to do is:
- Format it for Jekyll.
- Convert it to RTF for Substack.
- Write a punchy thread for X.
- Draft a professional update for LinkedIn.
- Remember to hit “Publish” at the optimal time.
It’s high-friction. And friction is the enemy of consistency.
The Solution: A Buffered Local-to-Cloud Pipeline
I’ve moved my entire workflow into a single command. I write in local Markdown, and my agentic pipeline handles the rest.
1. The Local Queue (The Buffer)
My publisher agent doesn’t ship to production immediately. It ships to a _queue/ directory in my blog repo and sets the metadata date to Today + 3 Days. This gives me a “cool-off” period to catch typos or rethink a hot take before the world sees it.
2. The “Cloud Cron” (GitHub Actions)
I’m using a native GitHub Action on my blog repo that wakes up every morning at 7:00 AM.
- It checks the
_queue/. - If a post’s date has arrived, it moves it to
_posts/. - It commits the change, triggering the site build.
- The Magic: It then hits the X and LinkedIn APIs to announce the post automatically using GitHub Secrets.
Why “Sovereign”?
In the Software 3.0 era, your “Source of Truth” should be local. My notes stay in my Git repo on my M4. The cloud is just a projection of my local environment.
By using GitHub Actions as a scheduler, I’ve eliminated the need for a dedicated server or a $20/month Buffer subscription. It’s slick, it’s vanilla, and it’s completely under my control.
Time is short. Stop manually posting. Start architecting.