Minecraft Wiki:Style guide/Versions

This article aims to provide a comprehensive style guide for Minecraft Wiki version articles to follow. This article is only about guidelines specific to version articles, for other guidelines, see Minecraft Wiki:Style guide.

Creation
Version article may be created provided the version is released, or there is a significant source of the unreleased version's existence. Sources include development versions or multiple sources of features for the next update.

Development version article may only be created if the development version exists, even if features have been revealed for the next development version, or there is a good source as to the next development version's title.

Versions of editions other than the computer edition are currently stored on the relevant Version history and Version history/Development versions articles.

Naming
Version of the computer edition are named using the version name, such as  or.

Pre-releases should be formatted with a single dash between the parent version and the word "pre". If the pre-release contains a number at the end, it should be placed with nothing bewteen "pre" and the number. For example:.

Article layout
All version articles should use the following layout. Ensure section titles have one return space above them, one return space below them, and a space on either side of the title inside the equal signs.


 * At the very top, version history nav should be placed.
 * 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.
 * Article body, starting with first header.

''Note: Keep in mind these are supposed to be h2 (two ='s). For the purpose of formatting on this page only, they are h3 (three ='s).

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.