Community Style Guidelines: Difference between revisions

From Victory Belles Community Wiki
Jump to navigation Jump to search
fandomVB>Sovereign
No edit summary
fandomVB>Sovereign
Line 4: Line 4:


Where possible, a belle/ship name should retain any accents or other markings of its native language.  For example, [[Algérie]] retains its accented letter.
Where possible, a belle/ship name should retain any accents or other markings of its native language.  For example, [[Algérie]] retains its accented letter.
==Belle Detail Pages==
To keep large data-dumps off the main belle pages, each belle has (or will have) a "DetailsPage" that contains her stock configuration, information about vestures, and default armor statistics.
Add the following code to any belle without a detail page.  Generally this should be placed after the Gameplay Information section.  This adds a box with an automatically-generated link which invokes a pre-loaded template to build out the belle's detail page.
<pre>
{{NoBelleDetailsPage}}
</pre>
=== Empty Categories ===
Some belles have nothing ''at all'' in a certain category--for instance some destroyers have no secondary battery, most battleships do not equip torpedoes.  See [[Victory Belles Wikia:NoStockPage|this list]] of templates for use on belle detail pages in these circumstances.


==Belle Name, Ship Name==
==Belle Name, Ship Name==
Line 48: Line 59:
* Minimize image use.
* Minimize image use.
* Prefer more rows, fewer columns (templates tend to encourage a two-column layout which fits well on mobile).
* Prefer more rows, fewer columns (templates tend to encourage a two-column layout which fits well on mobile).
* Consider moving ''extremely'' long tables of data (such as statistics) to a separate statistics page for the item in question.
* Consider moving ''extremely'' long tables of data (such as statistics) to a separate statistics page for the item in question.  Belle detail pages and a preloaded template already exist for that situation.


== Pages ==
== Pages ==
Pages should be derived from a template if at all possible.  This helps standardize the wiki's appearance.
Pages should be derived from a template if at all possible.  This helps standardize the wiki's appearance.


As part of mobile first design, pages should use as many infoboxes and templates within themselves as possible.  This game contains a large amount of data that needs to be presented in a unified, mobile-friendly format.  Infoboxes allow corralling said data while maintaining a mobile-friendly experience.
This game contains a large amount of data that needs to be presented in a unified, mobile-friendly format.  Tables allow corralling said data while maintaining a mobile-friendly experience.


Minimize image usage on main pages.  For example, if a belle receives a "skins" page, go nuts with images there, but not on her main page!
Minimize image usage on main pages.  For example, if a belle receives a "skins" page, go nuts with images there, but not on her main page!
Line 70: Line 81:
* The default "Unknown" if the line can be filled in the future, but the information that would populate it is not currently available.  For example, a belle whose voice actress has not been credited publicly at time of page creation would be listed as ''Unknown.''
* The default "Unknown" if the line can be filled in the future, but the information that would populate it is not currently available.  For example, a belle whose voice actress has not been credited publicly at time of page creation would be listed as ''Unknown.''
*"None" if the line can be filled, but isn't.  For example, a belle whose stock main battery contains an open but empty RDF slot should list RDF as "None."
*"None" if the line can be filled, but isn't.  For example, a belle whose stock main battery contains an open but empty RDF slot should list RDF as "None."
*"N/A" if the line applies to ''other'' uses of the infobox (as part of the template), but the line is not valid for the infobox in question.  For example, a belle whose stock main battery configuration has a locked RDF slot would list this as "N/A."
*"N/A" if the line applies to ''other'' uses of the table (as part of the template), but the line is not valid for the table in question.  For example, a belle whose stock main battery configuration has a locked RDF slot would list this as "N/A."

Revision as of 12:01, 30 September 2021

This is intended to be an overview of community-driven stylistic decisions for the Victory Belles wiki. As items arise, they will be added.

Accents and Language Marks[edit | edit source]

Where possible, a belle/ship name should retain any accents or other markings of its native language. For example, Algérie retains its accented letter.

Belle Detail Pages[edit | edit source]

To keep large data-dumps off the main belle pages, each belle has (or will have) a "DetailsPage" that contains her stock configuration, information about vestures, and default armor statistics.

Add the following code to any belle without a detail page. Generally this should be placed after the Gameplay Information section. This adds a box with an automatically-generated link which invokes a pre-loaded template to build out the belle's detail page.

{{NoBelleDetailsPage}}

Empty Categories[edit | edit source]

Some belles have nothing at all in a certain category--for instance some destroyers have no secondary battery, most battleships do not equip torpedoes. See this list of templates for use on belle detail pages in these circumstances.

Belle Name, Ship Name[edit | edit source]

Wiki Page[edit | edit source]

The current (September 2021) consensus is that the page should be the name of the ship the belle represents without any national modifiers (like "USS") or hull designators (like "CA"). For example, Admiral Graf Spee follows this convention while USS New Orleans CA-32 does not. New pages should follow this convention. Existing pages may be re-created under this convention.

Character[edit | edit source]

The current (September 2021) consensus is to refer to the belle in the same way as the page.

"Maury is one of the starting belles available to the United States faction."

Ship[edit | edit source]

The current (September 2021) consensus is to refer to the historical ship using its national designator ("USS," "HMS," etc.) and hull number if needed (in cases of multiple ships sharing the same name).

There is no consensus on whether historical ship names should be italicized when used in the wiki. When a consensus is reached, this page shall be updated.

"USS Maury (DD-401) was one of the most decorated ships of World War 2."

Capitalization[edit | edit source]

There is no current (September 2021) consensus on whether "belle" and "morgana" should be capitalized or not when used on this wiki. However, once a consensus emerges, wiki editors should strive for consistency. This page will be updated once a decision is made.

There is no current (September 2021) consensus on capitalization of specific game terms. For example, when discussing a belle's main battery, should it be written "Battery I" or "battery I?" Should nouns like "vestures" be capitalized?

Equipment[edit | edit source]

Equipment names in Victory Belles can be very complex and lengthy, with a single digit denoting two different pieces of otherwise-similar equipment.

Wiki Page[edit | edit source]

No consensus yet exists (September 2021) as to how to name pages for equipment.

Leading Zeroes[edit | edit source]

If the game uses a leading zero on a displayed decimal value (such as armor quality), the wiki should retain the leading zero when listing it.

Mobile First[edit | edit source]

As a game primarily directed at mobile users, this wiki should strive to present information in a way that is optimized for mobile devices.

  • Think vertical.
  • Avoid horizontal scrolling, even a little.
  • Minimize image use.
  • Prefer more rows, fewer columns (templates tend to encourage a two-column layout which fits well on mobile).
  • Consider moving extremely long tables of data (such as statistics) to a separate statistics page for the item in question. Belle detail pages and a preloaded template already exist for that situation.

Pages[edit | edit source]

Pages should be derived from a template if at all possible. This helps standardize the wiki's appearance.

This game contains a large amount of data that needs to be presented in a unified, mobile-friendly format. Tables allow corralling said data while maintaining a mobile-friendly experience.

Minimize image usage on main pages. For example, if a belle receives a "skins" page, go nuts with images there, but not on her main page!

Table/Information Box[edit | edit source]

Table vs. Information Box[edit | edit source]

The Infobox is a stock class on Fandom, and is restricted to loading on the right. The Belle information box is the only (September 2021) current example.

Almost all the templates for tables on belle "detail pages" are two-column setups with optional column headers and an optional title overall. These work well on mobile and don't look horrible on desktop.

General[edit | edit source]

When a value for a named line in an existing information box/table is not included, it will automatically populate with Unknown.

Text for an empty value should follow these guidelines.

  • The default "Unknown" if the line can be filled in the future, but the information that would populate it is not currently available. For example, a belle whose voice actress has not been credited publicly at time of page creation would be listed as Unknown.
  • "None" if the line can be filled, but isn't. For example, a belle whose stock main battery contains an open but empty RDF slot should list RDF as "None."
  • "N/A" if the line applies to other uses of the table (as part of the template), but the line is not valid for the table in question. For example, a belle whose stock main battery configuration has a locked RDF slot would list this as "N/A."