Editorial Guidelines

1. The answer is the first sentence

Every page's meta description is written to be quotable in a search result: the complete answer, under 155 characters, no ellipsis, no restating the title. The body then repeats that answer in a highlighted card before any background. If a page needs five paragraphs before the fix, it's written wrong.

2. Every step ends with a verification

Steps say what you should see when they worked. If a step can't be verified by the player, it isn't a step — it's a guess. This is also how we catch our own staleness: a verification that no longer matches reality is a page that needs re-checking.

3. Questions are recorded, not invented

Question-aggregation pages only contain questions players actually asked — from search "People Also Ask" boxes, GitHub issues, or forum threads, logged with their source. We don't generate plausible-sounding questions to fill a page, and a hub with fewer than 15 real questions gets no aggregation page until the questions exist.

4. No minimum word count

Some fixes are two sentences. Padding them to hit a word count wastes the reader's time and reads as filler. Short answers either stand alone or get merged into an aggregation page — the standard is information completeness, not length.

5. Sourcing tiers

Official first-party pages are linked whenever they exist and are alive. Official self-hosted repositories are linked with a note. Third-party download sites, mirrors, and domain-squatters are never linked — including when they rank well. Links are checked at build time; a dead official link is removed rather than left to 404.

6. Compliance lines

Pages about keys, firmware, or BIOS files must state that those files can only come from a console the reader owns, and must not link or name tools for obtaining them. Pages that touch system-level changes (BIOS settings, boot configuration) carry a risk warning with the exact rollback step. These boxes are rendered automatically from page metadata so they can't be forgotten.

7. Dating

Every page shows its last-verified date. When an emulator ships a breaking change, affected pages get re-verified and re-dated — an old date on a fix page is a defect, not a cosmetic issue.