User:Joey Coconut1/drafts/Titles and article organization

Titles and article organization is the first article in the Manual of style series. it describes how to write titles for articles and sections of articles, what information to include on infoboxes, what infoboxes go where, how to format a lead section, how to arrange the rest of the sections in an article, and what categories to include on an article.

Article titles
A title should be a recognizable name or description of the topic that is natural, sufficiently precise, concise, and consistent with those of related articles. If the name does not display properly by default, use the displaytitle template and affix the proper title.


 * 1) Titles are written in Sentence case. The initial letter of a title is almost always capitalized by default; otherwise, words are not capitalized unless they would be so in running text
 * 2) Article titles are singular in form, e.g. Elytra, not Elytras.
 * 3) Avoid ambiguous abbreviations. Abbreviations and acronyms are often ambiguous and thus should be avoided unless the subject is known primarily by its abbreviation and that abbreviation is primarily associated with the subject. It is also unnecessary to include an acronym in addition to the name in a title. The only time in which where acronyms may be used is for parenthetical disambiguation where applicable
 * 4) Do not use A, An, or The as the first word
 * 5) Use nouns or noun phrases whenever possible
 * 6) Do not enclose titles in quotation marks, or otherwise include quotation marks in a title
 * 7) Do not create subsidiary articles. Do not use titles suggesting that one article forms part of another: even if an article is considered subsidiary to another, it should be named independently
 * 8) Do not use characters not on a standard English keyboard
 * 9) In titles describing two or more closely related or complementary concepts, the concepts should be arranged in alphabetical order and separated by 'ands', AVOID the use of commas

Lead section formatting
An article's content should begin with an introductory lead section—a concise summary of the article—which is never divided into sections. The remainder of the article is typically divided into sections.

Initial templates
Initial templates should be affixed at the very top of an article.
 * If an article is about a base, and there is a World download of the base that can be linked in the infobox, affix the template
 * If the article has a name especially similar to another article, begin with a disambiguation hatnote
 * If an article is deemed too short to provide adequate coverage of a subject, it is deemed to be a Stub; affix the template

Infobox guidelines
Infoboxes follow the Initial templates near the top of the page, and should provide as much information as possible that is relevant to the available fields in said infobox.
 * 1) Infoboxes, images, and related content in the lead section must be right-aligned
 * 2) Infoboxes are required for pages about bases, players, groups, conflicts, or Incursions. These situations encompass the vast majority of page topics
 * 3) If a page arises that a template does not properly apply to, it is acceptable for it to not have a template. If this becomes a chronic issue, more templates and guidelines will be added
 * 4) It is important that all possible applicable information be included on an infobox, especially a pertainant image
 * 5) Whenever a date is put in an infobox, Template:Date and age is to be used

Section headings
The heading on a section reflects the contents of said section. The proper use of headings is essential for proper organization of a page.

Section heading formatting

 * Section headings should follow all the guidance for article titles (above), and should be presented in sentence case
 * Use equals signs around a section heading: ==Title== for a primary section, ===Title=== for a subsection, and so on to ======Title======
 * Do not skip levels
 * Do not use =Title=
 * Spaces around the title (== Title ==) are optional and ignored
 * Do not color titles
 * Do not use unusual fonts for titles

Section heading contents
Section headings should:
 * 1) Be unique within a page, so that section links lead to the right place.
 * 2) Not contain links, especially where only part of a heading is linked.
 * 3) Not contain images or icons.
 * 4) Not contain citations or footnotes.
 * 5) Not redundantly refer back to the subject of the article
 * 6) Not refer to a higher-level heading, unless doing so is shorter or clearer
 * 7) Not be numbered or lettered as an outline
 * 8) Not be phrased as a question

Section contents
The contents of a page are the page itself, organization of the page is extremely important.
 * The contents of a page should properly reflect the title affixed to said page
 * While generally the best way to maintain proper flow to a page is to organize it chronologically, this is by no means required, especially when the subject matter would otherwise jump back and forth. Use common sense.

Categories
Categories go at the end of a page, and are meant to group articles with other articles that cover similar subject matter. While Categories will doubtless change and increase in both count and scope, 2 types of categories (known as primary descriptors) MUST be affixed at the bottom of each page, those are the following.

Year
The category denotes the year an article took place in. For players, it is when they joined. For bases and groups, it is the year of foundation. For events, it is the year in which it took place. For exploits, it is the year they were widely used on the server. This tag MUST be placed on all pages unless they are on in-game items, machines, or anything else otherwise existing outside of the chronology of the server.

Other descriptors
The following listed categories are only to be affixed to pages relevant to said categories.

Players
All pages about players are to recieve the category. Beyond this, there are many other categories that can be found by going to the players category. As many tags can be added as are applicable to the subject of the article.

Bases
All pages about bases are to receive the category. Beyond this, there are many other categories that can be found by going to the bases category. As many tags can be added as are applicable to the subject of the article.

Groups
All pages about groups are to receive the category. Beyond this, there are many other categories that can be found by going to the groups category. As many tags can be added as are applicable to the subject of the article.

Events
All pages about events are to receive the category. Beyond this, there are many other categories that can be found by going to the events category. As many tags can be added as are applicable to the subject of the article.

Exploits
All pages about exploits are to receive the category. Beyond this, there are many other categories that can be found by going to the exploits category. As many tags can be added as are applicable to the subject of the article.

Wiki information
All pages pertaining to things that have happened on the wiki, the rules, staff functionality/voting procedure, or the Manual of style are to receive the category. Pages making up the style guide are also to receive the Manual of style category.

Miscellaneous
All pages not covered under the above categories are to receive the category. Oftentimes there will be no further categories available for contents falling into this classification, but for some types of pages there are further subcategories.