1,620
edits
StrategyWiki:Guide/Layout: Difference between revisions
From StrategyWiki, the video game walkthrough and strategy guide wiki
Drivel
m (rm abxy link) |
(Drivel) |
||
| Line 9: | Line 9: | ||
== Text == | == Text == | ||
The text will form the main part of the article, and so it is important that it is laid-out properly. In this respect, good authorship comes into play, with well-written guides being more interesting and engaging to read, and thus being more useful. If you aren't too competent with words, however, don't worry. Just try your best, lay out the article properly, and put <nowiki>{{cleanup}}</nowiki> at the top of the article to signify that it needs cleaning up. | The text will form the main part of the article, and so it is important that it is laid-out properly. In this respect, good authorship comes into play, with well-written guides being more interesting and engaging to read, and thus being more useful. If you aren't too competent with words, however, don't worry. Just try your best, lay out the article properly, and put <nowiki>{{cleanup}}</nowiki> at the top of the article to signify that it needs cleaning up. | ||
One of the key points of laying out text well is the effective use of paragraphs. Separate each idea out, and put them in different paragraphs by splitting them with a double-line-break (i.e. press enter twice after the first paragraph, then write the second). Note that a single line-break won't work: it ''has'' to be a double one. Note also that the splitting of paragraphs doesn't just work for text: other items separated by a double-line-break will also become separate paragraphs, which is sometimes less than desirable, and something to look out for. | One of the key points of laying out text well is the effective use of paragraphs. Separate each idea out, and put them in different paragraphs by splitting them with a double-line-break (i.e. press enter twice after the first paragraph, then write the second). Note that a single line-break won't work: it ''has'' to be a double one. Note also that the splitting of paragraphs doesn't just work for text: other items separated by a double-line-break will also become separate paragraphs, which is sometimes less than desirable, and something to look out for. | ||
=== Drivel === | |||
A further thing to watch out for when writing the text of a guide is drivel. This is extraneous and redundant text which just bores the reader and doesn't help the guide in any way. Examples of drivel would be: | A further thing to watch out for when writing the text of a guide is drivel. This is extraneous and redundant text which just bores the reader and doesn't help the guide in any way. Examples of drivel would be: | ||
* '''Contributor lists''': the history does this | * '''Contributor lists''': the page history does this | ||
* '''Editing guides''': we have a perfectly good [[Help:Contents|help and guidelines]] section | * '''Editing guides''': we have a perfectly good [[Help:Contents|help and guidelines]] section | ||
* '''"What this is/is not"''': again, we have a good guidelines section, and all content relevant to a game should be included in its guide | * '''"What this is/is not"''': again, we have a good guidelines section, and all content relevant to a game should be included in its guide | ||
* '''Overly poetic descriptions/purple prose''': let the game focus on being artistic, the focus of the guide is to help the player | |||
* '''Criticism of the game''': guides are not reviews and should remain neutral on the quality of the game | |||
* '''History lessons''': guides are about the game, not the real world | |||
* '''Comparisons to other games''': they are useless for people who don't know the other game and irrelevant for everyone. | |||
=== Headings === | === Headings === | ||
