So Google Docs - it’s not bad by any means. In fact it’s pretty good, all things considered, in multi platform availability and syncing. But also, it gets unorganized fast if you don’t use the Drive app to organise it into folders, as the main GDocs app is entirely reverse chronological in display. So I’d resorted to putting everything in a single Google Doc, which brings its own set of problems. It also force-converts Markdown syntax natively now. Which is good, usually, until I have to copy-paste it somewhere and it gets flattened. Which brings us to Notion.

Notion is a… note taking app, if I simplify it a lot. It has various blocks and features that make life easier for some use cases. In this case the ones that made my life easier is the database feature and the webhooks feature. A database contains… many individual pages with various attributes, and webhooks can fire when I change a state. You may see where this is going.

I made a page in Notion, with a database inside, that’ll now contain my article drafts. When I’m ready, and an article doesn’t need access to my local machine’s logs, notes or my Tailnet, I can flip a flag to “autopublish” to fire off a webhook. Said webhook goes to a Cloudflare Worker, fetching the Notion article’s content as markdown, putting it in my repo, and calling Jules (and maybe other agents in the future) to format it to Markdown / add any agent sections / add citations and verify facts.

Notion also has other properties I can add to the database, which I may end up using later, and it also supports rich media like images or file uploads - all of which isn’t processed by the Worker for now. This may change sometime, but for now, just the automated pushing workflow is a big QoL improvement! It’s also free (both the CF Worker and Jules), which is always a good thing.