My Full Make.com Blueprint For Automating a Sheets → OpenAI → Ghost Content Pipeline
→
I wired my entire content pipeline into Make.com so a single row in Google Sheets turns into a published Ghost post. Here is the exact scenario, module by module.
Letting AI refactor one legacy stylesheet
→
I pointed an AI model at a 1,200-line legacy Sass file and asked it to refactor everything to Tailwind. The useful part was mechanical syntax cleanup. The risky part was everything that depended on design, layout, and accessibility intent.
A tiny script that adds my internal links
→
A 40-line Python script adds internal links to my Ghost drafts via a shell alias. It is crude, fast, and only saves minutes, which is exactly why it works.
Three things I delete from almost every AI draft
→
When I use AI for first drafts, I spend most of my editing time deleting: fake origin stories, forced AI angles, and tidy morals the model invented for me.
The Hour I Lost to a Plausible AI Debugging Answer
→
A confident AI diagnosis of a React Native hydration issue sent me refactoring the wrong layer for 45 minutes. The real bug was a string "null" in the API.
What My Automated Archive Exposed About My Writing
→
Reading a batch of AI-written posts in my Ghost archive made the patterns obvious: recycled transitions, invented habits, generic intros, fake closure, and why even a few real notes change the result.