Style Guide

{{Page | text = Welcome to the Crafty Games Fan Wiki style guide & FAQ.

Wiki 101
Never edited a wiki before?

One of the simplest ways to get to grips with what's goin on is simply to click the Edit Page link and have a look at the code people have used. For those who's prefer a slightly more structured approach, here's a page dealing with the basics of text formatting.

It's really important to read at least that page, though I thoroughly recommend following the links at the bottom of it to familiarise yourself with some of the more advanced options, such as templates: this wiki uses quite a few of them.

Attributing Work
We stand on the shoulders of giants here, so we ned to make sure people are credited for their efforts.

Categories
Every designer whose work has at least one dedicated page should be given their own category in the format Designer "name" where "name", is replaced with the person's preferred name, ie Designer Koschei. Categories can easily be added using the editor.

In-line
On pages containing content by multiple authors such as a compilation of Talents, authors should be referenced on the line immediately below the appropriate heading. Typically it takes the following form: &#38;&#35;&#57;&#49; "Name" &#38;&#35;&#57;&#51; resulting in &#91; "Name" &#93; Using the ansi code is important due to the way wiki interprets the actual &#91; and &#93; characters to identify links.

In the case where the designer already has a category, you can use the following to link to it &#38;&#35;&#57;&#49; "Name" &#38;&#35;&#57;&#51;

Making a New Page
So, you've got an idea of what you want to write and how to write it. You'll see a link on the side bar named Create a new article; when you click on it, you'll be given a choice of standard layout or blank page. Choose the latter.

Template: Page
If you want to make your page look a bit nicer, there's the Page template which will give you some white space between the edge of your text and the screen. As you'll see when you follow the link, each template has a "how to" entry that you can simply copy-and-paste into your new page.

A reminder that an error with html, such as a broken bracket can affect the way the page displays; it's wise to click on the preview button before saving a page.

Template: tab & btab
The tab template & btab template are another great layout assistant for our wiki: they breaks up chunks of text by identing the first line of a text block so they're easier to read on screen; the btab template also inserts an extra blank line. When you look at the code for this page, you can see how it's been used at the beginning of each paragraph and the end of each section. It's important to remember that you can't manually indent using your space bar, because wiki reacts to a leading space with a funny little box

like this

which messes with formatting, especially for long strings of text. Similarly, there should be no blank spaces between the and the first character of the paragraph, but that's purely to help generate a uniform look.

Class Progression Tables
Tables can be hard work to use in a wiki, especially if they need extra formating. To make life easier, the prog template exists to largely automate the process of creating the level progression table for a class. It handle all three class types.

Linking to other Wikis
Sometimes you will feel a need to link to a wiki outside this one. While it's possible to use the [[metawikipedia:Help:Link#External_links|]] form, which works in all instances, you may feel that's a little on the inelegant side. Shortcuts to some of the more common wikis can be found here.

Inline Definitions
Sometimes when you write an article or a chapter, you might find yourself using a technical or in-inverse term the meaning of which is not always evident to the reader. You want to inform the reader of its meaning, but doing so inline may not be possible without disrupting the flow of the text and you may not want to include an external link. For instance, people might not even know what a d20 is.

The above link is achieved with the following code: object being defined

}}