Community Style Guidelines: Difference between revisions

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."
Anonymous user

Navigation menu