Editing the wiki

Find the right place

Search for an existing article before creating one. Ordinary recipes, obtaining instructions and short variant descriptions usually belong on the subject's page. Keep larger shared processes in their own guide.

Edit in the browser

1. Open the browser editor and sign in when remote editing is configured. The local developer file backend is a separate workflow that is disabled by default.
2. Choose the mod and article. Update the title, summary, release, evidence and Markdown body. Use the preview to review the text; check the actual site for recipe panels and final layout.
3. Keep unfinished work marked draft or review. Only articles marked published enter the reading site. Article readiness is separate from visibility.
4. Save, then reload the entry to confirm the saved file. On a connected Git backend, use the review workflow before merging and deploying.

Edit through files and Git

Articles live in content/afterfall/, content/brewhaven/, content/civic-frontier/ and content/beyond-overworld/. Keep media in the matching folder under public/media/. Use the shared schema and template in docs/foundation/.

1. Update the article and its sources, keeping its stable key and route.
2. Run npm run check, npm test and npm run build.
3. Review the rendered page with npm run preview, then submit the Git changes for review.

Write for the player

Explain the task using real in-game names, complete quantities and clear steps. Keep the mod’s established lore and avoid inventing new names or story details. Put IDs, internal flags, server settings and operator details under a final Admin & server owner reference heading; the site makes it expandable. Keep important player warnings in the main instructions.

Keep the evidence with the claim

Record the PDF filename, page range, chapter and report evidence IDs. Distinguish reported static findings, packaged data, historical tests and your own observations. Exact values need units and conditions. Pack overrides need their own evidence.

Images and uploads

Use authorized images with a meaningful caption and alt text. The browser media library saves into the shared media folders. Record rights and provenance in the section's asset inventory; a historical screenshot should be labeled historical.

Publish, rename and recover

Saving locally changes files; it does not publish a website. A production build includes only published articles, and deployment is a separate step. Coordinate renames with the main chat so incoming links and redirects can be updated.

Recover earlier text through Git history. Restore the selected revision of the article and related media, run validation, and submit the recovery through review. Keep local changes committed before attempting a recovery. Remote editor conflict and permission behavior must be verified when its backend is connected.