<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pipeline on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/pipeline/</link><description>Recent content in Pipeline on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/pipeline/index.xml" rel="self" type="application/rss+xml"/><item><title>Solo Multi-Channel Content: How I Built My AI Automation Pipeline LynxPipe</title><link>https://blog.lynxflow.co/en/posts/lynxpipe-ai-content-pipeline-architecture/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/lynxpipe-ai-content-pipeline-architecture/</guid><description>&lt;img src="https://blog.lynxflow.co/images/lynxpipe-ai-content-pipeline-architecture.png" alt="Featured image of post Solo Multi-Channel Content: How I Built My AI Automation Pipeline LynxPipe" /&gt;Running a blog, a Telegram channel, and a WeChat public account all by myself—the real bottleneck isn&amp;rsquo;t running out of ideas, it&amp;rsquo;s keeping up. Every day there&amp;rsquo;s an overwhelming flood of valuable AI news, and manually translating, rewriting, sourcing images, laying out, and distributing it all can eat up half a day before you even start. So I architected it as a pipeline I call LynxPipe: raw inputs go in, polished articles come out, and distribution to the blog, TG, and WeChat h</description></item></channel></rss>