Difference between revisions of "Help:Getting Started"

From UFOpaedia
Jump to navigation Jump to search
(→‎Discussion: A little spelling, added bits about StrategyCore and xcomufo and deletion of discussion pages.)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= Overview =
+
The Getting Started page is here to help existing and budding authors get up and running writing wiki articles. It contains various tips, from general naming convention to formatting tips and tricks that new wiki authors may want to have a go at.  
The getting started page is here to help existing and budding authors get up and running writing wiki articles. For the moment, it'll contain various tips, from general naming convention tips to formatting tips and tricks that new wiki authors may want to have a go at.  
 
  
-----
+
----
See that 'Show preview' button down the bottom of the 'edit' screen? Use it <i>before</i> posting. :)
 
  
Do as I say, not as I do...
+
__TOC__
  
- Bomb Bloke
+
==Starting off==
  
-----
+
The best way to learn how to start creating wiki articles is to click on the 'edit' button and look at the source of a page. Do this to look up how another author was able to achieve a certain effect that you'd like to duplicate.
  
=Starting off=
+
The following [http://meta.wikimedia.org/wiki/Help:Filling_the_page wikimedia] help page is a wealth of wiki text formatting information.
 +
 
 +
==Starting an article==
 +
 
 +
Whenever you follow a link to a page that does not exist, you will be brought to a blank edit box where you can create a new page. Alternately, you can edit the URL in the address bar at the top of the screen and enter the article name after ''title=''.
 +
 
 +
To begin writing a new article, all you need to do is start typing in the text in the edit box, preview your work and the save it.
 +
 
 +
If all you want to do is edit an existing article, each page will have a special edit button at the top of each article. Click on that to edit the respective article. You may also see edit links near sub headings that allow you to edit only part of the page.
 +
 
 +
== Preview button ==
 +
 
 +
Whenever writing or editing an article, make it a firm practice to use the preview button before making any changes to a page. It's a great way of learning how to format a page without doing any damage to existing articles. Still, no worries. The wiki keeps backups of previous edits that you can look up or revert to if you make a mistake.
 +
 
 +
 
 +
==Wikilinks==
 +
 
 +
One of the most important features of wiki articles is the ability to create links that point to other articles. Wikilinks are also an important tool for creating new pages.
 +
 
 +
To create a wikilink, the format is:
 +
 
 +
<nowiki>[[linkname | optional link text]]</nowiki>
 +
 
 +
The pipe and optional link text are optional. The link name is simply the name of the article you want the link to point to.
 +
 
 +
These links can consist of names with spaces. If linking from outside, it is best to use underscores instead of spaces.
 +
 
 +
===Links - watch those plurals!===
  
Until a more comprehensive getting started section is up and running, the best way to learn how to start creating wiki articles is to click on the 'edit' button and look at the source of a page. Do this to look up how another author was able to achieve a certain effect that you'd like to duplicate.  
+
When creating a plural link, watch where your ''s'' goes. It can be a bit confusing and even frustrating at times and can potentially create needless duplication.  
  
The following [http://meta.wikimedia.org/wiki/Help:Filling_the_page wikimedia] help page is a wealth of wiki text formatting information.  
+
Try not to put it inside the link. Instead, have it flush against the link, like so <nowiki>[[Laser Pistol]]s </nowiki>. The wiki knows to make the S part of the link. Or you can use a pipe, like so: <nowiki>[[Laser Pistol | Laser Pistols]] </nowiki> but that's a bit tiresome.
 +
 
 +
Don't use <nowiki>[[Laser Pistols]]</nowiki> unless the actual title is indeed plural.
 +
 
 +
Note that you can use this same basic technique for participles and other suffixes as well in some cases, such as [[manufacture]]d (<nowiki>[[manufacture]]d</nowiki>) for past participle; however, you wouldn't be able to do the same for the present participle in this case (i.e., manufacturing), because of the vowel switch.
 +
 
 +
 
 +
==Basic Text Formatting==
 +
 
 +
Wiki code allows basic HTML markup and cascading style sheets for formatting of its text. The wiki also provides its own markup for formatting text to bold and italics.
 +
 
 +
To achieve either, surround the text with a series of single quotation marks. Three for bold, and two for italic. For example: <nowiki> '''Bold Text''' and ''Italic'' </nowiki>
 +
 
 +
Produces:
 +
 
 +
'''Bold Text''' and ''Italic''
  
Also do as [[User:Bomb Bloke | Bomb Bloke]] says, use the preview button. It's a great way of learning how to format a page without doing any damage to existing articles. Still, no worries. The wiki keeps backups of previous edits that you can look up in case you deleted by mistake.  
+
You can also highlight the text you want set to bold or italics and hit the bold or italic buttons at the top of the wiki edit box to achieve the same effect.  
  
- [[User:NKF|NKF]]
+
To combine bold and italic you will need to use a combination of wiki markup and HTML or CSS markup.
  
= Tips =
 
 
==HTML and CSS in wiki text==
 
==HTML and CSS in wiki text==
  
Line 32: Line 71:
 
</table>
 
</table>
  
Wiki text allows some HTML to be used. Not all of it, but enough of the basics. For example, you may want to use a lot of whitespace in your text, but wiki text may eats most of your whitespace. This happens a lot when creating a quick list of items. Without resorting to creating an un-numbered wiki list, you can use a few HTML line break &lt;BR&gt; to force a few carriage returns.
+
Wiki text allows some HTML markup to be used. Not all of it, but enough to allow text formatting, paragraph formatting, preformatted text, Div and Span, and HTML tables.  
  
If all else fails, rather than pressing enter once after each list item, press enter twice.
+
For example, the use of the &lt;BR&rt; line break tag. You may want to use a lot of whitespace in your text, but the wiki removes most of the whitespace once it converts the code into the finished article. This happens a lot when creating a quick list of items. Without resorting to creating an un-numbered wiki list, you can use a few &lt;BR&gt; tags to force a few carriage returns.
 
 
The Wiki also allows Cascading Style Sheet elements to be included into Wiki text for the purpose of formatting.  
 
  
 
For a list of references, you can try [http://www.htmlhelp.com/reference/css/references.html WDG's CSS reference].  
 
For a list of references, you can try [http://www.htmlhelp.com/reference/css/references.html WDG's CSS reference].  
  
==Watch those leading spaces==
+
==Creating lists==
  
If you ever place a space at the start of a new line, the following happens:
+
The wiki provides an easy way to create unnumbered or numbered lists.
  
See this box? This is the result. It contains unformatted wiki text.
+
The unnumbered list is created by entering an asterisk * at the start of each line.  
You '''can''' include formatting elements in it.
 
Nothing's terribly wrong With it except that if your screen is too small, it can go off the page if the line of text is too long. See what I mean?
 
Note, this mimics the HTML &lt;PRE&gt; tag, which works on blocks of text rather than single lines. 
 
 
(You may need to scroll the page to right to see the rest of the last line)
 
  
== Section Headings ==
+
<pre><nowiki>
 +
*One
 +
*Two
 +
*Three
 +
</nowiki></pre>
  
Section headings divide your articles into, well, sections. To create a section heading, go to a new line and surround the title of your new section with equal signs. Like so:  
+
Produces:  
  
= <em>section name</em> =
+
*One
 +
*Two
 +
*Three
  
A section heading takes up a whole line, has the title bolded and a horizontal line is created underneath it. Also, all sections on a page are inserted into the current page's table of contents - assuming the table of contents for the page has not been disabled, and there are enough sections to justify a table of contents (basically, four).
+
You can create several levels of lists by increasing the number of asterisks on each line.
  
Section headings have various levels. The different levels are distinguished by the number of equal signs that you surround the title with. Level one uses one equal sign on either side of the title. Level two uses two equal signs.
+
*one
 +
**sub one
 +
***sub sub one
 +
*two
 +
*three
  
Level 1 is treated as the topmost heading. All other headings are treated as sub-headings. Look at the source for this page by clicking on the edit button to see title headings in action.
 
  
=== Section headings as bookmarks ===
+
A numbered list is created in the same way by entering a hash (#) instead of an asterisk. As long as the list is continuous without any line breaks the list will number itself accordingly. If there are any line breaks, the numbering is reset accordingly.  
Section headings can also act like bookmarks, in a way. They allow you to link directly to particular sections in a page from other pages as well. To do this, create a wiki link as usual, but place a sharp/hash after the link name and then followed by the section heading.  
 
  
For example, to link to the ''Maximum Caps'' section in [[Firing Accuracy]], we'd write:
+
#one
 +
#two
 +
#three
  
<nowiki>[[Firing Accuracy#Maximum Caps | Firing Accuracy ]]</nowiki>
+
And a multi-level numbered list combined with unnumbered list:
  
: [[Firing Accuracy#Maximum Caps | Test it!]]
+
#one
 +
##sub one - first
 +
##sub one - second
 +
##*sub one - second list item 1
 +
##*sub one - second list item 2
 +
##*sub one - second list item 3
 +
##sub one - third
 +
#two
 +
#three
  
You'll find that going to the page will jump you right to ''Maximum Caps''.
 
  
To create internal bookmarks, leave off the name of the page you want to link to. For example, to jump to the Tips section on this page, the following can be used:
+
==Watch those leading spaces==
<nowiki>[[#Tips | Jump to the top of this section ]]</nowiki>
 
  
One good example of this in action:  
+
If you ever place a space at the start of a new line, the following happens:
  
<em title = "This is an example of the above code in action"><small>([[#Tips | Jump to the top of this section ]])</small></em>
+
See this box? This is the result. It contains unformatted wiki text.
 +
You '''can''' include formatting elements in it.
 +
Nothing's terribly wrong with it except that if your screen is too small, such as 800x600, this box may very well go off the page if the line of text is too long.
 +
Note, this mimics the HTML &lt;PRE&gt; tag, which works on blocks of text rather than single lines. 
 +
 +
(You may need to scroll the page to right to see the rest of the last line)
  
Use this feature sparingly - if someone renames the heading on a page not knowing you have linked to it, your link will break and just go to the top of the page as if there was no section bookmark. There is no way to tell when changing a section if there are links to it apart from checking every link to the page in turn, so it reduces maintainability to use these sorts of links too liberally.
+
Unless you're writing short bits of program code, try to avoid unformatted text boxes such as this.  
  
==Links - watch those plurals!==
+
== Section headings ==
  
When creating a plural link, watch where your ''s'' goes. It can be a bit confusing and even frustrating at times and can potentially create needless duplication.  
+
Section headings divide your articles into manageable sections. A section heading produces a line of text that takes up a whole line, has the title bolded and a horizontal line is created underneath it. Some variances may appear depending on the style sheets used for the forum skin (see your account preferences).  
  
Try not to put it inside the link. Instead, have it flush against the link, like so <nowiki>[[Laser Pistol]]s </nowiki>. The wiki knows to make the S part of the link. Or you can use a pipe, like so: <nowiki>[[Laser Pistol | Laser Pistols]] </nowiki> but that's a bit tiresome.
+
To create a section heading, go to a new line and surround the title of your new section with equal signs. For the example, this section heading was achieved with the following line of code:
  
Don't use <nowiki>[[Laser Pistols]]</nowiki> unless the actual title is indeed plural.
+
<nowiki>== Section headings ==</nowiki>
  
Note that you can use this same basic technique for participles and other suffixes as well in some cases, such as [[manufacture]]d (<nowiki>[[manufacture]]d</nowiki>) for past participle, however you wouldnt be able to do the same for the present participle in this case (i.e., manufacturing), because of the vowel switch.
+
Section headings have various levels. The different levels are distinguished by the number of equal signs that you surround the title with. Level one uses one equal sign on either side of the title. Level two uses two equal signs. Level 3 has three equals signs, etc.
  
==Stub Pages==
+
Level 1 is treated as the topmost heading. All other headings are treated as sub-headings. The most common section heading level that you will use is level 2.
  
 +
All sections on a page are inserted into the current page's table of contents - assuming the table of contents for the page has not been disabled, and there are enough sections to justify a table of contents. This is commonly 4 headings, but may vary depending on your viewing preferences.
  
Stub pages are simply placeholder pages that contain little to no information that will later be turned into a full article, or even a redirection page.
 
  
For existing authors, try not to litter the wiki with lots of little stub pages that you'll probably abandon through neglect or you've suddenly decided to go for a better document title. Only create stub pages when you know you'll be using them and try not to fill them with unhelpful comments like ''"The banana peel bomb. Uh, yeah. it's really powerful. Blast the aliens to bits tod days beyond tuesday."'' and leave it at that.
+
=== Section headings as bookmarks ===
 +
 +
Section headings can also act like bookmarks, in a way. They allow you to link directly to particular sections in a page from other pages as well. To do this, create a wiki link as usual, but place a sharp/hash (#) after the link name and then followed by the section heading you want the link to jump to.  
  
<div align = "center">
+
For example, to link to the ''Maximum Caps'' section in [[Firing Accuracy]], we'd write:
<table style = "background: #FFFFFF; border: 1px red solid; border-style:dashed; width: 60%; margin: 1em 1em 1em 1em; padding:4px;">
 
<tr>
 
<td>
 
; Tip : If you have several unwanted stub pages, one excellent way of making sure that they don't go to waste is to move/rename them into the name of an article that has not yet been created, then fill in the page from there.
 
</td>
 
</tr>
 
</table>
 
</div>
 
<br>
 
===When creating Stub Pages===
 
  
If you are creating a stub pages and can't think of anything to say, consider entering the following line:
+
<nowiki>[[Firing Accuracy#Maximum Caps | Firing Accuracy]]</nowiki>
  
<pre><nowiki> {{STUB}} </nowiki></pre>
+
Test it: [[Firing Accuracy#Maximum Caps | Firing Accuracy]]
  
This makes use of MediaWiki's fascinating feature called transclusion (fills a page with another one) to insert the following message onto the page:
+
You'll find that going to the page will jump you right to ''Maximum Caps''.
  
{{STUB}}
+
To create internal bookmarks within an article, leave off the name of the page and go straight to the hash. For example, to jump to the Tips section on this page, the following can be used:
 +
<nowiki>[[#Section Headings | Jump to Section Headings ]]</nowiki>
  
Which is marginally better than leaving it blank.
+
One good example of this in action:
  
====Picture Stubs====
+
<em title = "This is an example of the above code in action"><small>([[# Section Headings  | Jump to Section Headings]])</small></em>
Want someone to upload an image for a particular article? Simply add the following line:
 
  
<pre><nowiki> {{PicStub}} </nowiki></pre>
+
Use this feature sparingly - if someone renames the heading on a page not knowing you have linked to it, your link will break and just go to the top of the page as if there was no section bookmark. There is no way to tell when changing a section if there are links to it apart from checking every link to the page in turn, so it reduces maintainability to use these sorts of links too liberally.
 
 
Again, this works on the principal of transclusion and inserts this block to the right:
 
 
 
{{PicStub}}
 
  
To see a list of pages which need images go [[Special:Whatlinkshere/Template:PicStub|here]].
+
==Stub pages==
  
Both of these stubs are site-wide messages. <br clear="all">
+
Since they were only used at the inception of the wiki, stub pages are now rarely used. They have been deprecated in favour of empty pages. Any links to pages that do not exist will populate the [[Special:WantedPages]] page.
  
 
==Discussion==
 
==Discussion==
  
First and foremost, the wiki is not designed to be a discussion forum. But where needs arise, some discussion will have to take place on the wiki, as not all visitors will be members of the various forums the regular authors frequent. We urge you to become members of the two largest X-COM forums ([http://www.strategycore.co.uk/forums/ StrategyCore] and [http://www.xcomufo.com/forums/ Xcomufo.com]) though, as you will be able to reply to existing discussions and start new ones too. A lot of information still resides in these forums and needs to be included in this wiki, and in order to read some of the subforums registering is necessary.
+
First and foremost, the wiki is not designed to be a discussion forum. But where needs arise, some discussion will have to take place on the wiki, as not all visitors will be members of the various forums the regular authors frequent.  
  
There's a discussion link at the top of each Wiki page. If you have a comment or are unsure and want to ask a question, the discussion page is the best place to do it. If you find yourself having a frequent or a long discussion with another author in an existing article, consider moving to the discussion page to iron out all the details and then edit the main page to reflect the discussion. It's a lot better that having important ideas being lost in the multitude of text.  
+
There's a discussion link at the top of each Wiki page. Also accessible with the ''atl+shift+t'' shortcut. If you have a comment or are unsure and want to ask a question, the discussion page is the best place to do it. Do not have the discussion in the actual article.  
  
Remember to use the + button at the top of the discussion page to add comments rather than using the 'edit' button (unless it's the very first comment). Also remember to enter a brief discussion heading (there will be a separate text box above the edit box for this) so that your new discussion topic stands out rather than ending up flush against the previous comment.  
+
The discussion pages are like blackboards. Remember to wipe them clean after you're done and all the changes are in effect. Empty, really old or useless discussions are wiped (deleted) on a semi-regular basis by the sysops as they are noticed.
  
The discussion pages are like black boards. Remember to wipe them clean after you're done and all the changes are in effect. Empty, really old or useless discussions are wiped (deleted) on a semi-regular basis by the sysops as they are noticed.
+
If for whatever reason you want to keep the discussion off the wiki, such as if you're having a long and detailed discussion and this is cluttering the recent changes page, consider moving the discussion to an actual web forum. Either at the [http://www.strategycore.co.uk/forums/UFOPaediaorg-f96.html Ufopaedia official forum], or a variety of other X-COM related forums around the world, which can be accessed from the [[Forums]] page.  
  
 
===Discussion : Separating ===
 
===Discussion : Separating ===
 +
 
In a Talk: page, remember to separate any posts that you make so that your post doesn't end up looking like a continuation from the previous post. You have a wide variety of methods available to separate your posts.  
 
In a Talk: page, remember to separate any posts that you make so that your post doesn't end up looking like a continuation from the previous post. You have a wide variety of methods available to separate your posts.  
  
If you use the + button to add your message, entering a title in the title textbox will automatically enter a section heading. See the [[#Section Headings |section heading]] for more information on how to enter section headings manually.  
+
If you use the +/add topic button to add your message, entering a title in the title textbox will automatically enter a section heading. See the [[#Section Headings |section heading]] for more information on how to enter section headings manually.  
  
You can also use horizontal lines. To create a horizontal line, enter five dashes (<nowiki>-----</nowiki>). To demonstrate:  
+
You can also use horizontal lines to break up different lines of discussion. To create a horizontal line, enter four dashes (<nowiki>----</nowiki>). To demonstrate:  
  
-----
+
----
  
 
Lines are automatically inserted whenever a section heading is created, but sometimes a simple line is all you need.
 
Lines are automatically inserted whenever a section heading is created, but sometimes a simple line is all you need.
  
== Signing Off ==  
+
== Signing off ==  
If you're a registered user of this wiki board, sometimes you will want to leave a link back to your user page - if you have one. The Wiki has a shortcut that allows you to do this without having to type the entire link to your user page manually.  
+
 
 +
Whenever you add a message to any discussion, it is good practice to sign off your messages so that other authors know who left it is from.  
  
 
There are two ways of doing this. The first version is done by simply entering <nowiki>~~~</nowiki>. This creates a link directly back to your user page and pipes the link to your user name.  
 
There are two ways of doing this. The first version is done by simply entering <nowiki>~~~</nowiki>. This creates a link directly back to your user page and pipes the link to your user name.  
  
The other version uses four tildes (<nowiki>~~~~</nowiki>). This does exactly the same as the there tilde shortcut, but it also appends the current date and time onto your piped user name. This is great way of time stamping any personal comments or discussions in talk pages, and it makes it much easier to follow a discussion on the talk page if you can tell who is saying what.  
+
The other version uses four tildes (<nowiki>~~~~</nowiki>). This does exactly the same as the last shortcut, but it also appends the current date and time onto your piped user name. This is the preferred method of signing your name.  
  
This shortcut will only take effect on the articles source when you finally save the document, however you will see the desired effect when previewing.
+
This shortcut will only take effect on the articles source when you finally save the document; however, you will see the desired effect when previewing the page.
  
 
== Indenting ==
 
== Indenting ==
The purpose of this section is to describe indenting. A line of indented text probably doesn't look like much, but it can certainly allow sections of large blocks of text to stand out a bit.
+
 
 +
One other tool in article creation as well as for organizing discussions in a talk page is the use of indents
  
 
: To indent a line, observe the following line.  
 
: To indent a line, observe the following line.  
Line 173: Line 217:
  
 
: Notice how there's a colon at the start of the line. This indents the entire line of text. Note that this only works on the one line.  
 
: Notice how there's a colon at the start of the line. This indents the entire line of text. Note that this only works on the one line.  
 
 
All text after the carriage return (the invisible character representing the enter/return key) will return to normal. Just like what has happened to this line, if you have a look at the source code. If you want to indent a large document, remember to place a ":" at the beginning of each new paragraph.  
 
All text after the carriage return (the invisible character representing the enter/return key) will return to normal. Just like what has happened to this line, if you have a look at the source code. If you want to indent a large document, remember to place a ":" at the beginning of each new paragraph.  
  
Line 182: Line 225:
 
:: It helps break up the large blocks of unweildy text
 
:: It helps break up the large blocks of unweildy text
 
::::::::::::::::::: <em><small>Fnord!</small></em>  
 
::::::::::::::::::: <em><small>Fnord!</small></em>  
:: How now brown cow? Where is my cow?
+
::: It has absconded with the kitchen sink
+
Combined with horizontal bars, indenting is a useful tool for discussion pages.
:::: A life on the run for one that befriends a cat with boots is a sad one indeed.
 
:: Mind you
 
: This is taking things to the extreme
 
And is just causing one big horrible mess.
 
: But it'll hopefully get the point across
 
 
 
Be advised that if you place a semicolon ";" instead of a colon at the start of a new paragraph, it converts the entire paragraph into bold text. This can be a really handy way of making quick minor sub headings. If you place a ":" right after the title, separated by a space, you'll get a heading and an indented pargraph. This is useful for definitions. For example:
 
 
 
<nowiki>; This is the topic being explained : This is the description</nowiki>
 
 
 
Produces:
 
 
 
; This is the topic being explained : This is the description
 
 
 
In this case, only one level of indent seems to work for the description, but you can indeed indent the entire definition, for example,
 
 
 
<pre>::; Indented Topic : Indented Topic description</pre>
 
 
 
Would produce: 
 
 
 
::; Indented Topic : Indented Topic description
 

Latest revision as of 02:29, 4 December 2019

The Getting Started page is here to help existing and budding authors get up and running writing wiki articles. It contains various tips, from general naming convention to formatting tips and tricks that new wiki authors may want to have a go at.


Starting off

The best way to learn how to start creating wiki articles is to click on the 'edit' button and look at the source of a page. Do this to look up how another author was able to achieve a certain effect that you'd like to duplicate.

The following wikimedia help page is a wealth of wiki text formatting information.

Starting an article

Whenever you follow a link to a page that does not exist, you will be brought to a blank edit box where you can create a new page. Alternately, you can edit the URL in the address bar at the top of the screen and enter the article name after title=.

To begin writing a new article, all you need to do is start typing in the text in the edit box, preview your work and the save it.

If all you want to do is edit an existing article, each page will have a special edit button at the top of each article. Click on that to edit the respective article. You may also see edit links near sub headings that allow you to edit only part of the page.

Preview button

Whenever writing or editing an article, make it a firm practice to use the preview button before making any changes to a page. It's a great way of learning how to format a page without doing any damage to existing articles. Still, no worries. The wiki keeps backups of previous edits that you can look up or revert to if you make a mistake.


Wikilinks

One of the most important features of wiki articles is the ability to create links that point to other articles. Wikilinks are also an important tool for creating new pages.

To create a wikilink, the format is:

[[linkname | optional link text]]

The pipe and optional link text are optional. The link name is simply the name of the article you want the link to point to.

These links can consist of names with spaces. If linking from outside, it is best to use underscores instead of spaces.

Links - watch those plurals!

When creating a plural link, watch where your s goes. It can be a bit confusing and even frustrating at times and can potentially create needless duplication.

Try not to put it inside the link. Instead, have it flush against the link, like so [[Laser Pistol]]s . The wiki knows to make the S part of the link. Or you can use a pipe, like so: [[Laser Pistol | Laser Pistols]] but that's a bit tiresome.

Don't use [[Laser Pistols]] unless the actual title is indeed plural.

Note that you can use this same basic technique for participles and other suffixes as well in some cases, such as manufactured ([[manufacture]]d) for past participle; however, you wouldn't be able to do the same for the present participle in this case (i.e., manufacturing), because of the vowel switch.


Basic Text Formatting

Wiki code allows basic HTML markup and cascading style sheets for formatting of its text. The wiki also provides its own markup for formatting text to bold and italics.

To achieve either, surround the text with a series of single quotation marks. Three for bold, and two for italic. For example: '''Bold Text''' and ''Italic''

Produces:

Bold Text and Italic

You can also highlight the text you want set to bold or italics and hit the bold or italic buttons at the top of the wiki edit box to achieve the same effect.

To combine bold and italic you will need to use a combination of wiki markup and HTML or CSS markup.

HTML and CSS in wiki text

Example
Here's an sample of a standard html table with CSS used to supply the aesthetic formatting. If you can't see this text surrounded by a purple right-aligned box, then your browser may not support CSS.

Wiki text allows some HTML markup to be used. Not all of it, but enough to allow text formatting, paragraph formatting, preformatted text, Div and Span, and HTML tables.

For example, the use of the <BR&rt; line break tag. You may want to use a lot of whitespace in your text, but the wiki removes most of the whitespace once it converts the code into the finished article. This happens a lot when creating a quick list of items. Without resorting to creating an un-numbered wiki list, you can use a few <BR> tags to force a few carriage returns.

For a list of references, you can try WDG's CSS reference.

Creating lists

The wiki provides an easy way to create unnumbered or numbered lists.

The unnumbered list is created by entering an asterisk * at the start of each line.

*One
*Two
*Three

Produces:

  • One
  • Two
  • Three

You can create several levels of lists by increasing the number of asterisks on each line.

  • one
    • sub one
      • sub sub one
  • two
  • three


A numbered list is created in the same way by entering a hash (#) instead of an asterisk. As long as the list is continuous without any line breaks the list will number itself accordingly. If there are any line breaks, the numbering is reset accordingly.

  1. one
  2. two
  3. three

And a multi-level numbered list combined with unnumbered list:

  1. one
    1. sub one - first
    2. sub one - second
      • sub one - second list item 1
      • sub one - second list item 2
      • sub one - second list item 3
    3. sub one - third
  2. two
  3. three


Watch those leading spaces

If you ever place a space at the start of a new line, the following happens:

See this box? This is the result. It contains unformatted wiki text. 
You can include formatting elements in it. 
Nothing's terribly wrong with it except that if your screen is too small, such as 800x600, this box may very well go off the page if the line of text is too long. 
Note, this mimics the HTML <PRE> tag, which works on blocks of text rather than single lines.  

(You may need to scroll the page to right to see the rest of the last line)

Unless you're writing short bits of program code, try to avoid unformatted text boxes such as this.

Section headings

Section headings divide your articles into manageable sections. A section heading produces a line of text that takes up a whole line, has the title bolded and a horizontal line is created underneath it. Some variances may appear depending on the style sheets used for the forum skin (see your account preferences).

To create a section heading, go to a new line and surround the title of your new section with equal signs. For the example, this section heading was achieved with the following line of code:

== Section headings ==

Section headings have various levels. The different levels are distinguished by the number of equal signs that you surround the title with. Level one uses one equal sign on either side of the title. Level two uses two equal signs. Level 3 has three equals signs, etc.

Level 1 is treated as the topmost heading. All other headings are treated as sub-headings. The most common section heading level that you will use is level 2.

All sections on a page are inserted into the current page's table of contents - assuming the table of contents for the page has not been disabled, and there are enough sections to justify a table of contents. This is commonly 4 headings, but may vary depending on your viewing preferences.


Section headings as bookmarks

Section headings can also act like bookmarks, in a way. They allow you to link directly to particular sections in a page from other pages as well. To do this, create a wiki link as usual, but place a sharp/hash (#) after the link name and then followed by the section heading you want the link to jump to.

For example, to link to the Maximum Caps section in Firing Accuracy, we'd write:

[[Firing Accuracy#Maximum Caps | Firing Accuracy]] 

Test it: Firing Accuracy

You'll find that going to the page will jump you right to Maximum Caps.

To create internal bookmarks within an article, leave off the name of the page and go straight to the hash. For example, to jump to the Tips section on this page, the following can be used:

[[#Section Headings | Jump to Section Headings ]]

One good example of this in action:

( Jump to Section Headings)

Use this feature sparingly - if someone renames the heading on a page not knowing you have linked to it, your link will break and just go to the top of the page as if there was no section bookmark. There is no way to tell when changing a section if there are links to it apart from checking every link to the page in turn, so it reduces maintainability to use these sorts of links too liberally.

Stub pages

Since they were only used at the inception of the wiki, stub pages are now rarely used. They have been deprecated in favour of empty pages. Any links to pages that do not exist will populate the Special:WantedPages page.

Discussion

First and foremost, the wiki is not designed to be a discussion forum. But where needs arise, some discussion will have to take place on the wiki, as not all visitors will be members of the various forums the regular authors frequent.

There's a discussion link at the top of each Wiki page. Also accessible with the atl+shift+t shortcut. If you have a comment or are unsure and want to ask a question, the discussion page is the best place to do it. Do not have the discussion in the actual article.

The discussion pages are like blackboards. Remember to wipe them clean after you're done and all the changes are in effect. Empty, really old or useless discussions are wiped (deleted) on a semi-regular basis by the sysops as they are noticed.

If for whatever reason you want to keep the discussion off the wiki, such as if you're having a long and detailed discussion and this is cluttering the recent changes page, consider moving the discussion to an actual web forum. Either at the Ufopaedia official forum, or a variety of other X-COM related forums around the world, which can be accessed from the Forums page.

Discussion : Separating

In a Talk: page, remember to separate any posts that you make so that your post doesn't end up looking like a continuation from the previous post. You have a wide variety of methods available to separate your posts.

If you use the +/add topic button to add your message, entering a title in the title textbox will automatically enter a section heading. See the section heading for more information on how to enter section headings manually.

You can also use horizontal lines to break up different lines of discussion. To create a horizontal line, enter four dashes (----). To demonstrate:


Lines are automatically inserted whenever a section heading is created, but sometimes a simple line is all you need.

Signing off

Whenever you add a message to any discussion, it is good practice to sign off your messages so that other authors know who left it is from.

There are two ways of doing this. The first version is done by simply entering ~~~. This creates a link directly back to your user page and pipes the link to your user name.

The other version uses four tildes (~~~~). This does exactly the same as the last shortcut, but it also appends the current date and time onto your piped user name. This is the preferred method of signing your name.

This shortcut will only take effect on the articles source when you finally save the document; however, you will see the desired effect when previewing the page.

Indenting

One other tool in article creation as well as for organizing discussions in a talk page is the use of indents

To indent a line, observe the following line.
: To indent a line, observe the following line. 
Notice how there's a colon at the start of the line. This indents the entire line of text. Note that this only works on the one line.

All text after the carriage return (the invisible character representing the enter/return key) will return to normal. Just like what has happened to this line, if you have a look at the source code. If you want to indent a large document, remember to place a ":" at the beginning of each new paragraph.

You can have multiple indent levels!
Observe.
See?
This can be handy for breaking up user discussions into threads
It helps break up the large blocks of unweildy text
Fnord!

Combined with horizontal bars, indenting is a useful tool for discussion pages.