How contributions work
The Fallen World wiki does not use separate website accounts. GitHub is the account, edit history, review queue, and moderation layer.
Community contributors can:
- submit a new guide
- improve an existing page
- add screenshots or diagrams
- correct outdated information
- propose new documentation inside the existing wiki categories
Nothing becomes part of the live wiki until repository contributors review and merge the change.
Submit a new community guide
Create a community guide on GitHub.
GitHub will guide you through creating the file and proposing it as a pull request if you do not have direct repository access.
Start your guide with metadata like this:
---
title: "My Guide Title"
description: "One clear sentence explaining what the guide helps players do."
category: "community-guides"
type: "community"
status: "current"
updated: "2026-09-01"
lastTested: "2026-09-01"
difficulty: "beginner"
tags:
- example
- useful-keyword
author: "@YourGitHubUsername"
featured: false
order: 100
related: []
---Then write the guide below the metadata using Markdown. Community submissions use .md files instead of MDX so guide content stays data-only and cannot import or execute site code.
What a good guide includes
A useful guide should answer these questions quickly:
- What problem does this solve?
- Who is the guide for?
- When was it last tested?
- What does the player need before starting?
- What are the exact steps?
- What can go wrong?
- How can the reader verify it worked?
Screenshots are encouraged when they make the steps easier to understand.
Screenshots and media
Commit screenshots with the same pull request instead of depending on temporary image hosts.
Put community wiki media under public/img/wiki/ and reference it from the guide using a root-relative path such as:
Use compressed web-friendly formats when possible. Avoid uploading huge raw screenshots when a smaller image communicates the same thing. Link to videos using normal Markdown links. Maintainers can add a reviewed embed later when an inline video materially improves an official page.
Spoilers
Community Markdown may use <details> and <summary> for collapsible spoiler sections. Other raw HTML is intentionally rejected by wiki validation.
Official vs community pages
Community guides are clearly marked as Community Guide and credit the GitHub author. Official pages are maintained by Fallen World contributors.
A community guide can still be corrected or maintained after it is merged. The original author credit remains unless the guide is replaced for a clear editorial reason.
Edit an existing page
Every wiki article has an Edit this page on GitHub button. Use it for corrections or improvements. GitHub keeps the diff focused on the page you changed and lets contributors review exactly what changed.
Report outdated or incorrect information
Every article also has a Report a Problem button. Use that when you know something is wrong but do not want to write the fix yourself.
Guide statuses are intentionally simple:
- Current: the guide is considered valid for the current Fallen World build.
- Outdated: the guide is known to need revision before players should rely on it.
Review expectations
A pull request may be rejected or asked for changes when it:
- gives unsafe or destructive installation advice
- conflicts with supported Fallen World configuration without clearly saying so
- has no last-tested date for community content
- copies somebody else’s work without credit
- contains broken media or links
- is too vague to follow
- belongs outside the wiki’s controlled top-level categories
- uses MDX or unapproved raw HTML in a community guide
The goal is not to make contribution difficult. The goal is to keep the wiki reliable enough that players can trust what they read.