AnvilWiki template update log (v2.32.0): new "wiki page templates" showcase page (/landing/templates, 中文版 /zh/landing/templates) — every page type the template produces (boss guide, codes page, tier list, beginner guide, item pages, docs center), each card linked to a real page on the live demo, closing with a fork CTA. Catches the "wiki template / wiki page template" long tail (~1k+ monthly searches, SimilarWeb 2026-08). Landing header/nav gains a Templates entry; the new copy ships in its own config file, the landing-en/zh modules are untouched. Forks: merge upstream and pnpm install as usual. This bar tracks template releases — details & full changelog on GitHub Releases.
AnvilWiki
Powered by Pagefind
中文
Lesson 2 · Know the Business Updated Sep 2, 2026

The Full Map: Six Stops to Your First Site

The six-stop subway map: pick and validate, stand it up, content, launch and index, monetize, operate — each with lessons, time cost, and what you carry away.

Your 30-day subway map

From zero to an earning site is six stops. See the whole route before boarding:

Stop Lessons Time You carry away
① Pick & validate 03-08 2 days A decided game + the day-one 10-page list
② Stand it up 09-12 1 day A working site that is yours
③ Content engine 13-17 Week one First 10-15 pages passing QA
④ Launch & index 18-21 3 days Live worldwide + Google indexing
⑤ Monetize 22-24 After qualifying Ad slots live + payout channel ready
⑥ Operate 25-29 30 min weekly A stable update-and-rank rhythm

Never skip a stop. Each stop’s output is the next stop’s raw material: without ①’s query list, ③’s pages target things nobody searches; without ③’s 15 pages, ⑤’s ad application fails review. Every day a skip saves you, you repay double later.

How to brief AI (three rules, used all through this manual)

Every hands-on step in this manual ships a copy-paste AI prompt. Before using them, memorize three rules:

  1. Feed material; never let it guess. Every <placeholder> in a prompt gets replaced with real material: real Trends data, real results-page listings. AI-invented game facts (codes, stats) destroy site trust — with material supplied, there is nothing to invent.
  2. Ask for tables, not prose. Tell AI to “output a table: priority / page / target query / material needed” — tables paste into your worksheet; prose does not.
  3. Make it ask you back. End prompts with “list what’s missing and ask me” — AI then puts the gaps on the table instead of silently filling them with fake data.

Uniform usage: copy the whole block → replace every <placeholder> → send. Planning prompts let AI advise but never touch files; page-production prompts are the ones that write into your repo.

Three classic mistakes (made for you in advance)

  • Skipping stops: jumping straight to “turn on ads”, then discovering the application needs 15-20 pages. Every stop’s gate is written on the road.
  • Reading without doing: every lesson ends with an acceptance checklist — no output, no moving on. This is a manual, not a novel.
  • Grinding when stuck: every lesson carries “three classic mistakes”; still stuck, throw your screenshot and question straight at AI — it is your teaching assistant on call.

✅ Acceptance (all must hold)

  • You can name the six stops in order
  • Every prompt you send has real material in its placeholders
  • ☐ You wrote down the goal: day 30 — one indexed site with 10 pages

Next lesson

First stop, and the most valuable skill in the whole business: finding queries. Next lesson: 20 minutes a day to fill your candidate pool past 10. Go to Lesson 3 · Where to Find Candidates

Advertisement