BETAServer is in pre-launch beta · official launch date TBAWhat this means →
Crushbone

meta

Contributing to the Wiki

How to add, edit, and correct wiki content. The style guide.

The Crushbone wiki is a living reference. It lives as plain markdown files in the crushbone-site repo under content/wiki/. Anyone can propose edits.

How to contribute

  1. Identify the page (or gap) you want to edit.
  2. Drop a note in Discord #wiki with the proposed change.
  3. For members with repo access: edit the markdown file directly and commit.
  4. For members without repo access: share the proposed text in #wiki and a GM will commit it with attribution.

Style guide

  • Voice: literary, serif-toned, a step above casual. The existing pages set the rhythm.
  • Tense: present.
  • Headings: H1 is the page title (auto-generated from frontmatter). Use H2 for section breaks, H3 sparingly.
  • Links: Internal wiki links use /wiki/<category>/<slug>. External links go to github.com, wiki.takp.info, or wiki.project1999.com.
  • Tables: Use markdown tables for facts-per-zone, stats-per-class, stats-per-race.
  • Lists: Use bullets for enumeration, numbered for sequences.
  • Code blocks: Triple-backtick for code, single-backtick for inline values (spell names, NPC names, ini fields).

Frontmatter schema

---
title: <page title>
description: <1-sentence description, used as meta-description>
order: <number, sorts within category>
updated: <YYYY-MM-DD>
---

The category is inferred from the folder the markdown lives in.

What to avoid

  • Don't invent. If you don't know a drop rate, a spawn timer, or an exact stat, omit it or say "approximate." The wiki loses credibility with specific-looking facts that turn out wrong.
  • Don't spoil. We're not a walkthrough site. Strategy for raid bosses, specific kill orders, and exploit guides go in guilds' private docs, not here.
  • Don't duplicate. If a page already covers something, link to it instead of restating.
  • Don't over-cross-reference. Two or three links per section is the sweet spot; more becomes noise.

Page templates

See existing pages as templates:

Editorial review

GMs review every wiki edit for accuracy and tone. Non-controversial additions (new zone page, new tradeskill page) ship within a day. Rewrites of existing content take longer — expect a conversation about why before the merge.

Related