How to Contribute to /v/'s Recommended Games

/v/'s Recommended Games is a volunteer-run wiki, and its own front page says it "lives and breathes on the efforts of volunteers." You can contribute by adding or correcting entries on existing lists, by supplying material when /v/ is discussing a new release or an overlooked older game, and by following the structure the wiki already uses. One important condition: the main page currently carries an "UNDER (RE)CONSTRUCTION" notice, so check the current state of a page before you edit it, since sections may be mid-rebuild.

What the wiki expects from contributors

The site is explicit about its editorial character, and that shapes what counts as a good contribution:

• Recommendations should come from /v/. The front page states that "all of these recommendations come from /v/ (or at least should be)." A contribution is not a general review — it reflects the board's consensus or enthusiasm.
• Taste is expected to be opinionated. The wiki warns readers to "expect tastes that may not match your own, a healthy serving of hateful language, and punishing standards of quality." Matching that tone and standard is part of fitting in.
• It is a wiki, not an official publication. Nothing on the site presents the recommendations as authoritative; they are community picks, which is why the lists are open to revision.

Where contributions fit

The main page is organized around a few areas, and the "Contributions" heading sits alongside them:

The platform list is the most concrete example of the wiki's format: each row pairs a developer/manufacturer with a type, a lifespan, and a name — for instance, "Acorn Computers | Microcomputer | 1983–1985 | Acorn Electron," or "Apple Computer | Computer OS | 1984–2001 | Classic Mac OS." If you add a platform, matching those columns is the minimum bar.

A practical contribution workflow

1. Pick a target. Choose an existing list (a platform page, a genre or special-interest page, or a guide) rather than starting a new page cold. The wiki's value comes from the lists it already maintains.
2. Read the page's current structure first. Note how entries are ordered, what fields each entry carries, and whether the page shows signs of the reconstruction mentioned on the main page.
3. Check whether the game is already covered. Duplicate entries are a common failure mode on recommendation wikis; a correction or an added note is often more useful than a second entry.
4. Write the entry in the wiki's voice. Keep it short, keep it opinionated in the way the rest of the site is, and tie the recommendation to /v/ rather than to your own general impressions.
5. Verify your facts. Platform lifespans, release years, and hardware names are the parts most likely to be wrong. The platform table format gives you a place to be precise.
6. Save and, if the wiki offers one, leave an edit summary explaining what you changed and why — useful when someone later reviews a list that is under reconstruction.

Expected result: your addition appears in the same format as neighboring entries and reads as a continuation of the list rather than a separate review.

Common snags

• Editing a page mid-rebuild. Because the main page announces reconstruction, a page you remember may have been reorganized. Re-read before you write.
• Contributing a personal favorite with no /v/ connection. The site's stated sourcing rule means a game nobody on the board has discussed is a weak fit, however good it is.
• Assuming the wiki is official. It isn't, and treating its lists as a fixed canon leads to edit conflicts with people who treat them as a working draft.
• Ignoring tone. The front page openly warns about harsh language and strict quality standards; contributions written in a neutral review style may simply be rewritten.

If you are unsure where to start, the safest first contribution is a factual fix to the platform table or a small addition to a list you already know well — low-risk, easy to verify, and directly in line with how the wiki is built.