Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

Building a Multilingual Blog Pipeline That Auto-Posts to Zenn, dev.to, and velog

说明与用途

一个自动化多语言发布管道,从单个 GitHub 仓库将文章推送到 Zenn、dev.to 和 velog,使用 Zenn 的 GitHub 集成、dev.to 的 REST API 和 velog 的内部 GraphQL API。

问题

Manually copy‑pasting articles into three platforms (Zenn, dev.to, velog) is impractical for a Korean engineer in Japan.

结果

Automated multilingual publishing pipeline reduces manual effort, ensures consistent deployment across platforms, and maintains private drafts in a private repo.

工作流

  • Set up repository layout with directories for each platform and a material.md backlog
  • Configure Zenn GitHub integration from Zenn side and push an empty commit to trigger deployment
  • Create GitHub Actions workflow to post dev.to files via official REST API, embedding front matter in body_markdown and setting canonical_url
  • Create GitHub Actions workflow to post velog files via internal GraphQL API, passing an empty object for meta and handling access/refresh tokens
  • Configure workflows to process only newly added files using git diff --name-only --diff-filter=A
  • Store API keys and cookies in GitHub Actions Repository Secrets and avoid logging them

证据

If you install the Zenn Connect app from the GitHub Marketplace side first, the integration never shows up in Zenn's dashboard

来源

dev.to was the pleasant one, since there's an official API

来源

velog was the hard one. There is no official API, so I ended up calling the internal GraphQL endpoint used by the web frontend

来源

  • 记录日期: 2026-10-08T12:41:01.240Z