PROFESSIONAL WORK · Publishing & platforms
Content operations & handoff
Took over existing blog, newsletter, and video workflows, restructured the queue and templates, and made them easier to run and hand off.
Took over & extendedLive workflows · ongoing refinementDocumented October 2026 review
My contribution
Took ownership of existing automation, improved queue structure and templates, and moved operation toward managed service accounts and clear review steps.
Tools
Make · Google Sheets · Gemini · WordPress · Mailchimp · HeyGen
How it works
- InputTopic & brief queueStructured Google Sheets queue · Improved
- AIGenerate blog fieldsGemini, orchestrated in Make
- CheckOutput contractTitle, content, metadata; duplicate-topic and audience checks · Improved
- PersonReviewDrafts and video output go to a person
- OutputPublishWordPress; inherited video path via HeyGen
- StepNewsletter draftFour recent articles → Mailchimp draft; a reviewer sends it
Decisions that mattered
Own the operating process
Account ownership, access handoff, and queue refill are part of the system, alongside the generation steps.
Standardize the output contract
Title, content, and metadata fields give downstream publishing steps predictable inputs. Topic-duplication checks and audience constraints reduce drift.
Newsletter preparation is not sending
The newsletter workflow gathers four recent articles, generates subject/title content, creates a Mailchimp draft, and notifies a reviewer. Final sending remains human-controlled.
Build on what was there
Before I took it over, the video path already connected blog content, scripts, video generation, approval, and publishing. My part was the transition and the improvements around it.
Results
The records include an April content-system handoff, a June 1 newsletter run, and later blog-queue and output-contract updates.
Scope & limits
These are several related workflows, each with its own approval path.