BETAOfficial launch July 9, 2026 · All/All/All race/class/deity · TLP · Classic → PoP eraBeta open now →
THE LAST CAMP
Wiki

Meta

Contributing to the Wiki

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

The Last Camp wiki is a living reference. It lives as plain markdown files in the crushbone-site repo under content/wiki/. Contributions go through GitHub PRs — the Edit on GitHub link in every page footer takes you straight to the file.

Anyone can propose edits. The GM team reviews for accuracy, era-correctness, and tone. The bar is editorial, not gatekeeping.

How to contribute

  1. Identify the page (or gap) you want to edit.
  2. Use the Edit on GitHub link in the page footer, or browse content/wiki/ in the staybased/crushbone-site repo.
  3. Fork → branch → edit → open PR. Vercel posts a preview deploy on every PR — review your change live before requesting merge.
  4. For substantial additions (new page, new category), drop a note in Discord #wiki first so we can coordinate naming and avoid duplicating work.
  5. For members without GitHub fluency: paste the proposed text in #wiki and a GM will commit it under your handle in the PR description.

Style guide

  • Voice. Dry, factual, reference-tone. A step above casual but not academic. Existing pages set the rhythm — read Iksar and Necromancer for the cadence.
  • Tense. Present.
  • Sentence-per-line for long-form prose. Improves diff readability.
  • Headings. H1 is the page title (auto-rendered from frontmatter). Use H2 for section breaks, H3 sparingly. Avoid H4+.
  • Cross-link generously. Two to four links per section is the sweet spot. Prefer internal /wiki/... links over external when the topic exists internally.
  • Tables for at-a-glance facts (stats per class, NPCs per zone, spells per level).
  • Lists — bullets for enumeration, numbered for sequences.
  • Code blocks. Triple-backtick for code snippets, single-backtick for inline values (spell names, NPC names, ini fields, file paths).

Frontmatter schema

Every page requires frontmatter:

---
title: <page title>
description: <one-sentence specific description, used as meta-description>
order: <integer; sorts within category>
updated: <YYYY-MM-DD>
---

The category is inferred from the folder the markdown lives in (/wiki/zones/... → category "zones").

Markdown conventions

  • Internal links use /wiki/<category>/<slug>. Examples: /wiki/zones/crushbone-keep, /wiki/classes/monk.
  • External links to the canonical EQ refs: wiki.project1999.com, wiki.takp.info, lucy.alkabor.com, everquest.allakhazam.com.
  • Numbers. Spell out one through nine in prose; use digits for 10+ and for stats.
  • Hard rule. No emoji except in functional contexts (the 🔗 column on spell tables, etc).

What NOT to add

  • Custom-NPC mechanics. Keepers of the Way, Cogsworth lore-drops, server-original encounter solutions — discovery is part of the design.
  • Real-name dox of staff or players. Use GM character handles (Rusty, Cogsworth) and player character names only.
  • Hype tone. No "epic," "amazing," "best server ever." This is a reference, not a sales page.
  • GoD+ content. Era-locked at Planes of Power. The live peq DB has post-era material; the wiki does not advertise it.
  • Made-up numbers. If you don't know a drop rate, a spawn timer, or a stat, omit it or say "approximate." The wiki loses credibility with confident-sounding facts that turn out wrong.
  • Duplicates. If a page already covers the topic, link to it instead of restating.

Page templates

See existing pages as templates:

Tooling

The site is Next.js + MDX deployed on Vercel.

git clone git@github.com:staybased/crushbone-site.git
cd crushbone-site
pnpm install
pnpm dev          # local preview at http://localhost:3000
pnpm build        # production build
pnpm typecheck    # validates frontmatter + link resolution

Vercel posts a preview deploy URL on every PR. Use it to verify rendering before requesting merge.

Editorial review

GMs review every wiki edit for accuracy, era-correctness, and tone.

  • Non-controversial additions (new zone page, new tradeskill page, typo fix) ship within a day.
  • Rewrites of existing content take longer — expect a conversation about why before merge.
  • Factual disputes are settled against the live peq DB / TAKP / P99 in that order. The Last Camp-specific tuning overrides P99/TAKP where they conflict.

Auto-generated pages

Bestiary entries and (eventually) item pages are auto-generated from the live database. If you spot a generated page that reads as obviously templated, the easiest contribution is to open a PR rewriting the prose sections. The frontmatter and stat tables are safe to leave alone — the next regeneration will preserve hand-written editorial blocks marked with the <!-- editorial --> comment fence.

Attribution

Commits land under the contributor's GitHub handle. The Crushbone GM committer (Rusty) handles batch edits, regenerations, and any commit that needs to attribute to the server rather than an individual. Real names are not used in commit history, page bylines, or the Credits page.

Related