Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
titleTable of Contents

Table of Contents
outlinetrue
excludeOverview

Overview

This page provides descriptions and instructions for when and how different elements of wiki pages are used.

Info

PORTFOLIO NOTE
This guide was originally created based on the interface of a server-based Confluence space, rather than a cloud-based space. The interfaces have significant differences.

Please note that identifying company information and non-generic page titles have been redacted throughout this article.

On this page:

Table of Contents

Page Layout

Sections

Pages are laid out in sections, using the "Two column section with right sidebar" style. This format is used to create optimum readability for wiki pages.

Tip

This is a guideline rather than a solid rule. If a large table, screenshot, embedded element, etc. is included in a section, adjust the formatting of the section according to your best judgment to maximize the readability of the page.

Page content is placed in the left column. The right column is reserved as white space, and for "^ top of page" links. In rare instances, annotations may be placed in the right column. All other content goes in the left column.

Info

See Wiki Editing 101#Sections for instructions on how to use section tools in the page editor.

Headings

Use title capitalization rules for headings (any text that will have one of the various heading styles applied to it). Omit periods and colons, and use exclamation points or question marks sparingly. Small words, such as a, an, the, but, and, if, as, or, nor, etc. are not capitalized, unless they are the first or last word in the title. Hyphenated terms in headings will be treated according to Chicago Manual of Style 15 8.1701

Anchor
note1
note1
.

Examples of headings:

...

When to Use Headings

Use headings at the start of a new section, or to highlight important information within a section. Main headings, such as the "Overview" at the beginning of each page, should use the Heading 2 style. The Heading 1 style is almost indistinguishable from the format of page titles, so it is not used.

As a general rule, each section has only one heading. Sub-sections, which would use a Heading 3 (or higher) format, are placed in a new section, immediately below their parent section. Below is how the Info, Tip, Note, and Warning Macros section and sub-sections of this page appear in the page editor.

...

Images

When inserting images, place a border around it to set it off from the rest of the page. This is especially important when the image has a white or light-colored background. Compare these two
examples:

Without Border

Image Removed

With Border

Image Removed

...

The image with the border stands out more clearly as an inserted image, rather than an element of the wiki page.

To place a border around an image, insert the image into the text, click on the inserted image, then click on the

...

Border

...

button to toggle the border on or off.

...

Image Captions

Confluence lacks a method of generating a caption that appears below an image. The following steps are the current best practice for adding a caption to an image.

  1. Insert a 1 x 2 table using the

...

  1. Insert table

...

  1. button in the editor toolbar.

...

  1. Image Added

  2. Insert the desired image into the top cell of the table (a cat picture is used for this example)

...

  1. .

  2. Type the caption in the bottom cell of the table

...

Image Removed

...

  1. .

  2. Italicize the caption text.

...

Image Added

If I fits, I sits

Useful Macros

Status

The status macro generates a small colored box that contains user-entered text. It is a useful way to draw attention to important text, such as the number rating in a list of testing risks.

These are examples of the available colors

...

:

...

Status
titleexample

...

...

Status

...

titleexample

...

...

 

Status

...

colourRed
titleexample
 
Status

...

colourYellow
titleexample
 
Status

...

...

colourGreen
titleexample
 
Status

...

...

colourBlue
titleexample

This is an example of status macros used in (a redacted) Risk Assessment to emphasize the severity of risk ratings:

...

Insert "Status" Macro

  1. Type

...

  1. {status

...

  1. and press Enter to open the

...

  1. Insert 'Status' Macro

...

  1. modal.

...

  1. Image Added

  2. Type

...

  1. desired text

...

  1. for the macro in the

...

  1. Title

...

  1. field of the "Insert 'Status' Macro"

...

  1. modal.

  2. Select the desired color from the drop-down.

  3. If you want an outline style macro, check the "Use outline style" box.

  4. Click the

...

  1. Preview

...

  1. icon to refresh the preview image of the macro.

  2. Click

...

  1. Insert

...

  1. to insert the macro when you are satisfied with how it looks.

Edit "Status" Macro

There are two ways to edit an existing status macro in the page editor

...

:

  1. To edit an existing status macro, double-click on the status macro to open the

...

  1. Insert 'Status' Macro

...

  1. modal.

  2. Click on the status macro you want to edit to open a quick edit toolbar.

...

  1. Image Added
  • Click the

...

  • Edit

...

  • button to open the full status macro editor.

  • Change the text of the macro using the text entry field (it contains the text "EXAMPLE" in the above screenshot).

  • Change the color by clicking the corresponding color button.

  • Click the

...

  • Remove

...

  • button to remove the macro entirely.

Info, Tip, Note, and Warning

Info, Tip, Note, and Warning macros are helpful for setting off important information from the surrounding text. See the Info, Tip, Note, and Warning Macros page for detailed information on how to use these macros. Examples of the macros in use are shown below.

Info

From the (

...

Redacted) page:

Logs and Dump files are both located in the same folder, which changes based on the executable used.

Info

If the user is using a (Redacted1) configuration file (redacted1.exe), logs and dump files will be located in C:\Users\<username>\AppData\Local\GameFolder\Saved\Logs

If the user is using a (Redacted2) or (Redacted3) configuration file (redacted2.exe or redacted3.exe), logs and dump files will be located in ...\<launcherfolder>\GameFolder\GameFolder\Saved\Logs

Server files require a request from department QA Leads or the Tech team.

Tip

From the (

...

Redacted) page:

This page details the process for awarding XP in (the game). Note that this can only be done in testing builds, and that awarding XP on the live servers for testing requires Production approval.

Tip

Access Server IP Addresses and click on the (program) Link to access (the program) with ease

REMINDER:

...

 Login credentials are only provided by department managers, or with their approval

Note

From the PS4 Bug Format page:

Video clips are saved into the capture gallery the same way as a screenshot is saved. When you save a video clip, however, the video is save retroactively. For example, depending on your capture gallery settings, selecting save video clip will save the 3 minutes of gameplay on your screen BEFORE you selected "save video clip". This is different from saving a video through Fraps where you must start recording before you reproduce the bug.

Note

Video clips saved by the PS4 cannot be processed by Movie Maker, so the clip must be trimmed in the PS4 before it is uploaded to the USB drive.

To do this, select the chosen video clip. Then, select the Options button. This will bring you to the Trim Screen. You can Trim your video in intervals of a selected amount of seconds. Use the left stick and X to select where you wish the video to begin and end.

Once you have selected how you wish your video to be trimmed, select "OK" to save trim.

Warning

From the PS4 Bug Format page:

Unlike the PC, evidence for bugs must be transferred from the console to the PC physically using a USB drive. USB drives can be obtained from a PS4 lead. 

Warning

ALL USB DRIVES

...

MUST BE RETURNED TO THE LEAD BY THE

...

END OF THE DAY

Labels

Add appropriate labels to each page. Adding labels to a page helps group related pages together and make related pages easier to find. Try to only use existing labels if possible (a complete list of the labels currently in use can be found here). Look at other related pages to see what labels they use. If a new label is necessary, try to keep it short and simple (one word only), but descriptive; think of what the page might be listed under in the index of a printed book.

Labels can be added to a page in the process of being created or edited by clicking the

...

Labels

...

 icon next to the page title:

...

Labels can be added to an existing page by clicking the pencil icon in the bottom right corner of the page:

...

Date

To add a neatly formatted date () to a wiki page:

  1. Type two forward slashes.

    • Example:

...

...

    • Code Block
      //
  1. This opens a calendar

...

  1. modal that allows you to select a date.

...

  1. Image Added
  2. Use the < and > arrows to select the month

  3. Click on the date to add it to the page

    • Example:  

^ Top of Page

If a page is very long (e.g. contains three or more sections), add "^ top of page" link at the bottom of each section. This allows a user to return to the table of contents and jump directly to another
section of the page if they wish. The horizontal line at the end of each section helps to visually separate and "chunk" a large quantity of sections.

There is no dedicated macro for creating a "^ top of page" link, so it has to be created manually.

  1. Insert an anchor macro at the very top of the page, before the "Overview" heading

  2. On a new line after the last word of text, type three dashes to create a horizontal line.

    • Example: 

      Code Block
      ---
  3. Below the horizontal line, create a link to the anchor you created at the top of the page; the link text should be "^ top of page".

  4. The "^ top of page" link can be copied and pasted multiple times on the same page without having to repeat the above steps for each link.

...

Footnotes

  1. CMS 15 8.170:

...

  1. Hyphenation: The more traditional rules. (1) Always capitalize the first element. (2) Capitalize any subsequent elements unless they are articles, prepositions, coordinating conjunctions (and, but, for, or, nor) or such modifiers as flat or sharp following musical key symbols. (3) If the first element is merely a prefix or combining form that could not stand by itself as a word (anti, pre, etc.), do not capitalize the second element unless it is a proper noun or proper adjective. (4) Do not capitalize the second element in a hyphenated spelled-out number (twenty-one, etc.). (5) Break a rule when it doesn't work."

...