Expedition Station: community knowledge and contributor guide

Expedition Station is best understood as a community workflow for turning AwayTeam observations into durable guides. Its job is to connect scattered notes from playtests, item data, system experiments, and player discussions into a searchable knowledge base.

What it helps with

• New players need a path through oxygen, power, piping, food, and exploration.
• Returning players need to track what changed between tests and versions.
• Guide writers need a place to turn mechanics, tables, and route notes into reusable articles.
• Site maintainers need to keep categories, links, outdated numbers, and empty templates under control.

Suggested roles

A healthy knowledge site usually has several kinds of work. Editors shape page structure, categories, links, and wording. Guide writers explain routes and decision points. Data contributors maintain values such as input, output, temperature, and conversion rates. Visual and outreach contributors make diagrams, banners, and community posts easier to understand.

Maintenance rhythm

During playtests, content changes quickly. Split pages into stable mechanics and temporary observations. Stable mechanics explain long-lived ideas such as oxygen failure, overheating, food shortages, and pipe bottlenecks. Temporary observations should carry version context and focus on what needs to be rechecked later.

How readers should browse

Start from the home page, then move through system guides and item indexes. For emergencies, read troubleshooting material first. For long-term planning, prioritize power, automation, temperature loops, and the food chain.

Writing principles

A useful AwayTeam page answers three questions: what the thing is, what problem it solves in a base, and when it is a poor choice. Names and numbers alone age quickly; context, failure cases, and alternatives make the article useful after the next patch.