User:Pinkachu/Sandbox/Manual of Style

This Manual of Style outlines standards for clean, consistent formatting for wiki content on Skyforge Wikia. This is a guideline and can be occasionally overridden where circumstances warrant it, and will never be perfect for every situation. Please when possible keep to the advice outlined in this article, so others may use your edits as an example for their own articles or sections.

These guidelines are a summary of the most important guidelines for the Skyforge Wikia. Additional help and guidance can be found on Wikipedia at Wikipedia Manual of Style.

Article layout
In wiki editing, one of the most important fundamentals is how to structure a wiki article. Structure is a powerful thing as it dictates the order and flow of the page, and can influence what people contribute, where it goes, and how it might be written. Structure has the equal power to confuse people just as bad writing does. A well structured article is more likely to maintain a high quality, long-lived page and source of information.

Wiki articles and pages are organized into sections, in a hierarchical structure similar to an outline. Wherever possible you should use a logical structure. Each section should start with an introduction, similar to the start of the article itself, and then have its own subsections below it if any.

Prefer using shallow structures over deep ones with many levels of sub-sections. Too many nested sections can lead to a overly confusing pages. See for more info on writing section headings. Most importantly, keep your layouts consistent, within a page and across pages. The following manual of style sections will offer some good advice on keeping your articles clean, consistent, and clear. They are generally presented in the order in which they should appear in an article.

Top non-article content
Non-article content, such as disambiguation and article message boxes, should be located above the lead. If no template, box, or precedent exists for a "non-content" type top message, then a simple indented italicized note may be used, which is preferably a complete sentence but does not necessarily have to be. See also, and , below.


 * Were you looking for Oceanic realms, or the Realms list?


 * Were you looking for Oceanic realms, or the Realms list?

Infoboxes
Infoboxes are generally boxes that usually appear at the top-right corner of the page, which summarize data relating to the article. These are placed immediately underneath any top non-article content with no extra lines or spaces. As a side-note, the item tooltips that can be seen when hovering over certain kinds of links, are actually constructed directly from these "page infoboxes".

Lead section
An page should begin with a short introductory lead section, just before the first section heading. 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. The lead should not have its own explicit  or any section header.

Lead page title
If possible the title of the page should lead the first sentence of the article. The exact page title should put in bold using three apostrophes, like  the first time the article mentions the title. King Banana III was King of Fruits during and after the Second War, and can now be found in Galeras, in the region of Alizar.
 * King Banana III was King of Cereal Bowls during and after the Second War, and can now be found in Galeras in the region of Alizar.

Lead bolding
Avoid other uses of bold in the first sentence, except when denoting alternative titles without links. Follow the normal rules for italics in denoting books or other important works. Do not make or put links in the emboldened page title in the article's lead sentence, or make bold links normally in general text. King Banana II, or King Banana, was King of Fruits during and after the Second War, and is an often referenced character in the Guide to Banana Wars trilogy. King Banana can now be found in Galeras, in the region of Alizar.
 * King Banana II or King Banana was King of Fruits during and after the Second War, and is an often referenced character in the Guide to Banana Wars trilogy. King Banana can now be found in Galeras, in the region of Alizar.

Lead italics
In the lead sentence of a page, putting part or all of the bold title in italics will mainly apply only the titles of books and games whether fictitious or real. The example below shows the whole name in italics with the page name in bold.
 * The Guide to Banana Wars trilogy consists of

Bananas of Wrath, War of the Bananas, and The Banana King books.
 * The Guide to Banana Wars trilogy consists of Bananas of Wrath, War of the Bananas, and The Banana King books.

Table of contents
A table of contents (TOC) will automatically appear default as left-aligned above the first explicit section heading, in articles with three or more user sections. This default behavior is considered standard style, and usually should be followed as such. However, the TOC can be altered using page options in wiki text, sometimes referred to as magic words.


 * to force the TOC to a certain position
 * to completely remove the TOC from a page
 * to force the TOC to float right, and/or to a certain position. See tocright.

A right-aligned TOC should only be used if it is very long, like over 15 entries, and an information box is not on the right side already. If you are having trouble positioning images, TOC or infoboxes, or find that you are having to change TOC behavior across multiple pages, feel free to contact any moderator or admin for help.

Article main content
This is where the main article content for the page would go, which should begin with a section heading, and is the part that covers regular page material. The content continues with main article text, content, and additional main article sections, and so on. For information on writing the actual article content itself, see the section below.

Sections
The article main content contains its own sections. Section headers should be un-decorated with no extra italics, bold, html markup, etc., and should use spaces between the section title and the == markup. Empty sections without wiki-text comment or stub-section markers, should not be left on finished pages; they can always be added later.

Section names should generally be cased like regular sentences, where only the first word is capitalized, unless is a proper name. Sections in wiki markup should have an empty line before them, and no empty lines before the section content text or markup.

After the article main content sections, other standard page sections sometimes called footer sections, can be placed to hold standard types of ancillary data. These should be always be placed after the regular article body, farther down the page. Lead introductory text.

Section name
Regular section name.

King of Cereal Bowls
Proper name section name.

Boiler-plate
Below is a basic standard skeleton for making a page, show in in wiki text, and illustrates some of the parts that surround the main article content (some not yet discussed). Many types of articles, such as Tradeskill infobox, have standard predefined skeletons, or similar boiler-plate for placing around main article content.

Media - images, videos, other
The Media section is the first standard footer section, and is for placing general media, such as images, videos, or others like audio, that relate in some way to the article subject. If there is no general media then this section can be omitted. See below for more detail.

The media section for a page should generally be organized such that
 * 1) At least two videos or images can be placed side by side at minimum width.
 * 2) The tag is used to encourage others to add media to the page
 * 3) Each media type should normally go in a separate sub-section under the media section.
 * 4) Rules for Media footer sections are an exception, for section spacing, and the Media sub-sections and the media section are all jammed together, with no empty lines.


 * Note: media can also be placed elsewhere such as in infoboxes and along the article main content, and should follow whatever way makes sense for that context.

Example media section with images and widths for only 2 videos:

Appearances
Appearances is a standard footer section, and is used on character or NPC articles to list which media (books, games, etc.) that character has appeared in. Unless need this type of disambiguation, this section is not added.

In Skyforge
Found among the trees and sandy shores of Lanber Forest.

In Skyforge: Even Wilder
Still found among the trees and sandy shores of Lanber Forest, but more appealing.

In The Card Game
Found as the third most top banana often waging war with I and II. Is found also on page 8 of the TCG handbook.

Patch changes
The Patch changes footer section is used to list and consolidate notes and statements about any patch and hotfix made to the article's topic. On pages that have very few notes or patch changes, these changes can be consolidated into and share the more general Notes footer section. Each separate item must be in list format using the * (asterisk) wiki markup, with a space between the * and the list text.

Regardless, entries should use the patch template to note the exact if known, and should briefly quote patch notes or My.com forum posts about hotfixes whenever possible. For when no note is available or for undocumented changes discovered by players, then a brief description of the change should still be made. References are not needed if the change is an official patch note, a Carbine post (though the post should be linked), or if the change is documented elsewhere on Skyforge Wikia.

Patch changes

 * - Bananas were augmented to be more appealing.

Interwiki links
The very special Interwiki links footer section is one of the two last standard sections, is usually for links to other language pages, and should be added at the very end of the article wiki text. Like Navboxes and Infoboxes, they do not normally have their own a section header. If there are no very special Interwiki links already, this section can be ignored. These special links should have at least two extra line-breaks between them and the end of the last section, or one extra line-break if after a Navbox section, and then should be placed one under the other with no wiki list markup or otherwise. See also Help:Interwiki links, which inthe general case can also be used in elsewhere in wiki text.

This footer section is different than the See also or the External links sections, and consist only of very special links, like links to other language versions of the current page. Other language links use special namespaces and look like, which would link to a French Skyforge wiki site's version of this site's   page. These bottom footer Interwiki links also work specially with the Wiki itself, similarly to how categories work, and will automatically show at the bottom of the page in a special looking list that the user can click on. However unlike categories, when an article page is opened again for editing the bottom Interwiki links will still appear in the actual wiki text just as you left them. So here good formatting is important for future travelers.

Categories
Adding categories to a page, adds that page to a category list. Category can be added directly to wiki text using markers, and these marker should always be placed in this footer section. Category footer section should have at least two extra line-breaks between it and the end of the last section, or one extra line-break if after a Navbox or Interwiki link, and then should be placed one after the other on one line, with no extra wiki list markup or otherwise. See Help:Category links. See Category policy for category naming. See Special:Categories for full list of existing categories.

These category markers take the form of  which marks a page for a category, whereas a wiki link to the Bananas category page with the list would be , with an extra : (colon) in front. These are very easy to confuse. Unlike links in the Interwiki links footer section, these category "markers" will always seem to disappear from the page text when opened again for editing. It is important follow the specific rules above, so that changes between revisions can be followed easily and when comparing page history. Placement is important here for future travelers as well.

Note that categories can later be removed (or edited) using the right tool bar when editing a page, and can be also be added simply at the bottom of any regular page.

Writing

 * "I believe the road to hell is paved with bananas..."
 * - Banana King

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, and you have to skillfully balance both.

General

 * Keep your writing concise. Don't use two words where one will do, or use fewer words. Keeping it simple will make it easier to understand for wider variety of audiences, and easier to expand upon later. Use complete sentences in regular text.


 * Check your spelling and grammar. Write the way you would for a class paper or a newspaper article.  Use correct grammar and spelling for whatever context you are in.


 * Don't use "texting type". Don't use 'u' or '2' in place of 'you' or 'to'.


 * Keep all of the topics you cover within the scope of the article. For example, a detailed history of the Banana elves on the page about Banana II is unnecessary, and should probably should go on its own page. Whereas similar text more centered on the relationship between them would be OK. Consider the article's title as your point of origin and write from that perspective, and make liberal use of the wiki's inherent ability to link more detailed articles or external sources for more information.


 * Write from an impersonal perspective. Don't write with the word "I". For example don't write, "Banana II was a ..., as far as I know." In general avoid drawing attention to the wiki article author, yourself, as much as possible. See also SkyforgeWikia:Neutrality policy.


 * Be bold in updating pages. If you know something is wrong or think something could be worded better, or if an article has a glaring deficiency, fix it. Even if your first attempt isn't golden, the fix it as best can. Later you, or someone else, can come along and fix it better. If you look at a set of changes and as a whole and can say, "Yes, this is progression.", then you are golden. Don't be afraid to make mistakes trying.

Grammar
It's hard to build good sentences without at least a few basic rules. Since a wiki article must be reasonably clear across wide audiences, various levels of understanding on a given topic, and possibly numerous edits across many authors, wiki editors must continually strive for clean grammar for clear communication. Remember that context is important, and good grammar depends on the words around it.

If ever unsure, always feel free to leave a message with an admin or moderator, to or join Wiki Chat for quick help or discussion. Skyforge Wikia is a friendly environment with active resources for help. It is far better, and much less work in the long run, to correct issues early on.

Capitalization

 * Titles - Proper titles on names or Sir names, such as lord, king, or arch-nana, must start with a capital letter when used as a part of a proper name, like "King Banana" and not "king Banana". Words used for proper titles when used generally, should be in regular lower case or cased normally, like "Banana II is a powerful king." Actual full proper titles, such as of an office, or honorary, are also treated as proper nouns, like "King Banana II is the current King of Fruits."  A title of work like "Bananas of Wrath" or "The Banana Wars", use same capitalization as original work, which is often simply in familiar title-case. See SkyforgeWikia:Capitalization policy.


 * Nicknames - Colloquial nicknames, like ones not actually found in Skyforge Wikia or other game materials, should be avoided, like saying "Nana-B", "B'nan", or "B II", instead of "Banana II". These can sometimes in violation of NPOV or SkyforgeWikia:Neutrality policy. It may however be OK to make a note in the Notes footer section well-known, pervasive, commonly used names in the community, which is also outside of the article body proper.


 * Classes - Game classes, like esper or warrior, should only be capitalized when used as a proper noun, or as a part of someone's name, like "Go fight, Warrior." versus "That warrior is fighting."

Italics

 * Titles of work - Italics are used for complete titles of work, such as name of a book or game. However, titles of sub-sets, like articles, chapters, and other short works are not italicized, but are instead enclosed in double quotation marks. For example the book Bananas of Wrath and the chapter "Rise of Bananas", could be written in wiki text as, which would be displayed as "Banana II is often referenced in Bananas of Wrath, especially in the "Rise of Bananas" chapter."

Dates

 * Shorthand - Dates in short format, like ones in used in tables, should be written formatted as "YYYY-MM-DD" to aid sort-ability, with a complete numerical year, month, and then day, separated with dashes, for example 2022-04-01. Dates formats of "MM-DD-YY" or "DD-MM-YYYY" are not used on Skyforge Wikia, as values would always be suspect, and possibly confusing and ambiguous for either the United States or more international standards readers. Shorthand dates should never be used in regular wiki paragraphical text.


 * Longhand - Dates in longhand, as written regular in article sentences, should be written in the form of "D Month YYYY" with no extra punctuation, for example, 1 April 2022. This date format should not be used in tables, or similar non paragraph format text, as can make adding columns and having enough room more difficult, and makes much harder for reader to scan table or grouped text for information. Use is discouraged in wiki lists, but acceptable.


 * Abbreviated - Dates when abbreviated, as with a shortened Month part, should be written in the form of DD-Mon-YYYY, with day, short month name, and then full year, separated with dashes, and no other punctuation, for example 1-Apr-2009. This abbreviated form is most appropriate for lists, such as in paragraph form, wiki bulleted lists, or otherwise, or where space is at a premium. This format also is acceptable in most cases, including tables, lists, and in paragraphs.

Quotations

 * Regular inline - Short or regular quotes, those under 4 lines in regular paragraphs, should be formatted using enclosing quotes using regular English grammatical rules, for example: King Banana then said, "I believe the road to hell is paved with bananas..."


 * Regular long - Long quotes, those over four lines in regular paragraphs, should be formatted as an italicized block quotation using, and indented from both margins and should not be enclosed in quotation marks, for example: King Banana then said, A very long quote that goes on for an while and is too big to show here.... . This format should not have any extra indentation or other formatting, such as wiki indentation markup using the initial : (colon) wiki code.


 * Stylized introductory - Stylized quotes, the kind suitable for page or section introduction, should normally be formatted using wiki indentation markup with initial : (colon) and enclosing italics and quotes, then a - (dash), a space, and then the author attribution, for example: . This format should be considered decorative, and as non-article content similar to the  section above.
 * "I believe the road to hell is paved with bananas..." - Banana King
 * The attribution can also be placed on a separate indented line with, or without, its own italics as:
 * "I believe the road to hell is paved with bananas..."
 * - Banana King

Tense

 * Regular article - Most articles should be described as facts, so writing should use present or future tense, which primarily involves choosing correct verbs like is or can be, for example: "Banana II is the King of Fruits." and "Only lemons can be this evil."


 * Quoted material - In quoted material Tense, or other grammar, should be left as is. This extends to any wiki reference material, such as stories from the game, patch notes, EULAs, outside technical docs, or other text on Skyforge Wikia for reference. It may seem strange to single out Tense for not altering quoted material, however is one of the most prevalent, persistent, and difficult to verify editing mistakes.


 * Terminology - Terminology and special wording, such as technical jargon or technical documentation, specific game terms, or well known and expected constructs, often use special Tense and should like quoted material, be left grammatically intact and unchanged, for example "Cooldown reduced", "has been renamed". Any surrounding text should still follow correct site grammar.

Media
Media like images and videos can be placed anywhere along the main page content, or in the general Media footer section.

Links and Galleries
Media is placed by using  style links, or the   extension. For Links, images and videos will by default "float", or allowing text or other images to stack against or wrap around. For Galleries, media displays in a grid, and don't "float", just displaying across the page, and normally only used in the Media footer section.

The format for file name and description is similar for a Galleries and Links both with an name and an optional description, with | (pipe) parameter separator. For Links, only the file name prefix "File:" should be used, not "Image:", and galleries only use the base file name, with no "File:" or "Image:" prefix at all, as shown below. A third type of placement is allowed using the {{media template, which is useful for displaying large single images, images in a pseudo-table, or for special occasions or formatting.

In Links: In a Gallery:

Using {{t|media}}: {{media|File:BananaTCG.jpg|Banana I in TCG|width=600}} {{media|File:SirLemon.jpg|Sir Lemon in TCG|width=600}}

Note for Links that a  can be placed any time afterward to clear and stop additional text wrap. Adding |none| parameter, instead of default '|left|' or '|right|', will stop the image from floating at all, no longer needing {{clr}} at all. A gallery tag always clears left and right after, and never needs {{clr}}.

Media footer section
See above.


 * Placement - New media should normally be placed in the Media footer section. Any media placed along the main body, should be removed from the footer section. Any media being removed from along the main body, should be moved to the Media footer section, and not just be removed from the page.


 * Sub-sections - Each type of media should be placed in its own sub-section, with a its own section header. Each section should use a plain wiki gallery or galleries, using the  tag extension.


 * Parameters - As few parameters as possible should be used, normally using only the defaults. Videos can be adjusted for better visibility using the widths parameter. Image widths should be left default.


 * Widths - The gallery widths parameter sets width for each thumbnail in the grid. Image galleries should not normally have the parameter set. Video galleries should use widths of 265, which allows 2 wide at minimum page width and 3 wide a when window is maximized to 1600. Values other than the recommended 265 are sometimes useful. Allowable values for media footer section:
 * 3 at minimum, and 4 at 1600 - Gallery with widths=195
 * 2 at minimum, and 3 at 1600 - Gallery with widths=265 (default expected choice for videos in gallery)
 * 2 at minimum, and 2 at 1600 - Gallery with widths=310 (only if only 2 media are likely for a long time)
 * 1 at minimum, and 2 at 1600 - Gallery with widths=415
 * 1 at minimum, and 1 at 1600 - Link or {{Media (preferred) with |600px

General Media extents
Following is a long list of wiki page inherent extents, which applies to all media anywhere in Skyforge Wikia.


 * In Row or Grid - The current minimum page width (MPW) can fit 2 videos or images (media) side-by-side, with a safe maximum width of 330 pixels using 'small' spacing, and 310 pixels using a 'medium' spacing. The current page width in a 1600px window (1600 wide PW) can fit 2 media side-by-side, with a maximum width of 415 using 'medium' spacing, and only 1 across at MPW. The current 1600 wide PW can fit 3 media side-by-side, with a maximum of 265 using 'medium' spacing, and 2 across at MPW. The current 1600 wide PW can fit 4 media side-by-side, with maximum width of 195 using 'medium' spacing, and 3 across at MPW. Gallery supports maximum widths of 480, but should not be used, as is a big enough jump over 415 and won't wrap to 2 across for 1600 wide PW.


 * Isolated single - For images or videos (media) when isolated, such as not floating along page text or in a gallery tag, the maximum acceptable and suggested width is 600. This will still fit on 640 wide constrained screen with page chrome and borders. Media in the Media footer section that is single, may use this format if is the only media of that type and/or is otherwise justifiable, like is a very special media that doesn't have another reasonable place on the page.
 * Inline with main text or standard sections - The current minimum page width in the top section, with no infobox, allows for reasonable size of 300 to 400, with default standard of 350, for float left or right, and only for a single video or image (media). For floating media left or right along content in regular sections, the current minimum page width allows for a 150 to 250, with default standard of 200.

General Media formatting



 * Media along main text and sections - Images and videos (media) actually along the article main body should normally float to the right. Left is also allowed, but rarely used. Wiki Links are preferred, with Media tags as optional replacement. Links float to the left by default, and need to have |right| added as a parameter anywhere before the description. Media template does not float by default, and needs |right| as 4th parameter or |align=right added. Use of |thumb| for Links is allowed, but discouraged in the top section. Use Media template where border is needed without the upload credit. Place media in wiki text just under section headings, not in middle of paragraphs.


 * Galleries outside the Media footer section - Galleries are encouraged outside the Media footer section and are useful for a set of images or videos (media) that especially relate to an article topic, are unlikely to change, and are not intended to accept general user media. These should follow the Media footer section formatting, and with any other options as necessary, and should have the  parameter added to remove the add button to be clear is not for regular user submission. Galleries are encouraged over tables for media sets, that only include media, as they work with flex layout and are generally much easier to maintain for regular wiki editors.


 * In Tables - Tables are useful for mixed media and titles using lighttable, and allow advanced positional features, like centering. For these the Media template is preferred over using actual tables, where table stylized headers, borders, and advanced positioning are needed, and are much easier to maintain than tables. Gallery is still preferred for general sections media over either.

Floating Links and Media (shown above):

Section header


King Banana II was King of Fruits during and after ....

Gallery outside media footer (not shown):

Stylized and positioned isolated media: Single:

Side by side 1 (different tables):

Side by side 2 (same table, one with old YouTube ID):

Single:

Side by side 1 (different tables):

Side by side 2 (same table):

Media only table (non-preferred):

Images
For the full guidelines on adding and managing images on Skyforge Wikia, see SkyforgeWikia:Image guidelines.

Videos
For the full guidelines on adding and managing videos on Skyforge Wikia, see SkyforgeWikia:Video guidelines.

Tables
Tables should use the "lighttable" class design when possible and by default, and should include as little "fancy" formatting as possible. Tables can also be made with alternating row background colors by adding "zebra" class, and sortable by adding a "sortable" class.

Basic table
Below are examples for basic Skyforge Wikia tables. It is recommended to use the "zebra" class to alternate row colors (preferred), or alternatively can add the "alt" class to a row for tables that are very simple and not get updated frequently. For tables of only 2 or 3 rows, the 'alt' and 'zebra' may be skipped. More information about wiki tables in general can be found on Help:Table.

...or:

Section headings
Section headings are used to create actual wiki page sections with titles. Each section heading organizes a chuck of article body, and creates its own entry in the page's Table of Contents (TOC). Sections using section headings allow for simultaneous editing by authors on the same page, where editing a different sections won't conflict when saving. Liberal use of section headers is encouraged. See, , and for related specifics.

Section types

 * The top section - Each page has one implicit section at the very top, that does not have a section heading where short introductory sentences are usually placed, and does not get an entry in the TOC, also as explained better in section above. Do not use single   section headings in normal wiki text or articles. The page header already uses an a level one header, and using them creates a section with no edit link, and skips the TOC.


 * Main section headings- Any major chunk on a wiki page should have its own section and top level section heading, created by using == (two equal signs) on both sides of section name, with a single space in-between. Main section headings with == (two equal signs) are generally equivalent to  in html.


 * Sub-level section headings - Often a sub-chunk under a major chunk should have a title and its own section and section heading, and is created similarly by using === (three equal signs), or more, on both sides of section name, with a single space in-between. Sub-section headings with === (three equal signs) are generally equivalent to  or greater in html.

Main section heading:

Section name
Text

Overall page section and sub-section headings: Text in top section.

Section name
Text

Sub-section name
Text

Sub-sub-section name
Text

Sub-section name
Text

Section name formatting

 * Links in headings - Links should generally not be placed on section headings. Links in headings are more difficult for a reader recognize, and often confuse edit history because of the link code. Consider instead putting the link word in the first or second sentence of the section and linking it there.


 * Capitalization - Section names should generally be cased like regular sentences, where only the first word is capitalized, unless is a proper name. For example use "Founding and history", not "Founding and History"; but "King Banana II" and not "King banana II".


 * Special characters - Avoid where possible special characters in headings, such as an & (ampersand), a + (plus sign), {} (curly braces), or especially [] (square braces). In place of the ampersand, use the word "and", unless the ampersand is part of a formal name.


 * Brevity - Keep heading names short and simple to make easy to spot scanning down a page, and to keep the page TOC to a reasonable width and easy to read. Avoid unnecessary words; redundancy; articles like a, an, and the; pronouns; words in the article title or parent sections, and so on.


 * Duplicate section names - Avoid giving identical titles to different sections, especially under the same part of a heading tree, as they are used for anchors for links to part of a page. For example, the name in, displayed as , is likely not used anywhere else.

King Banana II
King Banana II was....

King Banana II (King of Fruits)
As ....

Section style and formatting

 * Skip the line before - Each section heading should have the line before it skipped in wiki text, so that the start of a new section in code is clearly visible.


 * Skip no line immediately after - Each section heading should have no line skipped immediately after it skipped in wiki text, so that the start of a new section is more easily distinguishable from a single short line paragraph, and so that on pages with many very short sections the page is less lengthy to scroll up and down, or more easy read all together.


 * Empty sections - Empty sections should generally be removed until there is actually content for the section. See Boilerplate sections and Stub sections just below.


 * Boilerplate sections - Sections may be marked with wiki text comment, like, when content is eminent or possibly needed to bring an article out of Stub status. Smaller and sparse comments are encouraged in general for special communication, especially when a page is in transition. These comments are only visible when editing text.


 * Stub sections - Sections themselves may also be marked with Stub-section when content is eminent or when an editor notices section is in a stub like undeveloped state. Marking a section as Stub-section is an encouraged alternative to marking an entire page as stub.

Some previous text

Section name
More text

Section name
<!- Place list of Chua food here. Remove section if page no allow Chuas -->

Disambiguation
A disambiguation line is sometimes put at the beginning of an article, see, or section heading to link to another article with the same or similar title or otherwise disambiguate the following content.


 * Format - Like with any other special notation, the line should be italicized and indented once.


 * Semantics - Most usually should contain the phrase, "Were you looking for X?", like "Were you looking for King Banana I?"


 * Were you looking for King Banana I?


 * Were you looking for King Banana I?

Article message boxes
Article message boxes are generally used as a temporary notice on an article page in the form of a Page message box or Section message box, and it may flag up some issue or notify the user about some special aspect of the article or section

A list of message box templates can be found in Category:Article management templates.

Placement

 * Location - Article messages and message templates should be placed at the very top of an article or section, before all text and images, and other templates or infoboxes. The article message boxes should only be at the top, and never be part of the article content proper, unless is in the form of a Section message box which should only be at the top of the section just underneath the header.


 * Stacking - Article message boxes are generally come in the form of templates, like Stub, and are designed to stack like banners at the very top of a page or section. They can be placed one under the other at the top in wiki text.


 * In redirects - For pages that are redirects, like ones using #REDIRECT Some page wiki magic, message boxes should be placed just below the redirect, otherwise the redirect will cease to function. As with other wiki text placing boxes like delete should leave the underlying redirect and other text intact.

Some text

Section name

 * 1) REDIRECT Some page

Types

 * Message box categories - Most message boxes for pages or sections, place a page in one or more wiki categories for various reasons, like Category:Pages proposed for deletion or Category:Article stubs.


 * Boxes of notification - Some message boxes are simply notifications and used as to inform readers on special circumstances or otherwise as a convenience, like boxes stating Guild page user content, noting unreleased content subject to change, or Spoiler, silly, or lore page.


 * Boxes of action - Some message boxes are calls for action or change, and placed to help manage the page and alert readers and editors, such as Stub and Delete. Each of these has specific rules and remedies and which be explained or linked to policy pages on the template page itself.


 * Referenced text - Placing a change request type of Article message box is usually a notice being placed in lieu of actually making changes then. For example when placing delete, no content should actually be removed. See DNP for any exceptions.


 * Boxes order - Boxes of action should always be placed above Boxes of notification, like Stub should always be placed above Spoiler. Delete or Speedydelete should always be placed above all other notification boxes.

Delete Spoiler Some page that maybe should be deleted, about things that never really happened with King Banana II, but can see that text it still here and that the Delete message box is above the Spoiler message box.

Design

 * Reference boxes - Article message boxes for Page and Section message boxes should be based on the current forms of Stub and Stub-section respectively


 * Box icons - Should use the File:IconInteract.png or similar and following the icon sizes illustrated in stub and stub-section.


 * Box categories - Each article message box should place a page in at least one distinguishing category.

Conclusion
Every article can be improved, even this one. Following these guidelines will not ensure a perfect article every time, but it will give the article most of what it needs to start, and will give readers familiar constructs to follow. It's ultimately the job of the editor to pull it all together, and in whatever way is the most reasonable for any given content. Go forth and be bold.