Template guide

From Chronicles of Blood Wiki
Jump to: navigation, search


Page templates

We have page templates set up for several common types of information:

Calling page templates

You can see the list of page templates by clicking on the "Templates" item in the editors sidebar.

You call a page template by entering:

{{Subst: Template-name}}

on the first line of your document and immediately saving that page.

When you re-open the page for editing, you will find a number of items set up for editing, changing, or deleting, depending on the particular requirements of your page.

What's in a template

These page templates try to define all of the major categories of information that may be required on a particular page. This means that there is always at least one section of a page that is irrelevant to a given item and that needs to be deleted.

For example, the "Weapons" template includes the sections to describe weapons that are

  • dropped as loot;
  • crafted with the help of one of the location-specific merchants; and
  • purchased from one of those location-specific merchants.

One of the tasks of creating the page is to determine which sections need to be included and which need to be deleted.

If you are not willing to do the work, or if you do not understand our page-naming conventions, then please wait for someone who does to set the page up before you begin adding information.

Why use templates?

We use templates to standardize the content and presentation of particular types of pages and information. Doing this makes it easier for players to find the information they need on a particular page, since it is presented consistently.

This means that it is not your job to edit or change standardized headings, etc. If you have suggestions for changes, you are welcome to suggest them to the Sysop for consideration.

Small templates

We use a number of small templates to control bits and pieces of our pages — particularly items that are shared among many pages.

Those templates are generally called with

{{template name}}

or if variable information is required,

{{template-name | variable-name = }}

where the value is filled in following the = sign.

There are small templates like this that contain list item descriptions of all feats and procs, for example.

You can always see the complete set of proc list item descriptions by checking "Templates: Proc list templates" through the sidebar.

Similarly, the feat description items can be found through "Templates: Feat description templates".

Almost always when you call a "proc list" template, you call a "proc level" template following it. The proc level template can, and almost always should, be customized not just with the name of the proc and its level but also with an article preceding the page-item's name, and possible a word following it to make a grammatically complete and understandable sentence.

Other templates

In addition to the page templates, we have a number of smaller templates that are called and used for entering particular types of information (such as "Absorbs damage" in the box describing pieces of armor, or for entering the name of an image file).

We also have small templates for all of the procs that can be associated with a piece of armor, a weapon, an accessory, etc. For a list of those pros, see: Templates / Box templates.

The same is true for the prose descriptions of the procs that is part of the description section of pages. Those descriptions can be found by looking on the Templates page and then at "Proc list templates".


If you have questions, please address them directly to the sysop.

New templates

Do not create new templates without discussing them with the sysop first.

Template components

Most templates are made up of a number of "template components" that can be used or deleted as appropriate. If a template component isn't needed for the page you're working on, delete it — and delete the empty spaces that are left behind too!

Template components give us standardized language and formatting of items that tend to have variable values, while simultaneously allowing us to include only the pieces we need in any particular page. It also means that if the name of something (say, "Absorbs damage") changes, we can change that name in the template and all of the individual pages that use that template component will be updated the next time they are opened by anyone.

Personal tools
other gameplay