The following article is part of WARFRAME Wiki's policy.
For any inquiries, please consult an Administrator or Moderator.

This article consist of style guidelines to follow when editing or creating new pages for the WARFRAME Wiki. All editors are expected to agree and follow this guide when editing in order to ensure content consistency and quality in all of the WARFRAME Wiki's articles.

If you are new to editing wikis, you can visit Wikipedia's introduction to wikitext for a quick tutorial.

Last updated: Tue, 10 Jan 2023 22:49:36 +0000 (UTC) by User:Cephalon Scientia

General Guidelines

  • Try to use a simple register as you write. People from all around the world are probably going to read this wiki, and their first language is not always English. Do not use colloquialisms.
  • Try to be as impersonal as possible. Remember you are giving out information, not your own point of view. Refrain from writing biased walls of text about your experience with something in the article, do that in blogs or in the comment section at the bottom of the page instead.
  • Humor in the content section is strongly discouraged. Avoid being funny or witty as you write, people are here for pieces of information, not for a laugh.
  • Avoid inserting unconfirmed content or any speculations. If an unconfirmed content is significant that it has to be shown to the public for further testing, please state so clearly by adding {{Cite}} next to the text, or {{Speculation}} to the section.
  • Avoid referencing other video games or media. This wiki is for WARFRAME and WARFRAME only. An exception to this rule is the Real-World References page and possibly Trivia sections if there is undoubtedly a clear and intentional reference to another piece of media (speculations and similarities do not count).
  • Link words to articles. If a word in an article has its own page, link it to the page. However, that page should not be linked more than once in a particular section of the page; over-linking a page is unnecessary if the linked page can be viewed at least once on a single section.
  • Be professional. Use formal writing rules. The use of contractions is discouraged, but not forbidden. Strive for formal sentence structure, but don't avoid contractions if it creates clunky or unnatural flow (e.g. the use of "don't" vs "do not" in this sentence).
  • Feel free to correct spelling/grammar mistakes and help expanding Stub Articles and Update Me Articles. Editorial help is always needed for the most relevant and timely information on the wiki!

An Article's Skeleton

The basis of every WARFRAME Wiki article should consist of the following characteristics:

  • Infobox: The infobox should contain an image between 200 and 300 pixels that clearly illustrates the content subject floating on the right of the text. (See below) It may also include additional details about the topic.
  • Brief Description: This should be a paragraph or two. The first line should contain the title of the page and that title should be bold. (See below)
  • TOC: A Table Of Contents will automatically be created if there are 3 or more headers included in the article. (See below for how to manipulate TOC)
  • Headers and Content: More in-depth information about the article's topic will be located between the beginning and end of an article's page. Typically, there will be multiple section headers that divide the article into navigatable sections through the table of contents. Text below each header should be detailed and relevant with as little redundant information as possible (See below).
  • Navigation: A navigation box at the bottom of the page that includes the page and other pages in a similar category. (See below for the preferred format of pages on a specific topic)
  • Category: This helps define a page's function. It also serves as navigation pointers for the FANDOM app. (Click here for how to add a category)

Using Source Mode

Source mode is generally preferred over Visual mode when editing in this Wiki. Editors can switch to Source mode by switching between "Visual" and "Source" tabs on the top of the Editor Window.

Source mode enables the use of features such as Templates, commenting, easier formatting and most importantly, the browser's spell check. If Visual mode is used, unnecessary formatting elements would sometimes appear, which contributes nothing but distorts the main content.

You can always use the Preview button on the bottom middle of the Editor Window before you Save.

Here are some basic tips in using Wiki markup and HTML tags in Source mode:


Headers are section titles used throughout any page with more than one attributes. For example: Cryo Rounds has Stats, Notes and See Also headers.
Headers can be added by typing ==Header== in source mode.
If smaller headers are needed, such as a sub section in one of the sections in the same page, editors can type ===Header===. Smaller headers can be created by adding more "=", with a maximum of five.


Main article: Help:Links

If a specific word refers to a page anywhere in this wiki, such as Mods, editors can type brackets, like [[Mods]] in Source mode. No additional parameters are required.

Note that (other than the first letter) this feature is case sensitive. If the word "mods" has to be used, then typing [[mods]] will produce mods. Note that the link links to the same page but appears without the uppercase "M". For "WARFRAME", however, [[warframe]] will produce warframe, a redirect page to Warframes.

If a word has to link to a specific section in a page, editors can type [[Stealth#Silent or Quiet Weapons|silenced pistol]], which produces silenced pistol. The "#" defines the section (header) name. This feature can be used within a page as well: [[#Commenting]] produces #Commenting, which links to the next header after this one without reloading the page.

Some pages with a namespace such as Category:Enemy Weapon cannot be linked with the above method. Editors can link to these pages by typing [[:Category:Enemy Weapon]]. Otherwise typing without the first ":" will categorize the page into the category.

For any links that link to external sites, type [https://warframe.com/ Warframe] (note the space), which produces Warframe.

Bold and Italic

Editors can type bold text by typing '''bold text''', and Italic text by typing ''Italic text'' in Source mode. These can be combined '''''thusly'''''.


Commenting is creating hidden text that only editors can see in source mode.
Usually this is used for embedding instructions when working with layouts, or hiding a large amount of text that is subjected for deletion.
Editors can comment out a line of text by putting <!-- around text -->.


  • Bullets can be added by typing * in front of a line of text.
    • Typing ** will produce a "sub-bullet".
    1. Typing # instead of * numbers the list.

Line Break

Typing <br/> will produce a line break
like this.

Using Templates

Main article: WARFRAME Wiki:Using Templates

Using templates is a great way to save time and hassle when editing. Most pages in the WARFRAME Wiki are associated with a particular template, and it is often mandatory to use the appropriate template, so that pages on the same topic will have a unified format and can be edited easily in the future.

Templates can be edited by switching to Source mode. They exist in the following infobox and inline formats:

| name      = (Optional) Name of mod, defaults to {{BASEPAGENAME}}
| image     = Image of the mod
| polarity  = Polarity image
| rarity    = Common/Uncommon/Rare/Crafted
| droppedby = Grineer/Corpus/Infested/All Factions


Editors can consult the template page by searching the template name (in this case Template:ModBox and Template:M). Template pages often include crucial information, documentation and usage that editors need to know about before using them.

Many templates do not require any inputs, such as {{Delete}}, {{UpdateMe}}, etc. These are often used as public service announcement templates. These may still have optional inputs.

Frequently Used Templates

Stalker d
“I am your reckoning!”
This page is a candidate for deletion.
  • {{Delete}} — If you see a page that is inappropriate or irrelevant to the WARFRAME Wiki, and should be subjected for deletion, insert this template on the top of the page.

“It's taking longer than I calculated.”
This page is actively being worked on and may not be completely correct. Please assist in making this page accurate. See WARFRAME Wiki:Research on ways to perform research on this game. Click here to add more info.

  • {{UpdateMe}} — If you see a page that is incomplete and can use some editing, insert this template on the top of the page.

“I want more... Operator, please hurry! This story is getting quite good!”
This article is a stub. You can help WARFRAME Wiki by adding a sentence or two.
  • {{Stub}} — If you see a page that only consists of two lines of text or less, insert this template on the top of the page.

“My Styling Guide page, what have they done to it? Fix this!”
This article is in need of a clean-up. You can help out the wiki by re-organizing parts of the article, checking grammar and spelling to improve the article.

  • {{CleanUp}} — If you see a section or page that could use some clean up on grammar and content, insert this template in the appropriate area.

Sgt Nef AnyoIcon
“Orokin secrets cannot remain secret forever! Start talking!”
The following article/section is conjecture. Content is subjected to change/removal as the game progresses. Please do not use this article for critical in-game information.

  • {{Speculation}} — If you see a page or a section with conjecture, insert this template in the appropriate area.

AladVPortrait d
“You're not supposed to be in here! You're going to ruin the surprise!”
The following article/section contains spoilers.
  • {{Spoiler}} — If there are spoiler content on a page or section, insert this template in the appropriate area.

  • {{Cite}} — If you see a statement that needs confirmation, insert this template in the appropriate area.
  • {{Main|<article_name>}} — If the section refers to another article for more details, insert this template in the appropriate area and attach the target page name using the correct format.
  • {{clr}} — This template moves any content below any floating objects. Useful in defining the end of a section.
  • {{tocright}} — This template moves the TOC to the right of the page.
  • __NOTOC__ — This magic word removes any Table of Content (TOC) in the page.
  • __NOEDITSECTION__ — This magic word removes any clickable "Edit" links next to headers.

Page Styling

See WARFRAME Wiki:Creating New Pages for few example layouts of some specific topics. When in doubt, feel free to refer to existing pages or contact an Administrator.


Weapon Styling: There are a couple guidelines that you should know before editing a weapon page. First, the "characteristics" section is only for information pertaining to the weapon function. Otherwise, this information (including but not limited to: no polarity slots, event only reward, requires clan research, etc) must be listed in either the Notes or Tips section of the page.

Secondly, all damage, critical, or status numbers listed on the weapon must include at least one decimal place, or two if the number is whole. (for example, a weapon deals 23.3 damage, that number is fine. if a weapon deals 40 damage, it must be written as 40.00). This assures users that it is a whole number and not a rounded number, and it makes it look a bit neater.


Date Formatting

Because the WARFRAME wiki is an international community, every country has their own numeric abbreviations of dates. To avoid confusion, most dates should be written out fully in "Month DD, YYYY" format, e.g. "January 1, 2021" or "October 25, 2012".

If a numeric or short date is needed (such as in a table), then use a "YYYY-MM-DD" format, always with 2 digits for month and day (e.g. 2021-01-01 or 2012-25-10). Besides being the ISO standard, dates in this format naturally sort properly in the case where a table column is made sortable.

Avoid seasons for dates such as "Summer 2021" or "Fall 2022". On Earth, the northern and southern hemispheres have opposite seasons. Instead, use phrases like "Mid-2021" or "Late 2022". Lastly, do not abbreviate the month or use superscripts/suffixes such as "Jan 1st" or "25th of October".

For release dates or any scheduling related to DE (e.g. TennoCon), dates will be based on DE's local time in Ontario, Canada (Eastern Time). Everything else will use Coordinated Universal Time or UTC.

Number Formatting

When expressing number values in text format, use commas (",") to separate groups of thousands and a period (".") to denote a decimal place. For example, "9999.99" should be formatted as "9,999.99".

Grammatical Tense

All articles should be written in the present tense by default. This includes:

  • Character deaths, absence, or dissapearances during and after in-game quests. A character may be alive for beginner players but absent for those further into the playable story. To keep it simple and to avoid spoilers, text should stick to being in present tense unless otherwise appropriate.
  • Ambiguous relative timeframe of content.

However, there are exceptions to this rule:

Citations and References

Any citations or references should use Template:Ref for formatting which is based on Wikipedia's Citation Style 1. See https://dev.fandom.com/wiki/Global_Lua_Modules/Ref#Parameters for full documentation. The most common citations are for websites which have the typical structure:

{{Ref|title=Article title|first=Author first name|last=Author last name|year=2022|month=1|day=1|url=https://warframe.fandom.com|access-date=2022-01-01|archive-url=https://web.archive.org/web/20220311013004/https://warframe.fandom.com/wiki/WARFRAME_Wiki|archive-date=2022-03-11}}

Sample render: Author last name, Author first name (2022, January 1). Article title. Accessed 2022-01-01. Archived from the original on 2022-03-11.

Images and Videos

Main article: WARFRAME Wiki:Media Policy

Screenshots and gameplays are welcomed. Generally, if your uploaded media refers to a specific line of text in an article, make sure to add it next to the related text. For any media that are for showcasing only, make sure to add it in the Media section of the page.

Plain images are generally preferred over thumbnails. However thumbnails can be used if a caption is really necessary.

To add an image, upload it via the "Add New Image" button in the dropdown in the top right corner of any page or via this link, and then insert the following syntax in the appropriate page:


Note that the parameters thumb and caption are used in thumbnails only, and should be omitted in most media; left defines the position, in which right and center can also be used; 300px defines the widths of the media. If the height needed to be defined instead of widths, insert x300px in place of widths.

If a lot of media is added to a page, a gallery should be used:

<gallery widths="300" position="center" spacing="small">

Galleries pertaining to listing items by their in-game images should use the following format:

<gallery captionposition="below" captionalign="center" hideaddbutton="true" spacing="small" navigation="true" position="center" bordersize="none">
image1.png|link=Page link|Item name/description
image2.png|link=Page link|Item name/description
image3.png|link=Page link|Item name/description

All this information, as well as the policy regarding uploading medias, is discussed in length in the Media Policy page.

Creating New Pages

Main article: WARFRAME Wiki:Article Policy

Pages are considered formal content of the Wiki. The purpose of a page is to deliver information about Warframe to the public in a detailed, accurate, formal and unbiased way. Nothing more, nothing less. Pages showcasing defects, bugs, or problems with Warframe are not permitted, and must instead be contained in user blogs or in the 'bugs' section in already existent articles.

When new content is being introduced to the game, new pages should be created. Before creating a page, editors should familiarize the proper page layout, make sure that there are no existing pages pertaining to the topic, and ensure that the content is relevant to the canon of Warframe.

Not everything should be made into a new page. The policies regarding creating and editing pages are discussed in length in the Article Policy page.


Editors can see the list of revisions and contributors in the history page of any articles. To access the page simply click on the drop down menu next to the "Edit" button.

In the history page, editors can undo unfavorable edits via the "Undo" link beside each revision. This link will bring you to a new edit page with a list of changes. Further editing can be done, or the page can be published immediately.

To revert to a specific revision that is not directly the one before, click on the revision date, then on the Edit button once the page has loaded. Further editing can be done, or the page can be published immediately.

Administrators also have the ability to "rollback" unfavorable edits.

These features must not be abused. Offenders will be banned.



Main article: mw:Help:Tables

HTML tables can be easily created using wikitext syntax. They begin with a {| and end with |}. Additional HTML attributes can be added to apply to all elements in the table or to certain rows and columns. See this page for more details.

These tables can also inherit the styling from CSS classes. Most common CSS classes used for tables on this wiki include:

  • wikitable (general use)
  • emodtable (for Mods)
  • sortable (allows table to be sorted)
  • listtable (for lists in table format)

An example of a table looks like this:

{| class="article-table" border="0" cellspacing="1" cellpadding="1" style="width:475px;"
! scope="col" |Mission
! scope="col" |Required Points
! scope="col" |Reward
|Operation Orphix Venom Emblem [[Emblem]]
|[[Ayatan Treasures|Ayatan Hemakara Sculpture]]
|[[Aura Forma]] + {{Weapon|Mausolon}} Supulchrax Skin
Mission Required Points Reward
Normal 500 Operation Orphix Venom Emblem Emblem
Advanced 1,000 Ayatan Hemakara Sculpture
Endurance 2,000 Aura Forma + Mausolon Mausolon Supulchrax Skin


Main article: wikipedia:Help:Transclusion

Content from other pages can be transcluded into the current page by reference. This can be achieved by the following wikitext:

  • {{:Page_name}} — full page transclusion
  • {{#lst:Page_name|section_tag}}labeled section transcluding
  • {{#lsth:Page_name|section_name}} — section transcluding by headers
  • {{Transclude|Page_name#section_name}} - helper template for transclusion that also adds a link to original page

For example, content from the Warframe Nexus section of the WARFRAME page can appear on this page like so:

{{#lsth:WARFRAME|Warframe Nexus}}

To filter how source page contents appear when being transcluded or not, enclose the desired content with the following tags:

  • <noinclude>...</noinclude> — avoid transcluding this content
  • <onlyinclude>...</onlyinclude> — only transclude this content
  • <includeonly>...</includeonly> — transclude this content but do not render on source page

Transclusion is also the method of how Templates are used, albiet with the addition of passing parameters.


Some content on pages is generated by Lua scripts located in the Module: namespace. Generated content cannot be edited directly using the Visual or Source editor on the page on which it appears. Instead, users need to modify the Module page and related subpages of the Lua script that created the content. It is advised not to edit the source code directly unless you have reasonable scripting experience. Users should modify the /data pages instead when updating database information.

To call a function in a Module:


For example,

{{MissionTable|Plains of Eidolon|Hydron|Hieracon|Ganymede}}

generates the following table:

Target Planet Name Type Level Tile Set
DawnsEarlyLight Earth Plains of Eidolon Open World 10 - 30 Plains of Eidolon
IconGrineerB Sedna Hydron Defense 30 - 40 Grineer Galleon
IconInfestedB Pluto Hieracon Excavation (Dark Sector) 35 - 45 Corpus Outpost
IconCorpusB Jupiter Ganymede Disruption 30 - 35 Corpus Gas City

The WARFRAME wiki also contains user-made databases of WARFRAME's content. These reside in /data subpages of Modules and are formatted as Lua tables. These include, but are not limited to the following pages:

If any errors occur, "Script error" will be displayed where the module is called. Clicking on the error will reveal the call stack and error for debugging purposes.

Each Module page possesses a /doc subpage that provides additional information regarding the module's usage and function.

Feel free to contact any Administrator or Moderator for additional help or if any issues arise.

Site-wide scripts

Site-wide scripts are located in the MediaWiki: namespace and apply to all pages of the WARFRAME wiki, regardless of content. These scripts are programmed in JavaScript and require an Administrator's approval before being uploaded to the wiki.

Some features cannot be programmed in Lua and require external resources or more advanced features that JavaScript provides. These solutions cannot be implemented as Modules and must reside in the MediaWiki namespace. Typically, they are used alongside Templates that embed specific HTML elements onto pages which these scripts operate on. Examples of these scripts include:

For more information see the following resources:


Please feel free to take a peek on other pages for editing guidelines. Use your Profile Page as a testing ground or sandbox. Create testpages under your username (Special:Mypage/testpage).

If you have any questions or want to go beyond simple editing such as creating templates or even a page overhaul please do not hesitate to contact an Administrator.

Have fun editing Tenno!

Further Reading