Dwarf Fortress Wiki:Versions

These are the methods we use to organize versions on the wiki. Please bring any questions to the talk page.

Goal

The goal of this effort is to effectively mark articles according to the version they are about. Ultimately there are two goals:

• Allow users to know what major version (23a, 40d, etc...) an article pertains to.
• Allow editors to easily find topics for which a current version article is not complete.

This is not intended to:

• Remove all information about older versions. These articles have been moved to appropriate namespaces (ex. 40d:, 23a:), and the {{ArticleVersion}} template (which should be added to every version specific page) links between the various versions, noting clearly (through color and message) whether it is the current version.

Approach

Per topic

Each feature or idea that has an article will feature the "up to date" version and "old" versions: (note, if an article is version independent these points do not apply)

• The mainspace article will (usually) never contain anything.
• There will be namespaces for every major version: "DF2014" (likely to be renamed once a new save-incompatible DF version is released), "v0.34", "v0.31", "40d", and "23a".
• The cv: alias will redirect to the current version, ie. "Main".

Version articles

There is a template that should be placed on all version-specific pages. It looks like this (though it looks different on actual articles):

This article is in the DF wiki namespace. More Info · V

An example of this template on a real page can be seen at "milk": Main:Milk, v0.31:Milk, 40d:Milk, 23a:Milk.

This template is added by placing {{av}} (or {{ArticleVersion}}) at the top of an article.

The template will check the namespace of the article and use that to determine if the article pertains to the current version or not.

It will also place an article into a category based on whether or not it pertains to the current version.

One version will be considered "current", and articles in that namespace with the version template will be placed into a category marking it as such, all other articles will be put into a category marking them as Obsolete, and also placing them into a category based off of their version (from the article namespace).

With very little effort (read the documentation) every page's version template can be automatically updated when a new version arrives. This process automatically changes what namespace shows up as current on each page and what categories pages are put into. This makes it wonderfully easy the next time a new version comes around.

Redirects

Redirects to content in the current namespace should almost always be created in the current namespace, not the main namespace, and should use the current namespace as the namespace for the redirect. Redirects created in the main namespace to pages in a versioned namespace should only redirect to pages with the same name (create double redirects if needed). For example, Main:Kitten should redirect to Main:Cat, not Cat or cv:Cat. In cases where a redirect does need to be created in the main namespace, use "cv" for the redirects namespace instead (this is a shortcut to the current namespace). (Note: Currently there seems to be a bug with such redirects in that they redirect to the v0.34 namespace instead of DF2014.)

Pages in the mainspace should only redirect to an older versioned page if that content no longer exists in the current version of the game (e.g. Cave river, Chunk). In these cases the cv: alias cannot be used.

Redirects inside a versioned namespace should always use that namespace as the prefix (e.g. DF2014:Dodging, v0.31:Drink), not the cv: alias.

An example of redirecting the page "kitten" to "cat":

	Main namespace	Main
Kitten	Kitten #REDIRECT cv:Kitten →	Main:Kitten #REDIRECT Main:Cat ↓
Cat	Cat #REDIRECT cv:Cat →	Main:Cat content about cats

---

Although a lot of this is already underway, you should still feel free to make suggestions or bring up any comments on the talk page.