This is a (rough) guide for formatting Fancade wiki pages.

Table of Contents

Formatting

Wiki pages should not use one hash symbol to create sections and subsections, as the size would match the title page.

  • NO: # Section
  • OK: ## Section

Layout

Games

The article's title must match the casing of the game.

A snapshot of the game may optionally come first before the article content. Please use one image only.

Afterwards, the game name is written, and should link to its corresponding play.fancade.com game, with a description of the game thereafter, which may include:

  • who made it,
  • when it is introduced to Quest
  • Fanjam winner for…

The How to Play section should come next. Inside this section should show comprehensive details on the controls, and the resulting actions, as well as how objects interact, etc.

The following is optional but recommended to be added:

  • Solutions, showing the various solutions for each level. The notation should be described, unless controls are simple enough (e.g. swiping). Used for puzzle games.
    • The arrow macros can be used in cases like swiping. Enclose the cardinal direction in two angled brackets: << + W + >> = ←. W, NW, N, NE, E, SE, S, SW are available.
  • Walkthrough, linking to YouTube videos to solutions, in a series of levels. Generally used for non-puzzle games.
    • A playlist should be preferred if it is provided (or created), unless it is moderately out of order.
  • Credits by the author
  • Related, links to related articles.

Other optional sections may be created if there are technical details to the game (e.g. Extreme Painist)

Blocks

The title must match the casing of the block.

The article should firstly contain what the block does.

The inputs are listed next, from top to bottom. This should be indicated with Inputs: on the top (not a section, just plaintext). Outputs are listed similarly.

The image of the block is put hereafter.

Then, Notes comes next. This should contain all the necessary information about the block, along with its quirks.

The Example section comes next. In each example, the description of what the script does comes first before the image.