AnvilWiki ⚒️

带 AI 内容工作流的游戏 wiki 模板——广告收入 100% 归你。
开源、Cloudflare Pages 原生优化、零成本免费部署上线。

The game wiki template with an AI-native content workflow — 100% of your ad revenue.
Open source, natively optimized for Cloudflare Pages, free to deploy.

⚠️ Fork 部署前必读 / Before deploying a fork:仓库里的 wrangler.toml 存在时,它是 Cloudflare Pages env 的唯一真相源,dashboard 的 Environment variables UI 会被完全忽略。fork 后要么跑 pnpm apply-template(自动把 [vars] 重置为你的域名并清空 demo 值),要么手动改 [vars] 或删除该文件。详见 docs/deployment.md。

⚠️ The shipped wrangler.toml, when present, is the sole source of truth for your Cloudflare Pages env — the dashboard's Environment variables UI is ignored. Run pnpm apply-template after forking (it resets [vars] to your domain and clears demo values), or edit/delete the file yourself. See docs/deployment.md for details.

Lighthouse 4×100 — 实测于 anvilwiki.pages.dev（2026-08-12）

🚀 快速链接

📖 中文文档

这是什么？

AnvilWiki 是一个游戏 SEO 内容站模板——用来快速搭建围绕某款游戏(Roblox、Steam 新游等)的攻略内容站,通过 SEO 获取流量,通过广告变现。广告收入 100% 归你:无平台抽成、无收入分成(对比 Fandom 等托管 wiki 的平台分成模式)。

技术栈是 Astro + Cloudflare Pages:纯静态输出、零适配器、免费无限带宽、全球 CDN、零 JS 优先(首屏极快)。

适合谁:想靠游戏内容做副业、会用浏览器但不会编程的人(学习手册就是按这个标准写的),以及想被 AI 工作流加速的内容创作者。

核心特性

• 📚 零基础双手册(站内文档中心):学习手册 11 章 + 开发手册 7 章,中英双语,从选游戏到赚到钱、模板化复制、批量铺内页,再到 SEO 进阶(排名 + AI 引用),每一步都是 SOP + 可复制的 AI 提示词;每章带手册目录树和本页目录
• 🤖 AI 全链路(v2.0 内容经营操作系统):内容技能随仓库分发(.agent/skills/,Agent Skills 开放标准)——对 ZCode / Claude Code / Codex 说「根据这些笔记写篇攻略」,产出直接通过构建质检;PR 门控内容管道(GitHub Actions):关键词清单 → 确定性生成 → 八道质量门禁全绿 → 自动开草稿 PR,AI 永不直推;运营工具包 anvilwiki-ops 1.0(npx 免安装 + MCP):AI 替你拉 GSC/Cloudflare 数据、给优化清单、改完内容走 PR 上线,还能一套工具管 N 个站(多站注册表)并追踪 AI 引用(ChatGPT/Perplexity 来路 + AI Overviews 收录)
• 🧰 模板健康检查 + 批量产页 + 封面产能:pnpm template-audit 一键检查「这个站还能不能干净地复制成下一个游戏的站」;pnpm bulk-new-posts 从关键词清单批量生成内页草稿;pnpm gen-covers 自动生成 og:image 封面(1200×675,中/日文标题自动配 Noto 字体,品牌色取自主题)——跑通一个站后,30 分钟复制下一个,几十个内页连封面批量铺
• 💰 变现三件套:AdSense 广告位(3 个位置,env 驱动,默认关闭)+ 联盟链接组件 + Affiliate 建议位(v2.0:配置驱动的文末推荐卡,默认空不渲染)——无平台抽成
• 🔍 SEO 工程化:sitemap(含 lastmod)/ JSON-LD 全套 / hreflang / Quick Answer 摘要块 / llms.txt(AI 搜索),全部自动生成
• ⚡ 极快:Astro 零 JS 优先,Lighthouse 4×100 开箱即得(开了广告也不掉分)
• 🆓 零成本:Cloudflare Pages 免费无限带宽 + 全球 CDN + SSL,永远没有服务器账单
• 🌍 多语言开箱即用:英文无前缀(SEO 最优),其他语言带前缀,缺失内容自动回退英文(直链永不 404)
• 🎮 wiki 级内容呈现:Boss 数据卡、兑换码一键复制、文章 TOC 滚动高亮、画廊灯箱、Giscus 评论(默认关闭)

5 分钟快速开始

# 1. Fork 本仓库,然后克隆(换成你的 GitHub 用户名)
git clone https://github.com/<你的用户名>/AnvilWiki.git
cd AnvilWiki

# 2. 安装依赖并启动(Node 22+ / pnpm 11)
pnpm install
pnpm dev          # 打开 http://localhost:4321

# 3. 一条问答式命令,把 demo 站换成你的游戏
pnpm apply-template

# 4. 部署:cloudflare.com → Pages → Connect to Git → 选仓库
#    自动识别 Astro:构建命令 pnpm build,输出目录 dist,环境变量 NODE_VERSION=22

完全新手?别从这里开始——先去学习手册第 2 章,它把终端、Node、Git、AI 助手怎么装、每步会看到什么,全部一步步写清了。

用 AI 直接生成内容(无需脚本)

fork 后用 ZCode / Claude Code / Codex / Cursor 打开仓库,直接对话即可产页。Agent 会自动加载仓库里的内容规范,生成后自动跑 pnpm check-content && pnpm build 自检。内置 4 个技能:

完整的提示词库(选品分析、产页、批量产页、翻译、SEO 体检、关键词选题等 18 个模板)在学习手册里,整段复制就能用。

文档导航

首选:站内文档中心 —— 双手册(中英),手册 markdown 源码在 docs/handbook/(fork 后保留,可直接用提示词 SOP)。

仓库内参考文档(查阅式,按需取用):

为什么不用 Fandom / 自建 Next.js?

更完整的选型对比——含 Wiki.js、BookStack、MediaWiki、DokuWiki、Docmost 五个自托管引擎的数据表,以及「什么时候不该选 AnvilWiki」:见完整对比页。

常见问题

• 要花多少钱? 托管 ¥0;唯一必要开销是域名(一年几十块,AdSense 审核需要)。
• 不会编程能做吗? 能。学习手册按「完全零基础」标准写,每步都有「你会看到什么」;所有代码活交给 AI 助手。
• 多久有收入? 黄金窗口是游戏爆发后 2-8 周,头 1-2 周收入为零是正常的——手册第 8 章讲怎么经营预期。
• 模板更新了,我的站会被覆盖吗? 不会。三层分离设计,合并上游时你的游戏配置和文章永远保留(见 docs/staying-up-to-date.md)。

用 AnvilWiki 建了站?欢迎提交 Showcase

真实案例是这个模板最有力的证明(按提交顺序排列):

提 PR 在 src/config/landing.ts 的 COMMUNITY_SITES 追加一条即可——官网(/landing 与 /zh/landing)的「Built with AnvilWiki」区块会自动展示。

交流群 / 技术栈

微信扫码添加主理人好友,拉你进群交流讨论(部署问题、功能建议、游戏内容站经验都欢迎;项目官网右下角也有同款悬浮扫码按钮):

技术栈:Astro 5(静态输出)+ Tailwind CSS 3 + MDX 4 + astro-icon/lucide + Content Layer API(Zod)+ Pagefind 搜索 + pnpm 11 / Node 22。

📖 English Documentation

Start here: the Learning Manual — 11 chapters, written for complete beginners, every step a SOP with copy-paste AI prompts. The Development Manual (7 chapters) covers deep customization and AI-driven ops. Both bilingual, with a 10-job whole-picture checklist at the docs hub.

What is this?

AnvilWiki is an open-source game wiki site template: build a content site around a game (Roblox, Steam new releases…), pull traffic via SEO, monetize with ads — 100% of the ad revenue is yours. Built on Astro + Cloudflare Pages: pure static, zero adapters, free unlimited bandwidth, Lighthouse 4×100 out of the box.

Quick Start (5 min)

# 1. Fork this repo, then clone (replace with YOUR username)
git clone https://github.com/<your-username>/AnvilWiki.git
cd AnvilWiki

# 2. Install & run (Node 22+ / pnpm 11)
pnpm install
pnpm dev          # visit http://localhost:4321

# 3. One guided command swaps the demo for your game
pnpm apply-template

# 4. Deploy: cloudflare.com → Pages → Connect to Git
#    Astro auto-detected: build `pnpm build`, output `dist`, env NODE_VERSION=22

Complete beginner? Start from Chapter 2 of the Learning Manual instead — it walks you through installing every tool, with "what you'll see" on each step.

Key Features

• 📚 Two beginner manuals (Learning 11 chapters / Development 7, bilingual) with 18 copy-paste AI prompts
• 🤖 AI-native workflow (v2.0 content OS): agent skills ship inside the repo — say "write a boss guide from these notes", get a build-check-passing page; a PR-gated content pipeline (GitHub Actions) turns a keyword list into draft PRs — deterministic generator → all 8 quality gates → draft PR, AI never pushes to main; the anvilwiki-ops 1.0 toolkit (npx + MCP) has your AI pull GSC/Cloudflare data, rank SEO actions, ship content through validated PRs, run N sites from one registry, and track AI referrals (ChatGPT/Perplexity traffic + AI Overviews pages)
• 🧰 Template health check + batch pages + cover generation: pnpm template-audit scores how cleanly this repo can be copied into your next game's site; pnpm bulk-new-posts scaffolds dozens of draft inner pages from a keyword list; pnpm gen-covers auto-generates og:image covers (1200×675, CJK titles auto-subset Noto fonts, brand color from your theme) — once your first site works, the next one takes ~30 minutes, covers included
• 💰 Monetization trio: AdSense slots (3 positions, env-gated, off by default), affiliate link component, and the Affiliate suggestion slot (v2.0: config-driven end-of-article cards, empty by default)
• 🔍 SEO engineering: sitemap (lastmod) / JSON-LD suite / hreflang / Quick Answer blocks / llms.txt — all automatic
• ⚡ Fast: zero-JS-first Astro, Lighthouse 4×100 out of the box
• 🆓 Free forever: Cloudflare Pages, unlimited bandwidth, global CDN, SSL
• 🌍 i18n built in: English at root, prefixed locales, English fallback so URLs never 404
• 🎮 Wiki-grade presentation: boss stat cards, tap-to-copy codes, TOC scroll-spy, gallery lightbox, Giscus comments (off by default)

Generate content by talking to your AI (no scripts needed)

After forking, open the repo in ZCode / Claude Code / Codex / Cursor and just talk. Agents auto-load the content spec shipped in the repo and self-check with pnpm check-content && pnpm build after generating. Four skills are built in:

The full prompt library (game selection, page generation, batch production, translation, SEO audits, keyword research — 18 templates) lives in the Learning Manual; copy-paste ready.

Repository reference docs: game-selection · apply-template · content-format · deployment · staying-up-to-date · development · full index

Why not Fandom / a hand-rolled Next.js site?

For the full decision guide — a data table of self-hosted wiki engines (Wiki.js, BookStack, MediaWiki, DokuWiki, Docmost) plus an honest "when NOT to pick AnvilWiki" section — see the complete comparison.

FAQ

• What does it cost? Hosting $0; the only required spend is a domain (a few dollars a year — AdSense approval needs one).
• Can I do this without coding? Yes. The Learning Manual is written for complete beginners with "what you'll see" on every step; all coding goes to your AI assistant.
• How fast will revenue come? The golden window is 2–8 weeks after a game breaks out; zero income in the first 1–2 weeks is normal — Chapter 8 covers managing expectations.
• Will upstream updates overwrite my site? No. The three-layer separation keeps your game config and articles intact when merging upstream (see docs/staying-up-to-date.md).

Community Showcase

Real sites built with AnvilWiki (in submission order):

Built a site? Open a PR appending an entry to COMMUNITY_SITES in src/config/landing.ts — it will show up in the "Built with AnvilWiki" section on the landing page.

Community & License

MIT License — see LICENSE.

Questions, ideas, or want to chat about game content sites? Scan the WeChat QR code to join the discussion group (the project landing page has the same floating QR button in the bottom-right corner):

Tech stack: Astro 5 (static output) + Tailwind CSS 3 + MDX 4 + astro-icon/lucide + Content Layer API (Zod) + Pagefind search + pnpm 11 / Node 22.

Design Notes

• Three-layer separation (code / config / content) is the core architectural decision — it's what makes forks mergeable upstream. See docs/PRD.md.
• Optional features (ads, comments, analytics) are env-gated and off by default — a fresh fork ships zero-JS and zero-cookie, preserving the Lighthouse 4×100 contract.
• The demo game "Anvil Quest" is fictional by design: forks replace it wholesale via pnpm apply-template, and the project landing + docs center are removed for forks automatically (the handbook markdown stays as repo docs).