SS14:Style Guide

This page describes how the wiki is styled: how certain elements should look and behave. For all relative examples, I will be using the science department page.

For formatting, see the SS14:Formatting guide.

Page title

The page title should sit at the top of the page. Titles of content pages (i.e. regular pages) should follow Title Case - first letter of each word is capitalized, except some words like "over", "a", etc.

Titles for other pages (category, template) should follow Sentence case - only the first letter is capitalized.

Callout/Warnings

This banner should sit below the page title. Many pages can be highly volatile or considered a WIP. If you need to state a custom banner any reason use Template:Callout. If you prefer to use premade templates though there is Template:Important and Template:Unfinished.

Preamble

The preamble should sit below the title of the page. If a page requires an introduction to the information then introduce a preamble.

Table of Contents (TOC)

The table of contents should sit after the preamble. The TOC can be edited using Template:TOC. Generally, keep the TOC floating left and keep the depth between 3-4. If you absolutely need the depth to be longer, then you can but it can easily be overwhelmingly large if above 4.

Content

Most pages will follow their own logical breakdown of the content within.

However department pages follow a guideline of:

1. Sections of X
2. Jobs of X
3. System 1
4. System 2
5. System X...
6. Equipment
7. Guides

Headings

Headings should sit below both the TOC and their authoritative headings (i.e. Subheading 1 should sit under Heading).

• Headings should typically follow a logic of Heading for large sweeping topics.
• Sub-heading 1 for subsections of headings.
• Sub-heading 2 for subsections of sub-heading 1 sections....etc.

The way you should use headings is generally going to be determined by how you're going to break down a subject.

Paragraphs

Paragraphs should sit under each respective heading.

• Context paragraphs should provide an overview about what you're going to talk about in depth later.
• Content/Depth Paragraphs should provide a clear and in depth explanation of how a system works to the best of your ability.
• Supporting images should be used frequently and to aid in the explanation of what you're talking about and how to use something.