<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ai-Content on René Zander | AI Automation Consultant</title><link>https://renezander.com/tags/ai-content/</link><description>Recent content in Ai-Content on René Zander | AI Automation Consultant</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 05 Apr 2026 14:00:00 +0200</lastBuildDate><atom:link href="https://renezander.com/tags/ai-content/index.xml" rel="self" type="application/rss+xml"/><item><title>Automate Content Publishing with Make.com: One Article to Five Platforms</title><link>https://renezander.com/blog/automate-content-publishing-make/</link><pubDate>Sun, 05 Apr 2026 14:00:00 +0200</pubDate><guid>https://renezander.com/blog/automate-content-publishing-make/</guid><description>&lt;p>I publish most articles to five places: my own site, LinkedIn, Dev.to, Hashnode, and X. Doing that by hand costs 30 to 45 minutes per piece. Copy the body, reformat for each platform, upload a cover image, adjust tags, set canonical URLs, schedule. Multiply by every article and the cost is hours per week of editor time that belongs elsewhere.&lt;/p>
&lt;p>This is the tutorial for the Make.com scenario that replaced that routine. One Notion row flips to &lt;code>approved&lt;/code>, one scenario fires, five platforms publish with proper metadata and canonical links pointing home. The setup takes an afternoon. It pays for itself in a week.&lt;/p></description></item><item><title>Teedian: AI Content Operations Engine for Make.com, n8n, Notion</title><link>https://renezander.com/guides/teedian-ai-content-engine/</link><pubDate>Thu, 02 Apr 2026 14:00:00 +0200</pubDate><guid>https://renezander.com/guides/teedian-ai-content-engine/</guid><description>&lt;p>Editorial teams spend roughly 60% of their time on operations. Status updates. Briefing docs. Approval pings. Cross-posting the same article to five platforms. Pulling last week&amp;rsquo;s numbers into a spreadsheet so someone can decide what to write next. The other 40% is the actual work: voice, story, editing, judgment.&lt;/p>
&lt;p>Teedian is the AI content operations engine that flips those numbers. It orchestrates the content pipeline (briefings, drafting, approval, cross-posting, performance tracking) using Claude as the text engine inside Make.com and n8n workflows your team already runs. No new monolithic SaaS. No platform lock-in. The ops layer runs in automation tools you control, and humans stay on voice.&lt;/p></description></item></channel></rss>