ATITD Wiki: Wiki/Formatting

Standard Wiki Formatting

  Separate paragraphs with

  a blank line.

Separate paragraphs with

a blank line.

  Use tags to write text in <b>bold</b>, <i>italics</i>, or <tt>monospace</tt>.

Use tags to write text in bold, italics, or monospace.

 You can also use single quotes to make text '''bold''', ''italic'', or '''''both'''''.

You can also use single quotes to make text bold, italic, or both.

  Use tags for superscript and subscript: E=MC<sup>2</sup>, A<sub>1</sub> = A<sub>2</sub>.

Use tags for superscript and subscript: E=MC², A₁ = A₂.

  Indent text to cause it to appear in a monospaced font with spaces preserved.

  :Start a line with a colon to set it off as a block of quoted text.

Start a line with a colon to set it off as a block of quoted text.

Headings

  = Heading 1 =
  == Heading 2 ==
  === Heading 3 ===
  ==== Heading 4 ====

Heading 1

Heading 2

Heading 3

Heading 4

Lists

Start a line with a # to create a numbered list.

  # One
  # Two
  ## Two point one
  ## Two point two
  ### Two point two point one
  # Three

One
Two
1. Two point one
2. Two point two
  1. Two point two point one
Three

Use a leading asterik to create a bulleted list.

  * Level one
  ** Level two
  *** Level three

Level one
- Level two
  - Level three

Redirecting

It is possible to redirect a page to another page by having the first line be: See Page_to_Redirect_To OR See [[Page to Redirect To]]. ($REDIRECT will also work.) For example to redirect Grass to Basic Resources the page would be:

See Basic_Resources

See [[Basic Resources]]

ATITD Wiki Custom formatting

Tables

Create tables by beginning and ending each line with "||" and separating each column with ||. Align text to the left or right in a cell to align it in the table.

  ||  Column 1  ||  Column 2  ||  Column 3  ||
  ||  Center    || Left       ||      Right ||
  ||      Right ||  Center    || Left       ||

Column 1 Column 2 Column 3
Center Left Right
Right Center Left

Column 1	Column 2	Column 3
Center	Left	Right
Right	Center	Left

Tables may be automatically formatted with the $TABLE directive. Place "$TABLE <format>" directly before a table. The format consists of a list of letters, separated by spaces:

r - Right-justify column
l - Left-justify column
c - Center column
d - Delete column
i - Insert new column

Table formats will be reapplied every time a page is saved or previewed.

For example, after submitting the following table:

  $TABLE l d r i c
  || 1 || 2 || 3 || 4 ||
  || foo ||bar||baz ||snrub||

The page will contain:

  $TABLE l r l c
  || 1    ||    3 ||          ||  4      ||
  || foo  ||  baz ||          ||  snrub  ||

The $TABLE directive itself is never displayed.

A table may be made borderless by placing a "$TABLE noborder" directive before it.

Subpages

Subpages provide a way to organize topics within the wiki. Subpages can allow a large topic to be split up into multiple pages without adding a very long prefix to each page.

This wiki's subpage implementation differs from the original UseModWiki one. (See UseMod:Subpage.)

A subpage is referred to as MainPage/SubPage. For example: [[VoK Megalopolis/Member List]]. By default, however, only the subpage name is displayed: Member List.

Links without a main page reference, such as [[Joe User]] will be implicitly turned into a link to the appropriate subpage if there is only one page with that name. For example, if there is a subpage named "Users/Joe User", and no main page named "Joe User", the above link will be converted to [[Users/Joe User]] when the page is saved. If you explicitly want to link to a top-level page named "Joe User", write the link as [[/Joe User]].

You may link to a subpage under the current page like this: [[./Subpage]].

You may also have a multiple levels of subpages, such as [[Scratch/Foo/Bar]].

Subpages should be used in the following circumstances:

When splitting a single specific topic into multiple pages. Project pages such as megalopolises are a perfect example.
When organizing a group of pages that may contain names that conflict with other topics. For example, user pages should go under the Users topic.

Topics of general interest should not be placed in subpages. For example, Flax, The Test Of Festivals, and Alchemy Formulas should all be top-level pages.

Automatic Timezone Conversion

You can specify dates in such a way that they will be displayed in both UTC and the user's local timezone.

The date should be of the form {YYYY/MM/DD HH:MM UTC}. For example,

{2003/11/10 01:30 UTC}

will yield:

2003/11/10 01:30 UTC

If the user has javascript turned off, then the UTC data as you entered it will be displayed unchanged.

Note: The code currently uses a <DIV>, but really should use a <SPAN>. However, the <SPAN> code didn't work in IE (go figure). I'll try to fix that. -- Mjr

Use getElementsByName (and use the name field) instead of getElementsByTagName, perhaps? -- Taral

Tech tree links

Link to resources in the tech tree with the Resource: and Building: InterWiki links. (Or R: and B: for short.)

  [[Building:Flax gin|Flax gins]] are used to process [[Resource:flax]] into [[R:tow]]...

Flax gins are used to process flax into tow...

Maps

Add a map to a page with indicators marking specific spots with the "$MAP" directive. See the Location Maps topic for more information.

Automatic Indexing

Add a page to the Guides or Atlas sections by including an appropriate index statement in the page:

  $GUIDE Page
  $ATLAS Altars > Common

Index contains a listing of all of the pages on the Wiki. To not include a page there, add a "$NOINDEX" line to it.

Stylesheets

Pages under the Styles topic are assumed to contain a CSS stylesheet, rather than a normal wiki page. Users may elect to use one of these alternate stylesheets via their preferences page.

Todo: the Standard Wiki Formatting section doesn't explain anything about how to make links. I know I remember seeing it explained somewhere else, but it really ought to be here too. -- Brant

Wiki > Formatting