Notes from maintaining a small game reference page

Short summary

Reference documentation improves by separating verified facts from provisional observations and open questions. Use a repeatable checklist: verify claims across sources, explicitly mark unknowns, date version-specific changes, optimize for mobile, ensure clear next steps. Careful structure beats breadth and prevents wiki decay.

• •Separate confirmed mechanics, change-prone observations, and open questions before publishing
• •Apply a verification checklist: multi-source claims, explicit scope limits, version dates, mobile scannability, clear reader next-steps
• •Structured documentation prevents outdated information from persisting unchallenged

Generated with AI, which can make mistakes.