A game wiki looks simple until the game actually goes live.
Codes expire. Character names change between regions. Guides mix confirmed mechanics with community guesses. Search engines keep indexing pages long after their information becomes stale.
I ran into all of these problems while building SorWiki, a free knowledge base and player-tool site for the live Chinese release of Sea of Remnants. The project uses Astro, but the most important lessons are less about the framework and more about how content, evidence, URLs, and interactive tools fit together.
Here is the architecture that has worked best so far.
1. Model facts separately from pages
