Login

Fancade Wiki

Updated Manual of Style.md (markdown)

Wiki/Manual of Style.md
... ...
@@ -15,6 +15,10 @@ In the **Solutions** section of game articles, use Heading 4 for each level / se
15 15
16 16
- <span style="color:green">#### Levels 1-100</span>
17 17
18
To add a video, use the following macro:
19
20
- <code><&#x200b;<Video(/uploads/name-of-the-video.mp4)>&#x200b;></code>
21
18 22
## Layout
19 23
20 24
### Games
... ...
@@ -44,14 +48,18 @@ Other optional sections may be created if there are technical details to the gam
44 48
45 49
### Blocks
46 50
51
The image should be placed before the content of the article.
52
47 53
The title must match the casing of the block.
48 54
49 55
The article should firstly contain what the block does.
50 56
51 57
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.
52 58
53
The image of the block is put hereafter.
54
55 59
Then, **Notes** comes next. This should contain all the necessary information about the block, along with its quirks.
56 60
57
The **Example** section comes next. In each example, the description of what the script does comes first before the image.
... ...
\ No newline at end of file
0
The **Example** section comes next. In each example, the description of what the script does comes first before the image.
1
2
### Other
3
4
Other articles may not fit in the category. In this case, proper formatting. When in doubt, you may use the [Chicago Manual of Style](https://en.wikipedia.org/wiki/Title_case#Chicago_Manual_of_Style) for title casing of articles, unless the article title and content is similar to a Q-and-A format (mostly [[Build]] articles, like [[How to create a circle]])
... ...
\ No newline at end of file
Fancade Wiki