A mobile game launched on October 28, and I wanted a fan wiki that could answer the boring first-hour questions fast: what to claim, whether to reroll, which banner is limited. The result is Mirrors High Wiki, an independent English + Japanese wiki for BLEACH Mirrors High. Here is what actually mattered in the first two weeks.
1. Mark every claim with where it came from
Launch week is full of closed-beta screenshots and recycled rumours. Every fact table on the site has a "Status" column: Official, Community observation, or Unknown here. Pull rates and pity were simply marked unknown instead of guessed. It is less exciting, but it means a reader can trust the rows that are filled in.
2. Write the direct answer first
Each guide opens with a short "direct answer" block before any detail. The first-hour beginner route starts with exactly what to tap and in what order (tutorial, free retry summon, Gifts, team of three) and only then explains why. Search visitors on phones usually leave after that block, and that is fine.
3. Japanese is not a translation pass
The game is Japanese first, so the JA pages use the in-game terms players actually type (リセマラ, ミラハイ) rather than literal translations of my English headings. Keeping locales as separate content files instead of string tables made this much easier to review.
4. Static is enough
The stack is Astro for pages, Markdown content collections for guides, and Pagefind for client-side search built at deploy time. No database, no server. Content checks run in CI (missing dates, broken internal links, untranslated pairs) so a rushed update during a banner change does not ship half done.
5. Dates on everything
Limited banners end at a fixed time, codes expire, and "as of" matters more than prose. Every guide carries an updated date, and time-limited facts are written with both UTC and JST.
If you are building something similar for a game you play, the biggest win is boring: be explicit about what you have not verified yet.
