Wiki:Manual of Style
This is a (rough) guide for formatting Fancade wiki pages.
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 ==
Always provide an empty line before and after each section, for easier editing.
In the Solutions section of game articles, use Heading 4 for each level / series of levels:
- ==== Levels 1-100 ====
Layout
Games
The article's title must match the casing of the game.
Games with a conflicting article, regardless of casing should write "by", then the author enclosed in parenthesis. No formal rule is set, so currently the newer article should disambiguate the author. (h and H (by HexaPhoenix))
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:
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. This section may also be alternatively named Gameplay.
The following is optional but recommended to be added:
- Entities, the function and interaction of each necessary object present in the game. This is listed in bullet form.
- Shop system, describing the various upgrades and how it affects the gameplay.
- 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 template should be used in cases like swiping.
- Walkthrough, linking to YouTube videos of 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.
Please note the article is not restricted to using only the above. Other sections may be created when necessary.
Examples:
Blocks
The image should be placed before the content of the article.
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.
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. If required, an explanation can be added after the image.
Example:
Other
Other articles may not fit in the category. In this case, proper formatting. When in doubt, you may use the Chicago Manual of Style for title casing of articles, unless the article title and content is similar to a Q-and-A format, to which you can use sentence casing (mostly Build articles, like How to create a circle)