Fandom

Final Fantasy Wiki

Final Fantasy Wiki:Article Layout Guide

20,840 pages on
this wiki
Add New Page
Talk0

The Article Layout Guide is the official guide to structuring articles on the Final Fantasy Wiki. This will cover different types of articles, and the usage of headers, formatting, templates and standard page layouts.

This guide will refer to the term "release" (referring to a game/book/film/other form of media), and several forms of MediaWiki markup. For more information on how to use markup and on general editing, see Help:Contents. This is a guide for page structure and formatting articles, a guide to writing style and situations in which format types should be used is found on the Manual of Style.

Opening contentEdit

The opening sections contain a few tags and some brief beginnings to a page. Note, that a lot of tags and details will end up appearing throughout the article, but become immediately relevant prior to the main article body.

SideiconsEdit

A {{sideicon}} tag must be included in any article that is not out-of-universe. It will be included either at the start of the page if the article is about a subject from a specific release. A sideicon is inserted with the text {{sideicon|, followed by the codename of a series' release, and a closing }}. One must be included for every relase the article in question is written about. This will add the image and a link to the release at the sidebar of an article.

A list of sideicons can be viewed below:

MboxesEdit

An {{mbox}} is included right below the top sideicon (if present) or at the very top of an article otherwise. An example of these would be {{expand}}. This is to indicate a problem with the article, and to alert other users to fix it. This is only to be used if there is a significant issue with the entire article; if there are only a few sections which are problematic, a {{stub}} template is often preferred, with a stub type and the game it refers to.

InfoboxesEdit

Infoboxes are not required on all articles, but if an infobox is required (see below if an article fits), then it will go straight below. Infoboxes must be created with a specific purpose in mind, and will be based on another infobox template. Examples are {{Character}} or {{Location}}. Any links contained in infoboxes can be repeated throughout the article. Sharing information with infoboxes is generally discouraged, aside from unavoidable exceptions allowed and when the referenced subject can be mentioned in more detail; the article should generally not simply repeat what is mentioned in an infobox.

Infoboxes are used to portray a summary of facts, vital information on a subject, or information which lacks a better place in the article. Facts that are not found within the release should only be included if they can be sourced, such as from a Square Enix guide. The main image in an infobox has the same conventions applied as main images of any article.

SidenavboxesEdit

A side {{navbox}} often fits better at the start of an article than at the bottom. Examples would be {{Translations}}. In cases where sidenavboxes are used, no main image should be used at the top of an article.

ImagesEdit

The main image of an article should be played to the right, per "[[File:Example.jpg|right]]". It should be within an infobox, below an mbox, below a sideicon or simply at the very top. This image should not exceed 250px, and is generally preferred to be between 150px and 200px. The image should be the one representing the subject best. This can be a character model render, a screenshot, a photo or logo (if out-of-universe), a sprite, or an artwork. Whether it should be the main image or not is determined by image quality or recognisability. For instance, an image for an article about a recurring series subject should have recognisable traits, and if many of the recurring appearances represent a specific one, then the specific one should be used. In ability pages, an image of the ability being cast by any character that clearly represents it is considered best.

A secondary image can often be added to the side of the opening text. This could be a sprite in the case of character and enemy pages, or an icon in the case of abilities. There should generally be no pixel width needed to be adjusted, though if the image is too large, it can be set to 50px. The secondary image should go below a quote template and just in front of the introductory text.

Images can be used where appropriate if to represent certain sections, and should be placed to the right. Any image directly following should be placed to the left as per "[[File:Example.jpg|left]]", forming a sort-of zigzag pattern. An image without white/transparent backgrounds should be thumbnailed by adding "thumb" in the image coding, as in "[[File:Example.jpg|thumb]]". A caption should be added to thumbnailed images, a short description of what the image is by writing the caption at the end of the code as in "[[Image.Example.jpg|right|Caption here]]".

In sections where an image is contained, a {{-}} should be used below the section. Other uses of images should be in galleries.

QuoteEdit

Below any of the above, where applicable, a quote should be used. This will use {{q}}, or {{dialogue}}. The quote has no requirements other than to represent or mention the subject detailed in the article. It should ideally be an in-universe quote that a character actually said, though official game descriptions can be used in cases where none is available, or where the quote does give a representation of the subject. Examples would be descriptions of enemies within game guides.

IntroductionEdit

In all subjects with the exceptions of "list of" pages and game subpages, articles should begin with '''bold text''' of the name, as seen at the beginning of this page, followed immediately by the {{j}} template listing the name in Japanese, if known (although this is not required for out-of-universe people, or when the Japanese name is contained within an infobox). The kana and romaji are required, but the literal translation is only required if it differs from the name. Users can find Japanese names by viewing Translations pages. Following this, the intro should say what the subject is, and which game it is from, or note that it is a recurring feature using "recurring in the [[Final Fantasy (Series)|''Final Fantasy'' series]]". The rest of the introduction should give a brief outline on the subject, and can be only a few sentences or two/three paragraphs.

HatnotesEdit

Hatnotes are used to point users in a direction to find other content that cannot be linked to in the article below, or to make the link more obvious. Examples are {{See Also}} and {{main}}. See Also is used below introduction sentences and before the content of articles, or above introductions in place of a quote, to link users to similar topics with similar names. For instance, an article on Chocobo Racing in Final Fantasy XIV will link to the main Chocobo racing (minigame) page, while an article on a Behemoth in Final Fantasy XII will link to the main Behemoth page. Other hatnotes used such as {{main}} and {{SeeEnemy}} are used underneath section (sub)headers, below images and sideicons but always at the top of the content.

BodyEdit

The body of an article is its main content. This will differ greatly based on the type of articles, and details are listed below. Headers should be used to detail the content below the introduction.

Specific feature pagesEdit

For all in-universe pages, the first section should often describe the subject in more detail. This could be through a Profile describing the appearances/personality/behavior, or a Mechanics section describing the gameplay details and fundamentals. Neither apply when the specific page layout includes neither of these sections as mandatory, or when the information is brief enough that the opening paragraph(s) already describe enough about the subject that is not contained within the following content.

For specific feature pages, anything below the above will be lore information through a Story section, or will contain more gameplay details. If the subject is a primarily gameplay subject (an ability, an enemy, a quest), then this could be through a series of sections or tables; if the subject is a primarily lore subject (a character, a location) then this could be through a Gameplay section or anything that the specific layout demands. A "Gameplay" section should not be used if the subject is a gameplay subject primarily.

Recurring feature pagesEdit

For recurring feature pages, the article body is often very brief, containing only quick "Profile" or other content about the general subject. The main body of these pages will be an Appearances section, used for all appearances within first-tier coverage per scope. The start should be a sideicon followed by an image to the right as usual, and any hatnote can be used below this, but is often not needed. The first time the subject's name is mentioned within these sections, a release-specific link, such as the anchor on a "list of" page or the tagged version of a page for that release, should be used. The following content should describe only notable information anyway; if the information exceeds a significant length of content, it is often preferable to split the content off into its own article for that release.

SpoilerEdit

Any section that contains information that may spoil readers must be preceded with {{spoiler}} and concluded with {{endspoiler}}. Please see Project:Spoiler Policy for more details.

Controlling content displayEdit

On several pages, there may be a desire to display content that is not plain prose. There are many ways to control the display of content to be best for readers on all screen types and to be most suitable for the specific situations and types of information.

In the simplest form, bulleted and numbered lists can be used where appropriate for simple lists, and appropriately formatted tables can be used for data and more complex lists.

There may be a desire to feature content within multiple columns to make the best use of horizontal space available, such as to group together tables and lists with a small width and similar purpose, or to group together different versions of the same table/list within a game. This content should be placed within a flexbox div (<div class="multicolumn"> to open and </div> to close). This is the most responsive way to control layout, meaning it will make the best use of space for different screen sizes by displaying as many columns in a row as needed.

Displaying different content through tabbers should be avoided. This is because they are too reliant on JavaScript to appear, which does not work outside of a web browser with the desktop skin, such as on the mobile skin.

TablesEdit

Many specific articles may contain data and information that can be compiled into a table ({| and |}). Tables should be used only for this purpose and not for controlling the display of content.

A table should either take up the width of the screen (class="full-width") or half the width of the screen (class="half-width"). Alternatively, many tables can be placed on a page, in which case they should be wrapped in a flexbox div (<div class="multicolumn"> at the beginning, </div> at the end) with no set widths other than pixel widths to best fill the space of various screen types.

Each game has a certain color swatch code for its table headers and subheaders. Instead of inputting the hexadecimal code for each color (style="background-color:#000000"), type in the class code for each release (class="seriesa"). The colors that correspond to each class code are listed below and in Help:Codenames, and are also provided further below for consultation. It is required that class codes are use.

The main row is given the header color, while the main column is given the subheader color. Both contents are centered. Use ! instead of | before each to automatically center and bold the header and subheader, bypassing the use of three apostrophes ('''). Wordings are in left-alignment, while numbers or very short terms are centered.

Class codes are found on Help:Codenames. For more detail on table formatting and markup, please see Help:Tables.

VideosEdit

Throughout an articles' content, it is often required for an article to contain a media file. Policy on what files is found at Project:Media, while any other information is listed at the specific layouts.

When embedding a video from YouTube, it is encouraged to place them inside boxes. Place a caption and the caption box will be colored according to related header - follow game specific colors as above, or the series color if general. Video alignment follows viewer discretion and suitability. The coding below is an example, with those in double brackets being which parameters editors can customize.

To embed a YouTube video, use the following. For more details see the {{Video}} template.

{{Video|[YouTube ID]|align=[align]|title=[title]|class=[class]}}

Closing contentEdit

Closing content is contained below the main body of an article.

Creation and developmentEdit

Below the body of an article, but above musical themes, appearances sections or notes/gallery, a Creation and Development section can be included for in-universe subjects. It is important to include references and sources throughout this section as it covers out-of-universe information. This can use interviews with developers or videos to describe the internal development of the subject. If only brief information exists, however, a Trivia section is preferred.

In some cases, such as character articles, a {{quote}} template is used for a voice sample in a Voice subsection. This will only be an English voice actor/actress. Brief details on who the voice actor/actress is for the Japanese and English versions, with links to their pages, and if available, why they were chosen, should be used.

Musical themesEdit

A Musical Theme section should be used when demanded. This only applies where the template is demanded; locations will always demand Musical Themes section, character and sidequest pages often will, while ability pages clearly won't. Enemy pages should often not have a Musical Themes section, as if a boss has a specific theme, it will have one on its related character page, as opposed to its enemy page.

Musical Themes will contain a {{listen}} template is used to help readers listen to an audio sample of the main theme. Template placement should be aligned to "right". Standard practice is to put those templates on the left-hand side. Seek out the Audio help page for more information.

Below the listen template, the theme name, a link to its page (if it has one, per ACP dictation) and the Japanese name with {{j}} should be used. All themes relating to the subject should be used.

Related appearance sectionsEdit

Below the body of an article, the musical themes or the creation and development sections, but above notes and gallery sections, a section will be used with subsections below it that will list the appearance of a subject, though how they are listed depends on the scope.

For articles about a recurring feature, an Appearances section is used within the article body, see above.

For articles about a specific feature, an Other appearances section is used (or a /Other appearances subpage, if there are 5 or more). Similar to "Appearances", this contains the same section structure, and is used for all appearances which are given first tier coverage. The difference is that Other Appearances is secondary to articles about specific feature within specific appearances, such as the appearance of a character outside of their original storyline, or a spinoff game modeled after a location or enemy. These do not include appearances canon to the original storyline of the subject or its subseries, and only non-canon appearances in or outside of its subseries are included.

Non-Final Fantasy guest appearances sections (which can also be moved to a /Other appearances subpage if one was created) are used to refer to game series in which a significant guest presence of the character, ability or location featuring strongly in gameplay, story or context. It normally refers to games which have second-tier coverage in scope, and includes material licensed by Square Enix, often as a collaboration. A subsection should be added for each game series in which a guest appearance features as long as it is second tier in scope*if a series does not appear in second tier but features a significant guest appearance, it should be added to second tier should have a link, hatnote or otherwise, to their page on a wiki with specific information within that subject, such as {{KHWiki}}. The subsections should briefly describe the story, gameplay and context, of the guest appearance, and contain an image.

Other media sections appear with images to detail the other media the subject appears in popular culture or otherwise, and is used to contain third-tier scope information. Possible subheaders include Impact section detailing reception and popular culture appearances of the subject, a Fandom section for small notes about fandom impact, as well as Television, Film and Anime to list various cameos. A Games subheader can be included for any cameos or references to the subject in other games (that are not full guest appearances), such as a costume in LittleBigPlanet. Additional subheaders can be added for notable third-tier appearances, such as fandom projects like 8-Bit Theatre. These sections are optional, and are the most important to be referenced by far. They can contain images, though it is often preferred to include galleries if the content will clutter the section.

Finally, Merchandise contains galleries or otherwise of licensed Square Enix merchandise.

GalleriesEdit

Image galleries section should also be created when a number of images in a section clutter the layout. Images should also be used with a caption to describe each of the images it contains.

<gallery>
Example.png|Caption here
Example.png|Caption here
Example.png|Caption here
</gallery>

Galleries are created where appropriate, but they should mostly be placed above note sections but below appearances sections under a Gallery header. If the gallery contains a very large amount of images, a /Gallery subpage can be created, and the Gallery header should only contain a {{main}} link to that gallery. When a subpage is created, the base page should not contain any other galleries, as every gallery should be moved to the subpage to allow readers to view all images on that subject at once.

A ;title, or ===Subheader===, should be used if the gallery refers to a specific set of images; for instance, if a large number of images exist for images of Blitz in the GBA release, when the article contains images of the most recent release (the mobile port), then a gallery may be titled "GBA images".

Note sectionsEdit

Below galleries as the final sections on a page, notes refer to any miscaellaneous content that has yet to be outlined on the page.

An Etymology section will describe where the name came from. This uses one or multiple {{Etym}} templates, which get content from their respective information given on their page in Etymology namespace. More information is covered at Project:Etymology.

A Trivia section will contain bullet-point lists of interesting facts about the subject. This could contain popular references or fun facts that do not fit within the article. Trivia may only contain notable information, although the notability can be dealt with on case-by-case basis.

External links sections should link to relevant pages on important fansites, Wikipedia, the Google Play/App Store respective links or Square Enix' website.

References should only contain {{reflist}}. If any information needed to be sourced, this is always included as the very last thing.

NavboxesEdit

The final content on a page, {{Navbox}} templates which are not a sidenavbox are used. Any specific feature page, or recurring feature page where a specific release is strongly relevant to the recurring feature, will have release navboxes, such as {{FFIX}}, {{FFXIV}}. A recurring feature page is only strictly recquired to have the navbox for its subjects, such as {{weapons}} or {{enemies}}, but can include release navboxes if it fits the preceding requirement. Out-of-universe subjects should have any relevant navbox to their page, such as {{personnel}}. The only exceptions to all of these are subjects which are even more specific, such as {{FFXIV Items}} or {{FFXI Enemies}}.

Categories and interwikiEdit

Categories and interwiki links are the final things added to a page, but do not make up its content.

Specific page layoutsEdit

The layouts of specific pages vary on the type of page. This will include specific information on the body of the articles.

Media releaseEdit

Articles for media releases (games, books and films) should contain:

  • the descriptive Intro, describing about the game in general. Some snippets from the content of the article may be written here,
  • the Gameplay (if the release in question is a game), divided into subsections on the aspects of the game that makes it unique from the rest of the series. Links to the gameplay element pages, if any, should be linked too,
  • the Synopsis section for an overview of the lore, containing:
    • the Setting in which the story takes place. A link to the main/list location/world article should be added too,
    • the list of playable Characters including a short description. A collage of the characters picture would be a good addition,
    • the Story, written from the point of view of the main/player character,
    • Themes, describing the main conceptual themes and influences to the game's style and design,
  • the Music, describing the composition, composer, soundtrack, including main themes, adding in links to the respective music article,
  • Development, featuring important details on the creation and development of the game, featuring detail on:
  • Release (or Releases depending on if it was re-released), containing the original release and any re-releases of the media in question and their changes,
  • Reception, which contains:
    • Critical reception, listing the reaction of critics,
    • Accolades, listing any awards the media has won,
    • Commercial performance, listing any known information about the sales performance and/or box office for films,
  • Production credits, listing the entirety of the staff/cast behind the production.

CharactersEdit

All character articles follow the same format general format, with the exception of whether they are a recurring character or not. For specific characters:

  • A character infobox, usually {{Character}} unless the game has its own specific infobox.
  • An Intro, which determines which games the characters is from and their role within the game and a brief explanation of the character in terms of setting and personality.
  • A Profile for a background on the character's information, which will contain the following subsections (normally in that order, though it can be bent depending on whether spoilers are included):
    • An Appearance to describe how they appear in their releases in terms of features and attire.
    • A Personality section to describe their personality and character within their various releases.
    • Depending on the character, an Abilities section to describe what the character is shown to be capable of.
  • A Story section about the role of the character in the series of events that involve them. Divided by events (e.g. early life), and also by game if the timelines do not overlap. This story section must be from the original series in which they appear, and details in-universe chronology.
  • A Gameplay section if the character features in battles or other gameplay. Contains general information about their roles in gameplay, general battle style, job, how they are played, or other information. If the character is playable in any release, it should contain a {{main}} link to its /Gameplay subpage. Divided by release if the character appears with this information in multiple appearances.
    • Depending on the game which the Gameplay section discusses, a similarly appropriate sub header can be used.
  • A Creation and development section describing behind the scenes work.
    • A Voice sub-section if the character appears in a voice acted game with audible lines. Mentions of the voice actor, comments on the voice, and a sample of the character speaking are featured here.
  • A Musical themes section if the character has themes unique to them. Details said themes based on the soundtrack and in-game occurrences, with a sample of a version of their theme present.

Gameplay subpageEdit

If a character is playable in any release, and many data tables are required, it should have a gameplay subpage. Like the gameplay section on the character's base page, this should be divided by release if there are multiple. It should contain the following:

  • A Party member section if the character is playable and does not otherwise appear as a boss or in another form.
    • An Abilities section if the character is playable and has abilities specific or related to them. General discussion of abilities and links to the relevant articles for them are featured here. This includes all command and support abilities, including Limit Breaks, possibly divided into sub-sections.
    • A Stats section if the character is playable and has unique stat information. For listing base stats, and stat growth data specific to the character.
    • An Equipment section if the character has their own equipment not shared by every character or the release involves weapon proficiencies. Statement of weapon types and weapons equippable by the character are made here, and a link to the release's weapons article.
  • A Boss section if the character appears in a boss battle. Mentions of when and where they are fought, and general comments on how they fight, as well as links to the boss pages are featured here.

AbilitiesEdit

The following constitutes an Ability article:

  • The Intro describing the ability in general, such as which job/skillset generally possesses it, and where the ability first appeared.
  • Depending on the length of content, a Mechanics section can be optionally used.
  • If the ability page is a skillset, such as Blk Mag (Final Fantasy IX), a List of [title] Abilities section containing a table should be used.
  • If it is recurring feature, the Appearances section divided between every game title should list them, whether as a status effect, magic, enemy skill or player skill, and listing every possible name the ability has appeared in every possible version of each title.
  • A Gallery section which contains images related to that ability in all possible appearances, including screenshots from different platforms for the same game.

EquipmentEdit

Equipment pages have:

  • An Intro describing the Equipment in general, such as which job generally uses it, and where the equipment first appeared.
  • If it is recurring feature, the Appearances section divided between every game title should describe it, whether wielded by the player or the enemy, and listing every possible name the equipment has been given in every possible version of each title, plus what attributes, elements or abilities are usually related to the equipment in question.
  • A Gallery section which shows all appearances of the equipment piece in question, listed accordingly to the Scope order and oldest to newest for each console the equipment piece may have a more or less different design for the same game.

Place the navigation template related to the type of equipment, and don't forget to categorize them with relevant categories.

LocationsEdit

Locations are usually given the fullest title used in their respective game. For example, the nation of Nabradia in Final Fantasy XII is usually referred to as such, and not as an individual city. Thus, the location page is titled Kingdom of Nabradia. Locations with the article "the" preceding the name are referred to without the article for Wiki organization purposes. Rationale is on Talk:Neverwood, and covers locations such as Bosco Pampa and Gapra Whitewood.

A Location article should include:

  • A location infobox, usually {{Location}} unless the game has its own specific infobox.
  • An intro, which determines which game the location is from, and summarizes its placement in its setting.
  • A Story section for events that occur at the location.
  • A Locations section covering how the location is accessed and its placement in the game's world, and featuring sections for each of the multiple sub-locations or sub-areas that compose the location individually. Descriptions of the setting, events, interesting dialogue, and items found with specific reference to location should be listed here.
  • A Maps section if applicable showing the layout of each location, optionally with points of interests marked on them.
  • A Quests section covering every individual subquest, sidequest, or minigame related with the location. In instances where a quest takes place over multiple locations, the quest should have its own article and be mained, featuring only information relevant to the location in question in the section. Item Farming and Blue Magic earned in the are also included here.
  • A Shops section covering the inventory and prices of shops found at the location. Should state the sub-location the shop is found in and link to the relevant place on the page.
  • An Items section listing every item obtained in the field, with the sub-location it is found and a link to the section given. Criteria should also be stated if it is not always present or accessible in the area.
  • An Enemies section for enemies found in the location, divided by sub-location. Most games have specific sets of enemies that appear, whether through random battles or visible on the field map. If so, the section should list groups of enemies, and potentially encounter-rates and battle-type information. Denote bosses with the unlinked phrase (Boss) following each linked enemy.
  • A Musical themes section listing the tracks that plays in the location and when they are played. This includes music that plays during specific scenes that take place at the location.

EnemiesEdit

There are two general distinct approaches to enemy pages, based on whether the pages are parents, or individual ones. Parent pages and individual pages are recurring feature and specific feature respectively. A third approach is a distinct individual page for an enemy family within a game.

SummonsEdit

Summon pages are similar to character pages in that they cover the entire existence of the summon within a subseries as the parent page. They are outliad with:

  • A location infobox, usually {{Summon}} unless the game has its own specific infobox.
  • The Intro should briefly explain its role.
  • A Profile section (which can be split into Appearance and Personality subsections) which details the general appearance of the summon and any personality it shows in the story.
  • A Story section listing any roles it has within the story.
  • An Obtained section listing how it was acquired. If it contains spoilers for the main story, include it within the spoiler template and finish with {{endspoiler}}.
  • A Battle section listing how it fights in battle when summoned by the party. Describes its role in battle and lists its abilities.
  • An optional section for any roles it has outside of battle regarding teaching abilities or boosting stats.
  • A Boss section if it is fought as a boss.

Parent pagesEdit

The parent page contains:

  • The Intro describing the enemies' appearance, typical elemental affinities and status effects commonly used, if any, and notable subspecies. This section above it will have an image representing the general appearance of the enemy; typically, art is used to depict the enemy, but this is not necessary.
  • An Appearances section listing all the Final Fantasy titles the enemy has occurred in. Under each title is listed the enemy's appearance, its other variants, and traits of the enemy in the specific game.

The {{enemies}} template should be included on enemy parent pages.

Individual pagesEdit

  • The enemy infobox designed for the game, if applicable (see Category:Enemy Infoboxes).
  • The Intro should contain relevant story information or when the enemy is fought along with the information.
  • A Story section depicting its role in the story if a character page is not warranted (such as Astos).
  • In the case of some enemies, such as Final Fantasy XII enemies, an appropriately titled Bestiary Info should be added as well. In the case of Final Fantasy XII Marks, information about location of the petitioner as well as the Mark itself should be added, the battle strategy, the reward and finally, the bestiary info (see Gil Snapper for example).
  • A Formations section if the game has battles that take place off the field. Stats based on battles rather than enemies are listed here, such as ABP in Final Fantasy V.
  • A Locations section which lists all the sub-locations the enemy appears in, if the content is too much for the intro or infobox. Also lists which formations appear in those locations if they exist, or the amount or frequency of enemies in that area if enemies are found in the field.
  • A Stats section if the game in question has different stats per level and are not all displayed in the infobox.
  • A Battle section listing its battle attacks, movement and behavior. Additionally, a Strategy sub-section on how to beat it.
  • An AI Script section if one is known or available for the game.
  • Finally, a Related Enemies section, listing additional parts of a foe or additional enemies in a boss fight, palette swaps, and enemies with the same class and/or genus. Much better if there is already an in-game classification. This section will go below a "Gallery" section.
    • Should there be related enemies in more than one game in the same continuity (such as an enemy related between Final Fantasy X and Final Fantasy X-2), enemies from games other than the game the enemy of the page is should be listed under a sub-header within the Related Enemies section, sorted by game (See Adamantoise for an example).

A navbox is not necessary for singular enemy pages, but categorize them according to the relevant enemy categories.

Individual familiesEdit

  • The Intro should explain the game, how many members of the family exist, and related families.
  • If applicable, a Bestiary Info section.
  • A List of enemies section with bullet point lists of all enemies within the family.
  • A Related families with bullet point lists to similar families, such as palette swaps.

A navbox is required for the release.

JobsEdit

There are two distinct approaches, the parent page for recurring abilities, and the specific job page. The former is a recurring feature page, while the latter is a specific feature page.

Parent pagesEdit

For parent pages:

  • An Intro about the job's appearance in the series, with an overview abilities used, weapons equipped, physical appearance of the job class, and notable characters who have been in the job class, such as Kain Highwind as a Dragoon.
  • An Appearances section, which list appropriate traits for the job as it appeared in each game that had a job/class system only. Examples of these are Final Fantasy, Final Fantasy III, Final Fantasy V, Final Fantasy X-2, Final Fantasy XI, Final Fantasy XII International, and the Final Fantasy Tactics series.
  • An Allusions section, which lists any appearance within first-tier scope that might allude to the job.
  • If not already listed in its Disambig, an Etymology section with an external link, preferably to relevant name origin websites.

Specific pagesEdit

For specific job pages:

  • The Intro should say which game the job is from, any relevant story and points at which the job is aquired.
  • A Profile section giving a description on the job's costume design.
  • All of its Abilities, placed inside neat tables with relevant statistics and color coding.
  • Finally, a Gallery that showcases artworks related to the job class.
  • Optional sections include:
    • A Requirement section on unlocking Jobs - if and when the job needs to be unlocked.
    • An Equipment section.

Different games can have differing job layouts which are specific to that game, and the above guide should be followed only on a case-by-case basis.

Status effectsEdit

Make to focus on the status itself, not a spell that may share a name. A (status) tag should differentiate the article from a related spell, and contain:

  • An Intro which describes the general consequences of the status effect and whether it is positive or negative.
  • An Appearances section, which lists the specific effects of the status in each game with links to them on their list of status pages.
    • List all of the possible abilities, cures, items and any cause or relative of the status in a table.
    • This table should list, in order: the Game Element, its Type (Ability/White Magic/Weapon/Item/etc.), and its Effect.
  • A Gallery of characters under the status or status symbols.
  • Add the navigation template {{Status}} at the end of the page.

ElementsEdit

Element pages are designated with the (element) tag if another identically named page exists, and outlaid with:

  • The Intro should touch briefly on the element's history in the series, such as when it first was featured. The element's defining qualities and relationship with other elements should be mentioned.
  • A Recurring themes section that lists the element's representation by Abilities, Enemies, Equipment, and Summons throughout the series. This section should not list each example, but rather the most prominent.
  • The Appearances section lists each game that the element makes an impact in.
    • It lists any unique features of the element in that game that may not be as obvious or prevalent in other games.
    • A table listing all abilities, equipment, and items that are related to the element. The table should be ordered by Game Element (the thing that is related to the element, not the element itself), Type, and Effect.
  • The navigation template {{Elements}} at the bottom.

MusicEdit

A substantial amount of discussion have been initiated in the past to decide ways of writing music articles. As recently discussed, music articles have two different approaches, depending on content:

AlbumsEdit

It has been discussed that pages for original soundtracks and albums should generally contain:

  • The {{Infobox Album}} template placed and completed before the Intro.
  • The descriptive Intro, describing the album in general. This includes any relevant information such as production staff, release date and retail price.
  • The Numbered Tracklist that includes track names in both Japanese and English, track duration and, if possible, a description on track recurrence. Should there be no track recurrence, prose may describe track characteristics i.e. composer/arranger/artist involved.
  • External links that link first to official homepages, and then to any notable and relevant websites, such as, gaming news websites.
  • Place the navigation template {{Music}} and/or the relevant game template, if applicable, and the category "Music" and/or relevant game category as appropriate.

Individual tracksEdit

Articles for individual tracks should contain:

  • The {{Listen}} template, which houses a sample of the track. Refer to Working with Media Files on working with music samples.
  • The Intro that describes the track in general, including composer and/or artist involved, its occurrence in-game and the soundtrack, and description of the music, including leitmotifs and other relevant tracks, if any. Subsequent paragraph may include development notes.
  • The Game appearances section, which covers each appearance of the track on a Final Fantasy game title, and detailing any appearances on a "Soundtrack" or "Soundtrack PLUS" album.
  • The Arrangement Album appearances section, which covers each subsequent original arrangement of the track on a Final Fantasy music album.
  • The Live performances section, which covers each individual performance of the song at a concert or tour.
  • The Compilation Album appearances section, which covers each subsequent appearance of an arrangement of the track on a Final Fantasy music compilation.

Place the navigation template {{Songs}} and/or the relevant game template, if applicable, and the category "Music" and appropiate type categories depending on track's appearance in each game, e.g. "Aerith's Theme" will get categories like "Category:Final Fantasy VII Event Themes" and "Category:Theatrhythm Final Fantasy Curtain Call Battle Themes". There are three types of themes the Wiki recognizes: Event Themes, Battle Themes, and Field Themes, similarly to Theatrhythm Final Fantasy series.

PersonnelEdit

Personnel pages follow a similar format, and all contain the {{Personnel}} navbox at the bottom, and an appropriate category.

Voice actorsEdit

Voice Actor pages on the wiki are strictly related to the FFWiki's Scope. This means that, while coverage of the voice actors may reference their work outside the series, they should primarily concern work within it.

  • The Intro should mention their first and/or most notable voice acting appearances, and the character that the voice actor is most often associated with.
  • The Roles section should contain table(s) for their works within the Final Fantasy series.
    • The first row should be the Title of the release, the second should be the Character they played, and the third should be the Release year. The "Release" column should always state the year of first release of the language version, e.g. for Ali Hillis, though Final Fantasy XIII was released in 2009 in Japan, the first English release featuring her was in 2010 so that is the date given.
    • If they appeared multiple times within a subseries, and then sometimes outside the subseries, then creating a subheader of Roles with the subseries title is often preferred.
    • A Related games subheader can be used if the voice actor appeared within releases below the wiki's First Tier Scope.
  • A Background section should contain brief information on how the voice actor was chosen (if possible) and could mention briefly a few notable works of the voice actor outside the series.
  • An External Links section can link to the voice actor's Wikipedia, Twitter, and IMDb profiles.

ListsEdit

Most "List of" pages do not follow specific rules and operate on a case-by-case basis for the games, unless listed below.

Achievement listsEdit

As per most "List of" pages, a page listing the Achievements found in a game will be titled "List of [title] Achievements". However, if the game's achievements are titled differently, then replace "Achievements" with the different title. If two sets of Achievements are included with different titles, then both names should be included in the title (e.g. "Achievements and Trophies").

  • The opening intro must contain the number of achievements found within the game.
  • The first section should simply be List, as "of Achievements" is a tautology. It should contain a table with the following rows:
    • Name, a table header, the simple name of the achievement.
    • Icon, a 50px sized image of the achievement, but it should contain whatever image is common between all forms. For instance, with iOS and Android achievements; as the image in the picture is identical between both, that image should be used.
    • Description, the in-game associated description, using the quote class (|class="quote"|[description]).
    • Notes, explaining various information, tips for acquiring the achievement, and if the method of acquiring is ambiguous, contains details on how to unlock.
    • Value, if any achievements contain a certain value point; replace this with the value in question, for instance, Xbox points or PlayStation Bronze; if there are multiple values, include multiple columns for each.
  • A Gallery should only be included if there are valuable images of the achievements that are not found in the Icon row.

The navbox {{Achievements}} should be at the top of the page, as it is a sidenav. At the bottom of the page, the appropriate game navbox. The "Achievements" category should be used.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.

Also on Fandom

Random Wiki