𝗛𝗼𝘄 𝗧𝗼 𝗠𝗮𝗶𝗻𝘁𝗮𝗶𝗻 𝗔 𝗦𝗺𝗮𝗹𝗹 𝗚𝗮𝗺𝗲 𝗥𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲

𝗛𝗼𝘄 𝗧𝗼 𝗠𝗮𝗶𝗻𝘁𝗮𝗶𝗻 𝗔 𝗦𝗺𝗮𝗹𝗹 𝗚𝗮𝗺𝗲 𝗥𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗣𝗮𝗴𝗲

A reference page should not look bigger than the facts it holds.

A short page with a clear scope beats a large page full of guesses.

I maintain a fan reference page. I use a specific process to keep it accurate and easy to update.

I split my notes into three groups before I publish them:

• Confirmed mechanics: These go in the main table.
• Change-prone observations: These need a date or a version note.
• Open questions: These stay out of the main answers until I find proof.

This method makes updates fast. When a player reports a change, I compare it to my current notes. I do not rewrite the whole page. This prevents the wiki problem where old, wrong info stays visible for years.

Use this checklist before you update a page:

• Can you check this claim from two sources or direct play?
• Does the page show the limits of your knowledge?
• Do you include dates or version notes for changing info?
• Is the answer easy to read on a phone?
• Can a new reader understand the next step without reading everything?

Small projects do not need complex tools. They need careful words, repeatable checks, and the discipline to leave uncertain details out until you verify them.

Source: https://dev.to/xian_x_9469bb3e1b9a2f6ed0/notes-from-maintaining-a-small-game-reference-page-5edp

Reference page: https://growagardens2.com/