User:Cephalon Scientia/Test6

=How to Effectively Contribute to this Wiki - A Comprehensive Introduction=

Introduction
Hello there! As a long-time contributor to this wiki, I see a lot of places where the wiki could be improved on, particularly in the lore department. That is where you can come in! The purpose of this blog is to introduce some of the basics of the Wiki Markup Language to get more users to effectively contribute to the growing state of this wiki. No 'coding' experience needed! As menacing as it looks when you first click the edit button of an article, understanding the meaning of some markup text goes a long way in building the confidence needed to conquer the foreign landscape behind the everyday articles we use.

Take this blog post as an informal tutorial on how to navigate through the editing page of an article. For more information on wiki formatting, please see the bottom of the page for additional resources.

Feel free to hit edit on any section of this blog post to see how the wiki markup is used.

Terminology

 * Anything enclosed in triangle brackets < > are known as HTML tags.
 * Escaping refers to text not being recognized as wiki markup.
 * Calling refers to the usage of curly brackets  to reference a template or module that returns an output. (e.g. calling a navbox using  )

Wiki Markup Basics
Markup code is what makes wikis wikis. It formats text in a way that gives wikis their distinct style. They are not displayed on the actual articles, but, instead, you will see the formatted text resulting from those markup codes. The following markup code is shown in the order of most to least common occurrence to a Wiki Contributor.

Section Headers
Section headers are denoted by equal signs that sandwich between a word or phrase as such:

=Header 1=

The more equal signs that sandwich between a phrase, the higher the level of the header text:

Header 6
There are no more header levels beyond 6.

Level 1 headers are never used explicitly because those are reserved for article titles. Normally, you will use level 2 headers for dividing the article into sections. Each subsequent level of headers will be more rarely seen and are used in very specific situations. If the table of contents is enabled for that page, section headers will appear in it to easily navigate through the page.

See It In Action

 * Weapons

Linking Articles
To put a link to other articles in the same wiki, sandwich the name of the article with square brackets as so:

Article Name

You can rename article links by adding a vertical bar  followed by the new name as follows:

New Name

Linking Sections of Articles
Insert a pound symbol  following the article name.

Article Name

Linking Subpages of Articles
Insert a slash  following the article name.

Article Name/Subpage Name

See It In Action

 * Riven Mods

Calling Files from the Wiki
Files are images and videos that are uploaded to the wiki to be used in articles. They called in a manner similar to inserting a link to another article:



See It In Action

 * Maneuvers

Lists
Lists are created using bulleted text, denoted by an asterisk in front of the text:

*Item

The more asterisks a text has, the more levels into the bulleted list it is in:


 * Sub-item


 * Sub-sub-item


 * Sub-sub-sub-item

...and etc.

You can make lists to have as many sub-items as you want. Typically, lists on this wiki will have at most 3 levels of items (three asterisks). Do not leave blank spaces in-between items of the same list, otherwise, a new list will be created for you.

Numbered Lists
Numbered lists are formed from pound symbols (#). These are rarely used on the wiki.


 * 1) Step 1


 * 1) Step 1.1


 * 1) Step 1.2


 * 1) Step 1.2.1


 * 1) Step 2

...and etc.

Description Lists
Description lists are a subtype of lists that combines the use of semicolons and colons  in order to list out terms and their descriptions. In the context of this wiki, semicolons are commonly used in patch histories to denote titles while colons are rarely used. Using semicolon boldens the text following it and colons indent the text following it.


 * 1) Term


 * Description 1


 * Description 2


 * Description 3

...and etc.

See It In Action

 * Any weapon page like.
 * Any patch history like Survival.

Bold
To bolden a piece of text, sandwich it with three apostrophes:

Text

Italics
To italicize a piece of text, sandwich it with two apostrophes:

Text

Breaks and Non-Breaking Spaces
Break tags are used to separate two pieces of text explicitly:

or

When you hit enter within the editing page, you are essentially putting an invisible break tag in the text. To force a line break in a text, type in a break tag. The reason why you would use break tags rather than hitting enter is because of markup code formatting in the editing page. Sometimes adding breaks makes it more visually appealing and easier for users to edit a page.

On the contrary, to prevent two words from having a line break between them when there would normally be one, type in special character for a non-breaking space:

&amp;nbsp;

Comments
Comments are text that not explicitly displayed in the article. They serve as a way for users to point out specific usage of some of the more complex markup code or as a way to hide certain text. To make a text comment, sandwich it with  as follows:

Special Characters
Special characters are denoted with an ampersand symbol (&) and end with a semicolon. A common special character you will encounter (albeit rarely) will be the non-breaking space:

&amp;nbsp;

Escaping Wiki Markup
Wondering how I have been able to display markup code in the article even though I said otherwise? Well,  tags make it so that any markup code is shown as if they are normal text:

Markup Code< / pre>

However,  tags stand for "preformatted text" so what you see is what the markup code looks like as if you are in the editing page. If you want to display markup code without the gray boxes behind it, put in the  tags between the text:

Markup Code 

See It In Action

 * Commonly used in documentation for templates and modules like Template:Icon.

Combining Markup Codes
Markup codes can be combined to produce complex formatting. For example, you can have bold and italicized text like so:

Text

Order markup code in the order that you want the text to be presented as.

HTML Formatting With CSS Styling Basics
Wiki Markup Language also allows the use of HTML tags for formatting and CSS for styling text. Here are some features of the wiki that utilize this.

Div Tags (Division)
Text between div tags can be stylized using CSS. Text

Text

Text

See It In Action

 * Pages with tables or collapsibles like [[

Common HTML Classes on Wiki
tabbertab-borderless

Galleries
Picture galleries can be created by inputting the file names in the order you want them to be displayed between gallery tags as such:

Galleries are usually placed under "Media" headers.

See It In Action

 * Any enemy page like Bombards.

Templates
Templates are special pages that can have its content displayed in other pages. These help better organize information for wiki users and/or improve navigation through the wiki.

Examples of templates include navigation boxes such as Template:NeutralNav:

Or infoboxes like Template:Enemy:

Or message boxes like :

Calling Templates
Templates can be called by adding curly brackets around the template name like so:

By convention, template names don't have spaces in between words. Instead, each new word starts with a capital letter to differentiate words. For more details see this Wikipedia article.

Using Templates
Each template has a different way of using them so be sure to consult its documentation page to ensure that you are calling it correctly (or be like me and copy and paste the template from another article and learn from trial & error). To find its documentation, go to the template's page by searching  in the wiki search bar or type in   at the end of the URL:

In the occasion where a template does not have documentation associated with it, it most likely inherits the properties of a more general template, like in the case of navboxes like Template:CorpusNav which inherits the properties of Template:Navbox.

Some templates are simple in their usage. Just calling them does the job. However, others may require extra user input like Template:ModBox where you need to fill out specific parameters. You may get script errors after calling a template. To fix this, fill in all the needed parameters for the template to work.

Warframe Wikia Specific Templates
The following templates are made by Warframe Wikia contributors and are commonly used throughout the wiki:

- for icons such as status procs

- for text links to Warframes with a tooltip

- for text links to Warframe abilities with a tooltip

- for text links to mods with a tooltip (no Riven Mods)

- for text links to weapons with a tooltip

- for button keys (PC, Xbox, and PS4 - no Nintendo Switch yet)

- for quoted text

& - for hidable content

"This is a quoted text. Notice how the text inside the template call is stylized without using double apostrophes or line break tags. The quote template automatically does this for you."

- Me "This is a quoted text. Notice how the text inside the template call is stylized without using double apostrophes or line break tags. The quote template automatically does this for you."

- Me

Hello there.

Hello there.

Message Boxes
Message boxes are templates that are usually placed at the top of a page to alert users about a particular thing about the article. Here are some of the common ones:

- tells users that the article needs to be updated

- tells users that the article needs to have more info added

- tells users that there are spoilers in the article

Other Useful Templates
- prevents text wrapping

- citation needed for information

& - forces the table of contents to align right or left

Calling Modules
Modules are advanced versions of templates and are called the same way:

Tables
Tables are used to organize information in an orderly manner for easy digestability.

Conclusion
Hopefully, this blog post helps alleviate any confusion and clarifies how one edits articles. There are a lot of details that I purposefully missed because they are not commonly implemented in this wiki (examples include numbered lists, blockquotes, indentation, etc). If you have any comments or questions, please feel free to leave a reply or contact me. Editing the wiki is not a one-person project, so I encourage everyone to lift each other together!

Additional Resources

 * https://en.wikipedia.org/wiki/Help:Wikitext, for more comprehensive documentation of all the features of Wiki markup
 * https://www.mediawiki.org/wiki/Help:Formatting
 * https://www.w3schools.com/html/default.asp, for HTML reference
 * https://www.w3schools.com/css/default.asp, for CSS reference
 * WARFRAME Wiki:Styling Guide


 * Last updated: 6/26/19