Manual of Style outlines a standard of clean, consistent formatting for articles on this wiki. The formatting described here is a guideline and can be overridden where circumstances warrant it. These guidelines will never be unerringly perfect for every situation. However, please try your best to keep to the advice outlined in this article so others may use your edits as an example when creating and editing their own articles.

These guidelines are a summary of the most important guidelines for this wiki, but a more expansive set of style guidelines can be found on Wikipedia at Wikipedia Manual of Style.


One of the most important parts of wiki editing is how to structure an article. The structure is a powerful thing: it dictates what information the reader reads and when he or she reads it. It can influence what people contribute, where it goes, and how it might be written. Structure has the power to inform or confuse the same way good or bad writing does. Keep a well structured article, and you're more likely to have a high quality one.

Organize sections in an article in a hierarchical structure like you would an outline. Keep it logical, but feel free to forsake strict logic for readability. Wherever possible, try to have an introduction for each section. Just like the article as a whole, the section should start with an introduction and then have its subsections below it. Try using a shallow structure rather than a deep one. Too many nested sections usually leads to a confusing or unreadable article.

Above all, keep your layout consistent. Don't throw your reader a curve ball too often. The following sections will offer some good advice on keeping your articles clean, consistent, and clear.

Article layout examples

The wiki has guidelines for how to lay out different types of articles. You can see these layouts in the Boilerplates and Templates pages.


When you have different versions of a subject that have the same title, Tabview should be used. For example, if you need a page for the new Doom Weapons but their are also many other versions of the same weapon, instead of cramming them on one page you would use Tabview because it would look much more organized.

To use Tabview, you need to create a page of content for each tab you wish to display. You use the tags <tabview></tabview> on the main page where all the tabs will be displayed and enter the name of the pages that the tabs will show in between. For example, this is what the Tabview for the ShadowReaper of Doom looks like:

ShadowReaper of Doom/Original|Level 8||true
ShadowReaper of Doom/Dark|Level 10
ShadowReaper of Doom/Unlucky|Level 12
ShadowReaper of Doom/Mighty|Level 15
ShadowReaper of Doom/Dread|Level 18
ShadowReaper of Doom/Heartless|Level 24
ShadowReaper of Doom/Obsidian|Level 27
ShadowReaper of Doom/Forsaken|Level 31
ShadowReaper of Doom/Grim|Level 35
ShadowReaper of Doom/Dire|Level 40
ShadowReaper of Doom/Bone|Level 44
ShadowReaper of Doom/Horrific|Level 48
ShadowReaper of Doom/Ghastly|Level 52
ShadowReaper of Doom/Grisly|Level 56
ShadowReaper of Doom/Bloody|Level 60
ShadowReaper of Doom/Sanguine|Level 64
ShadowReaper of Doom/Corrupt|Level 66
Each line has the name of the page, followed by the text that will show on the tab. Where it says "true" is what the default tab will be.


In encyclopedic articles, the protagonist of DragonFable should be referred to as the "The Hero."

As the player characters can be either male or female, remember to write in a gender-neutral way. Where a pronoun must be used, the wiki uses "they" or "their", rather than "his/hers". However, in walkthrough articles and guides, second person (you) should be used.

The term "the player" should only be used to refer to the individual playing the game, not a character.

Lead section

Unless an article is very short, it should start with an introductory lead section, before the first subheading. The lead should not be explicitly entitled == Introduction == or any equivalent header. The table of contents, if displayed, appears after the lead section and before the first subheading.

The lead should be capable of standing alone as a concise overview of the article, establishing context, and explaining why the subject is interesting or notable. It should be between one or two paragraphs long, and should be written in a clear and accessible style so that the reader is encouraged to read the rest of the article.

If possible, make the title the subject of the first sentence of the article. For example, write:

Artix is a great paladin and servant of the Light Lord.

The first time the article mentions the title, put it in bold using three apostrophes — '''article title''' produces article title. Avoid other uses of bold in the first sentence, except for alternative titles of an article; for example:

The father of Absolix Ryuusei Cartwright, known as Omega, was the one responsible for the death of Glenn Galrick.

Follow the normal rules for italics in choosing whether to put part or all of the title in italics. This will mainly apply to the titles of books and games:

AdventureQuest: The Dragon Secret is a novel set in the AdventureQuest universe.

Do not put links in the bold reiteration of the title in the article's lead sentence.

Table of contents

A table of contents will automatically appear in articles with a minimum of four headings (unless forced by the below options). By default this will be left-aligned above the first section heading.

  • To the force a TOC position (left-aligned): __TOC__
  • To completely remove the TOC from a page: __NOTOC__

The table of contents can be right-aligned - but only if it is very long (over 15 entries) and an information box is not occupying the top-right corner of the article (rare exceptions exist).

  • Right-aligned TOC that floats next to text: {{tocright}}

Section headings

Use the == (two equal signs) and === (three equal signs) markups, as in === Section headings ===, to enclose major and minor section headings respectively. These are convenient synonyms of the <h2> and <h3> heading markups.

Be careful not to use single equal signs by mistake. That is a synonym of the <h1> heading markup, which is used automatically by the wiki's page header mechanism. Reusing it is bad style and risky coding.

Section headings are signposts to your article's structure. Make them short and simple to avoid confusion. Concision without obscurity in headings is good: for instance, you may usually drop a, an and the; omit unneeded pronouns; and so on.

Do not reuse the article title in section headings. Searching an article is made easier if section headings are distinct from the title and from each other.

Write section headings in lower-case letters, except for the first letter of the first word and the first letter of any proper nouns.

This convention may differ from section heading rules that you have met elsewhere.


DragonAmulet Update


Images make an article memorable and pretty. They can speak where words fail. At the same time, misplaced or untidy images can detract from an article. When choosing images, keep in mind placement, size, and the appropriateness of the image to the section. Let images flow with the text instead of break it up.

Large images such as screenshots should use the "thumb" (example:[[File:CoolImage.png|thumb]]) option which displays large images as thumbnails. Images should generally be right aligned to enhance readability by allowing a smooth flow of text down the left margin - the "thumb" option does this by default. If an infobox is not being used in an article, a right aligned picture in the lead section is encouraged.

For more information, see Help:Images.


When an article has many images, or can be improved by having more, and having inline images be detract from the readability of an articles, the use of a {{Gallery}} section is encouraged.


Article message boxes and tags

You may tag an article if you believe it may need to be reviewed due to inaccuracies or poor writing. Articles will be categorized in one of the categories of Category:Site maintenance. For a complete list of available templates, see Category:Article management tags.

Writing and formatting

The message boxes generally appear at the top of the page after disambiguation links, but may be included within a section. {{stub}} must always be at the top of the page.

  • Stub {{stub}}: When an article has very little information and you believe more can be added.
  • Section stub {{Section-Stub}}: When the article is not a stub, but some sections may need expansion. Use it within a section.
  • Missing information {{Missing info|<specify>}}: Use it when a specific key information is missing.
  • Bad writing or poorly formatted {{cleanup|<specify if possible>}}: When an article may require a rewrite because it is poorly written or does not adhere to our current policies and guidelines, or the article has formatting/layout issues.
  • Picture required {{pictures wanted}}: Article generally benefit from having pictures. If the picture is bad or does not adhere to DF:IMAGE, you may add it to the article and/or tag the picture with {{cleanup}}.

Tags within the text

  • Confirmation {{confirm}}: When you contest certain material.
  • Citation {{citation needed}}: When a citation is required to support the claim, generally from developers.
  • Clarifying {{explain}}: If something is too vague and requires a better explanation.


  • Move {{move|<page name suggested>}}: If you are unsure how to name the article or think that it may be contested.
  • Merge {{merge|<page to merge with>}}: When the article should be merged with another and may be either deleted or used as a redirect.
  • Split {{split}}: If the page covers more than one topic and may benefit from splitting (e.g., a section would be more appropriate as a separate article).
  • Delete {{delete|<reasons>}}: If you think a page about a character or a topic isn't needed (e.g., it isn't notable or it should be merged with another article).
  • Speedy delete {{speedydelete}}: Page deletion which does not require review, such as vandalism, spam, etc.

See also, references, external links, and navigational tables

The last sections, if they exist, should always be "See also", followed by "References", followed by "External links". In the case of "See also", use bullets to list the internal links. Under the references section should be placed <references/>. Finally, in the external links should be all external links.


Categories should be added to the end of an article—a full list can be found on Special:Categories. They take the form [[Category:Categoryname]].

All articles should be accessible starting from Category:Browse, via subcategories.


Head quotes

This type of quote is seen at the top of an article. It is only allowed within character pages. Place {{quote}} above the infobox.


Format a long quote (over four lines) as an italicized block quotation, which will be indented from both margins. Do not enclose the block quote in quotation marks. To format a block quotation, do not use the wiki indentation mark ":" — instead, use the HTML <blockquote> element.


Grammar is a writer's toolbox. You can't build good sentences without knowing how to use your tools. Since a wiki article must be as clear as possible for all the people reading it, editors must keep close to correct grammar standards to ensure clear communication.


Titles such as lord or king start with a capital letter when used as a title (followed by a name): "King Tralin", not "king Tralin". When used generically, they should be in lower case: "Tralin is a wise king." The correct formal name of an office is treated as a proper noun. Hence: "Tralin is the current King of Deren."

Classes should only be capitalized when used as a proper noun, i.e., as someone's name. ("Wizard, go be evil" versus "That wizard is quite evil.")

Races such as elf, moglin, human and dwarf should not be capitalized except when used as a proper noun or at the beginning of a sentence.

Titles of works

Italics are used for the titles of works, such as books and games. The titles of articles, chapters, and other short works are not italicized but are enclosed in double quotation marks.

For example, italicize AdventureQuest: The Dragon Secret, and use quotes if it is only a chapter that is mentioned.


As any work of fiction, the installments of the DragonFable series (regardless whether they are video games, novels, comic books, or any other supplemental material) take place in a "perpetual present tense" in the sense that their events unfold before the player/reader's eyes as if in the present (even though e.g. the novels are technically written in the past tense). With the narrated events thus continuously shifting from the future, through present, to the past as each story progresses, there is no single definitive "now" in the DragonFable series but the one that each individual player/reader is currently at. Since this wiki is written for the benefit of the players and readers of the DragonFable series, it should therefore ease their access to its contents by recounting the events of individual stories in the present tense. On the other hand, events that led up to them should be summed up in the past tense to clearly indicate that they took place outside of the time frame of the described installment.

  • Present tense should be used to describe the involvement of any character, inanimate object, location, group, country, etc. in the plot of a particular installment of the DragonFable series, be it a video game, a novel, a comic book, etc. Additionally, present tense should be used when writing about the last known state of an entity that has not yet been invalidated by new information.
  • Past tense should be used to describe events that transpired "off-screen", such as historical lore and character backgrounds before their introductions to the DragonFable series. Events that happened with a particular subject between installments should likewise be recounted in the past tense before describing the subject's involvement in the more recent installment in the present tense.
  • Future tense may be used at the contributing editor's discretion whenever it helps to make the article better readable.

Walkthrough articles should always use the present tense, because they are intended to be read in real time as the player progresses through a game. Occasionally, however, future tense may be used to warn the player of unforeseen consequences without spoiling the plot.


We now come to the meat of an article: the words themselves. When you're editing wikis, you're both academic and artist. You have to be accurate, but you also have to be interesting. Neither one can dominate; you have to skillfully balance both.

Keep your writing concise. Don't use two words where one will do. Keeping your writing simple will make it easy to understand and easy to expand on. Use complete sentences whenever possible. When you write, use grammar as a toolbox: know the rules, but only break them on purpose.

Check your spelling and grammar. Do not use 'u' in place of 'you' or '2' in place of 'to'. Write the way you would for a class paper or a newspaper article.

Keep all of the topics you cover within the scope of the article. What that means is, you don't need to give a detailed history of humans on the page about Winston Churchill. Consider the article's title as your point of origin and write from that perspective. Make use of the wiki's ability to link to more detailed articles or external sources for more information.

Write from an impersonal perspective. Do not use "I." For example, do not write, "Of all the threats from heck, few demons are as insidious and deceptively deadly as the darkness demon, as far as I know." Avoid drawing attention to the author (yourself) as much as possible.

Be bold. If you know something is wrong, correct it. If you think you could word something better, write it. If an article has a glaring deficiency, fill it. Even if your first attempt isn't golden, you can fix it later or someone else will come along and fix it for you. Don't be afraid to screw up.


Every article can be improved (even this one). Following these guidelines will not ensure a perfect article the first time, but it will give the article a stronger skeleton. It's ultimately your job as an editor to put meat on it.

External links

Community content is available under CC-BY-SA unless otherwise noted.