Minecraft Wiki:Style guide/Versions

All version articles should use the following layout, to allow for consistency between version articles.

Introduction
At the very top of the article, version history nav should be placed.

After templates should be an introduction with a general description. This description should contain the release date of the update, and a brief description of the update. If it is a development version, it should state which version of it is a development version.

Additions, Changes, and Planned additions
These three sections are combined in the guide due to similarity, in the actual article this is three separate sections. General changes in a version should go within the three sections as follows:
 * Additions: Any new features added in the version. This includes features added in development versions.
 * Changes: Any changes to old features from the version. This includes features changed in development versions.
 * Planned additions: Any features announced for this version that have yet to appear in a development version.

If the version is a full release, each section also should have the following subsections:


 * General: General features, such as options, splashes, and graphics changes.
 * Gameplay: Features relating to gameplay mechanics, such as achievements, status effects, game modes, and visual changes
 * Commands & NBT Tags: Features related to mob tags or commands
 * World Generation: Features related to world generation
 * Blocks and items: Features that are either blocks or items
 * Mobs: Features that are mobs.

Fixes
Bugs fixed in this version using fixes. Bugs should also be organised into sections using the following headers:


 * Fixed in the development versions
 * From released versions before
 * From the development versions
 * From the previous development version
 * From the current version, hotfixed

Note that fixes supports shortcuts for common headers.