guide:style
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| guide:style [2017/03/19 09:06] – [Article Content] wes | guide:style [2018/07/07 14:57] – [Images] wes | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| - **Each section** of an article should generally contain prose **immediately after any section header**. | - **Each section** of an article should generally contain prose **immediately after any section header**. | ||
| - Articles should be internally consistent. | - Articles should be internally consistent. | ||
| - | - Articles of a common type (such as starships or guns) should adhere to the common format (see [[guide: | + | - Articles of a common type (such as starships or guns) should adhere to the common format (see [[: |
| - **Do not use forced line breaks** unless necessary (such as in a table). | - **Do not use forced line breaks** unless necessary (such as in a table). | ||
| Line 32: | Line 32: | ||
| - Leave a space on either side of the title or section heading and a blank line before them. | - Leave a space on either side of the title or section heading and a blank line before them. | ||
| - Headers should be in order: H1 (title) should contain H2 sections, and they should contain H3 sections, etc. | - Headers should be in order: H1 (title) should contain H2 sections, and they should contain H3 sections, etc. | ||
| - | - Ordered lists are preferred to unordered lists. | ||
| ===== Article Content ===== | ===== Article Content ===== | ||
| Line 55: | Line 54: | ||
| ===== Images ===== | ===== Images ===== | ||
| + | As of 7/7/2018 the first image on a wiki article must be an image about the actual subject of the article. Don't use corporate logos, etc, as the first image on the page. This helps with indexing and page previews. | ||
| + | |||
| Please only use file names that make sense and are easily read. Badly named images make images difficult to find, and they make understanding the image difficult or impossible for blind and low-vision roleplayers who have to rely on the text being read to them. | Please only use file names that make sense and are easily read. Badly named images make images difficult to find, and they make understanding the image difficult or impossible for blind and low-vision roleplayers who have to rely on the text being read to them. | ||
guide/style.txt · Last modified: 2023/12/20 18:20 (external edit)