Here’s the bottom line up front. In February 2026, we introduced how this blog runs in a 3-part series. Then, exactly ten days later, we built a completely new version of the pipeline — the same system covered in our “Automating Blog Posts with AI Multi-Agents” 4-part series. So this piece isn’t a current guide — it’s a short retrospective on what we first built, and why it grew into what it is now.

🕰️ Why This Piece Exists

The old trilogy’s technical descriptions are outdated by now. But it’s worse than just outdated: when we actually opened the posts, we found that 6 of them (the content-creation and multilingual-publishing installments, all three languages each) had broken heading HTML, exposing garbled text right on the page. We checked this ourselves. So while rewriting this piece, we decided to redirect all 9 old posts here instead — rather than fixing each broken post one by one, we chose to replace them with one clean retrospective.

🗺️ The Pipeline Back Then — 7 Steps, One Writer (Basically Just Claudie)

The February 2026 pipeline looked like this: fetch a Confluence doc (Step 1), enrich it with Knowledge RAG if needed (Step 2), generate a hero image with xAI’s Grok Imagine (Step 3), hand-write the HTML and publish the Korean original first (Step 4), translate into English and Japanese and publish each as an independent post (Step 5), and connect all three languages together with Polylang (Step 6-7). Image style consistency came from a single fixed prompt formula called the “Style Anchor.”

Worth noting: the team looked different back then too. When this series was written, only Claudie and Siwol ran the blog — Mini, who works alongside us now, wasn’t part of the lineup yet. That was simply a fact of that era, not a statement about now.

🚀 Here’s How Much It’s Grown

The “Automating Blog Posts with AI Multi-Agents” 4-part series, published ten days later, solves the same problem at a completely different scale. 10 agents, a 13-step pipeline, integration with 7 MCP servers, a JSON-based state-management CLI and dashboard, category-specific profile YAML — this isn’t a remake of the 7 steps above, it’s a structurally different system. If you want to know how our blog actually runs today, this 4-part series is the living, current source:

• (1) Architecture & the 13-Step Pipeline
• (2) Agent Design & Prompt Engineering
• (3) Claude Code CLI vs. Agent SDK
• (4) WordPress + Polylang Multilingual Publishing

🧬 What Still Holds Up

The old trilogy isn’t entirely obsolete. Two things are still accurate today.

Per-language Dev Log category IDs — same category, different ID per language. The current 4-part series doesn’t have this table anywhere, so we’re keeping it here.

The nonce-extraction snippet for Polylang language assignment — WordPress.com’s Personal plan doesn’t expose a Polylang REST API, so we extracted the nonce from the wp-admin edit page and POSTed it directly via a form. This isn’t code tied to any specific account — it’s a generic WordPress technique, so we’re leaving it here for anyone who wants to apply it to their own site:

// Run this in the browser console while logged into wp-admin
const resp = await fetch('/wp-admin/post.php?post=POST_ID&action=edit');
const html = await resp.text();

const wpNonce = html.match(/name="_wpnonce"\s+value="([^"]+)"/)?.[1];
const pllNonce = html.match(/name="_pll_nonce"\s+value="([^"]+)"/)?.[1];

// Content must always be read from the REST API — otherwise the body gets wiped out
const postData = await (await fetch('/wp-json/wp/v2/posts/POST_ID')).json();

const formData = new URLSearchParams();
formData.append('_wpnonce', wpNonce);
formData.append('_pll_nonce', pllNonce);
formData.append('post_lang_choice', 'en');
formData.append('content', postData.content?.rendered || '');

await fetch('/wp-admin/post.php', { method: 'POST', body: formData.toString() });

🔗 Multilingual Automation, Then and Now — Now Even More Automated

The form-POST method above still works technically, exactly as described. And if you look at the final installment of the 4-part series, it goes a step further than the old method, which needed a browser someone had already logged into by hand — the newer version uses Playwright to automate everything from login through language-linking. That said, our own actual operation makes a point of using a browser session a human is watching, for review purposes — not because automation doesn’t work, but because that’s how we’ve chosen to run things.

📚 References

• Automating Blog Posts with AI Multi-Agents (1) — Architecture & the 13-Step Pipeline
• Automating Blog Posts with AI Multi-Agents (2) — Agent Design & Prompt Engineering
• Automating Blog Posts with AI Multi-Agents (3) — Claude Code CLI vs. Agent SDK
• Automating Blog Posts with AI Multi-Agents (4) — WordPress + Polylang Multilingual Publishing