Aug 5, 2026
The Architecture Behind My Blog Workflow
A visual breakdown of how thoughts go from my head to the blog — and the automation that holds it together.
In my last post, I explained the stack — Hermes, Telegram, Directus, Astro, Obsidian. The pieces. But the pieces alone don't tell you much. What matters is how they connect.
So I drew it.
The flow, in one breath
I have a thought. I send it to Telegram — quick notes go to a topics thread, longer ideas to general. Hermes picks it up, writes a markdown file to my Obsidian vault, and publishes to Directus via its API. Short notes go live instantly. Longer posts save as drafts so I can review.
The vault syncs to my phone and laptop through Syncthing — end-to-end encrypted, edits flow back. Meanwhile, Directus feeds Astro, which builds the blog you're reading right now.
What's happening in the background
Four cron jobs keep the system alive:
- inbox-watcher — every 30 minutes, checks for unpublished notes and pushes them live.
- nudge-checker — three times a day, reminds me if I've been quiet for too long.
- weekly-review — Sundays at 6pm, clusters my notes and suggests post ideas.
- monthly-planner — first of every month, sets targets and reviews what happened.
What's next
The pipeline works. The next step is extending it — drafting tweets from vault sparks, prepping weekly LinkedIn content from note clusters, and getting suggestions for what to write next based on what I've been thinking about.
The goal was never to build a complex system. It was to remove every excuse for not capturing what I learn. This diagram is what that looks like when you lay it all out.