Template:Recipe/doc

Basics
To use Template:recipe, several pieces of information are needed:
 * the name of the item produced by the recipe,
 * the quality of the item ( poor, common , uncommon , rare , epic , quest ),
 * the skill level of the recipe ,
 * the cost to purchase the recipe (including specialty currency like Artisan's Marks)
 * the ingredients to craft the item,
 * and the file name of the icon for the item.

Knowledge of several additional templates is necessary for proper formatting of this template.
 * Template:recipelevel takes the different skill levels of the recipes and formats them by color
 * Template:cost allows entry of vendor cost, whether in platinum or other currency
 * Template:ilink is useful when entering the ingredient list

Usage
Template:recipe has two different methods of entry. The first, and perhaps more common method, is to enter the fields in order. The second uses named variables (in any order) to indicate the different fields. Either method provides the same information, but the first method makes long lists look fairly uniform and easier to edit.

The fields, in order, are as follows:
 * Item name
 * Item quality
 * recipelevel
 * cost
 * ingredients
 * file name

Examples
For readability in this document, examples will be broken into several lines. And, although it is possible to actually use these separations and get an expected result, in practice the data should all be on the same line.

The results of the examples will be shown in one table after the examples.

Example 1

 * &#123;&#123; recipe | Tin Totem | green |
 * &#123;&#123; recipelevel | 1 | | | }}
 * &#123;&#123; cost | | | 3 }}
 * 3x &#123;&#123; ilink | white | Tin Bar }},&lt;br/&gt;
 * 1x &#123;&#123; ilink | white | Cerulean Wax }},&lt;br/&gt;
 * 1x &#123;&#123; ilink | white | Unstable Flux }}
 * Stub.png }}
 * 1x &#123;&#123; ilink | white | Unstable Flux }}
 * Stub.png }}
 * Stub.png }}

Note that the ingredient list uses a forced newline to put each ingredient on a different line. Without breaks, the items in the list may get wrapped at awkward spots, so separating the ingredients onto different lines (or a couple per line) aids in readability.

Example 2
Some information can be left out and the template will still function. At a minimum, the template expects the name of the item. Other information will be either left blank in the table, assumed as a default value, or filled in with question marks.
 * &#123;&#123; recipe | Tin Totem }}

In the absence of an icon, the template uses &#91;&#91;File:stub.png&#93;&#93;. Template:ilink, without a given quality, defaults to epic.

Example 3
In this example, the actual item icon is shown. A few other modifications include adding in the source of the item and the skill leveled at which the recipe is learned.
 * &#123;&#123; recipe | Carmentium Bar | green |
 * (225) &lt;br/&gt;
 * &#123;&#123; recipelevel | | | | 225 }}
 * Vendor &lt;br/&gt;
 * &#123;&#123; cost | | 6 | 75 }}
 * 3x &#123;&#123; ilink | white | Carmentium Ore }}
 * Carmentium_Bar.jpg }}
 * 3x &#123;&#123; ilink | white | Carmentium Ore }}
 * Carmentium_Bar.jpg }}
 * Carmentium_Bar.jpg }}

More examples
More examples are shown in the table (not depicted here) that show variations on how the recipe template can be implemented.