// the find
YYsuni/2025-blog-public
开源blog，让你不写代码就开始写 blog，管理 blog 内容。无需服务器，无需费用。
A Next.js blog template that uses GitHub as its CMS — you fork the repo, deploy to Vercel, create a GitHub App for write access, and then edit your blog through the deployed site itself. No database, no separate admin panel, no hosting cost. Aimed squarely at non-developers who want a personal blog without learning any infrastructure.
- The zero-cost, zero-server model actually works: GitHub stores the content as flat files, Vercel serves the static output, and the GitHub App handles authenticated writes. For a personal blog at low traffic this is genuinely sufficient.
- 847 forks against 1600 stars is a healthy ratio — people are actually deploying it, not just starring it. The QQ/WeChat community support fills the gap where documentation falls short.
- Editing happens in-browser on the deployed site itself using the private key stored in Vercel env vars. It's a clever inversion: the blog is its own CMS without a separate admin surface to host.
- The TypeScript + Next.js stack is boring in the right way — any frontend developer picking this up will understand it immediately, and there's no proprietary framework lock-in beyond Vercel.
- Every content change triggers a full Vercel build and deploy, which takes ~60 seconds by the README's own admission. That's tolerable for weekly posts, but iterating on a draft or fixing a typo means waiting for a pipeline each time.
- All blog content lives under public/blogs/ as markdown and images committed directly to the repo. As the blog grows, the repo balloons, cold build times increase, and git clone gets slow. There's no strategy for this — the design doesn't scale past a few dozen posts with heavy images.
- The setup guide (create GitHub App, manage private keys, configure Vercel env vars, trigger a redeploy) is genuinely complicated for the non-developer audience the README is pitching to. The author acknowledges this by pointing to community chat groups as the support channel, which is an honest admission that the documentation isn't enough on its own.
- The entire README is in Chinese with no English translation, which limits adoption and makes it harder for the international open-source community to contribute or report issues.