As a Solution Engineer, my brain is hardwired to look at a repetitive task and think: “There has to be a pipeline for this.” For weeks, I’d write a deep-dive technical post on my Hugo blog, and then… I’d just sit there. The thought of copy-pasting, re-formatting, and uploading images to LinkedIn felt like a chore that belonged in 2010.
So, I decided to give my Hugo (Blowfish theme) site a superpower.
The Tech Stack:
🚀 GitHub Actions for the heavy lifting.
📜 PowerShell (pwsh) to handle the LinkedIn API versioning handshake.
🔑 OpenID Connect to secure my identity via the sub claim.
🤖 Decap CMS as the launchpad.
The Result?
Now, when I hit “Publish” in my CMS, a GitHub Action triggers. It parses my frontmatter, grabs my feature image, and fires off a formatted post directly to my LinkedIn feed.
No more manual uploads. No more “I’ll do it later.” Just code doing what it does best: saving me time for the things that actually matter (like building more AI agents). 🛠️
The Big Lesson:
Don’t let the “PowerShell curl trap” or API versioning headers stop you. The bridge between your content and your network is just a few lines of YAML away.
CTA:
What’s the one repetitive “social” task you wish you could just script away? Let’s talk automation in the comments! 👇