Article Structure
A shared shape keeps the wiki readable without forcing every page into the same mold. This page describes what a good article contains and when to reach for the fancier syntax. Treat it as a standard to know, not a form to fill.1)
How an article is put together
Most pages share the same bones, in this order:
Lead — one or two sentences saying what the page is about and who it's for. Brief someone over the shoulder: plain, specific, no throat-clearing.
Body — the actual content, shaped by the topic. A config becomes a table of settings. A walkthrough is a description with a spoiler flag where it's needed. A guide is an explanation that earns its length. Don't force a topic into a recipe it doesn't fit.
Related — a short list of pages that genuinely connect, including the section hub.
Tags — `` at the bottom linking the page across namespaces.
The lean template
The minimum you need to start a page:
- template.txt
====== Article Title ====== One or two sentences: what this is about and who it's for. Say it like you're briefing someone over the shoulder. ===== Body ===== Write the content here as prose, tables, or code blocks. Let the topic set the shape. ===== Related ===== * [[minecraft:start|Back to Minecraft hub]] {{tag>minecraft}}
When to use the extras
The installed plugins are powerful when used sparingly:
| Tool | Use it for | ||
|---|---|---|---|
| Tables (` | ` header, ` | ` row) | settings, comparisons, small metadata blocks |
| `<code>` / `<file>` blocks | config values and commands, so they're copy-pasteable | ||
| `<WRAP box …>` callouts | genuine warnings and spoilers only | ||
| `` | cross-linking topics across namespaces, feeding the tag cloud | ||
| `2)` footnotes | asides that would clutter the main text |
If a callout exists only to call something out, leave it out. Plain prose is fine.
Optional metadata
Add a small table near the top when version or status actually matters to the reader: which server release a config targets, or whether a page is still a draft.
| Field | When it matters |
|---|---|
| Type | Guide, Config, Walkthrough, Reference |
| Game / version | when the content depends on it |
| Status | Draft, Review, Published, while a page is settling |
| Updated | last meaningful edit, ISO date |
Conventions
Page names are lowercase with colons separating namespaces (`minecraft:paper-global-yml`), one topic per page, English. Content is CC-BY-SA 4.0: attribute sources, and don't paste game text verbatim.