Neptunia Wiki:Manual of Style

This page will give an idea of how to write articles so they are consistent with many of the similar articles.

General article guide

• Article title must follow the subject's official name. It must also be written in Singular instead of Plural - exceptions are only when the article is (or meant to be) a List.
  • Articles about a video game, anime, book, album, or Drama CD should have the {{Italic title}} template on the top of the page.
  • For subjects without official names, please use the most accepted title.
• Always include basic information about the subject when starting an article. The first sentence should detail the name, classification, and game (or compilation, or series if it recurs). In succeeding sentences, the place where the thing is found, what the thing looks like, and its purpose within its appearance.
• When writing the article content, titles for video games, anime, books, albums, and Drama CDs should be written in italics, e.g. Hyperdimension Neptunia while song, chapter and episode titles should be with "quotation marks", e.g. "Ryuusei no Bifröst"
• The definite article (the) and indefinite articles (a/an) should be avoided in article titles except if they are used as the official title.
• Please write in third person: use "the player" instead of "you". Disregard this when writing walkthroughs.
• Please avoid writing abbreviations for game titles, e.g "HDN RB1" - it should be "Hyperdimension Neptunia Re;Birth1", and gaming systems e.g. "PS" - it should be "PlayStation". Exceptions are for spaces where the full name would not fit or would cause things to look cluttered.
• Follow the official game title letter for letter and word for word when typing (e.g. Megadimension Neptunia VII instead of Hyperdimension Neptunia Victory 2 or Hyperdimension Neptunia Re;Birth1 instead of Hyperdimension Neptunia RE;Birth 1).
• Wikilinking is limited to the first occurrence of the word or phrase (the exception is if the word or phrase has also been linked in an infobox; in that case it is fine to link it once again within the article content).

What should an article have?

For games

Game pages can vary by content, whether they have DLC, Achievements, etc. The {{Parent Tab}} template should be included in every game page, including subpages.

An example of what a usual parent tab template has:

{{Parent Tab
|backcolor     = #8A2BE2
|altbackcolor  = transparent
|textcolor     = #fff
|alttextcolor  = #D15FEE
|bordercolor   = #8A2BE2
|activeborder  = #8A2BE2
|borderradius  = 6
|height        = 2.2
|maxwidth      = 15
|tab1          = Overview
|tab2          = Gameplay
|tab3          = Downloadable Content
|tab4          = Trophies
|tab5          = Image Gallery
}}

• the descriptive Intro, describing about the game in general. Some snippets from the content of the article may be written here.
• the Story header to explain the general plot of the game.
• the Gameplay header, 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 list of Characters including a short description and also Voice Actor(s). Each character must be categorized by title or role.
• the Music header, describing the composition, composer, soundtrack, including main themes, adding in links to the respective music article.
• A Videos header for videos related to the game such as trailers, promotional videos, or other official content.

For characters

All character articles follow the same format; however, some things are exclusive to playable characters or characters belonging to certain games. Parent tabs are dimension specific in accordance to the main series, and as such not all characters will have the same parent tabs.

For example, a character who has a meaningful appearance in all the dimensions would have a parent tab such as this:

{{Parent Tab
|backcolor     = #8A2BE2
|altbackcolor  = transparent
|textcolor     = #fff
|alttextcolor  = #000
|bordercolor   = #8A2BE2
|activeborder  = #8A2BE2
|borderradius  = 6
|height        = 2.2
|maxwidth      = 15
|tab1          = Overview
|tab2          = Super Dimension
|tab3          = Hyper Dimension
|tab4          = Ultra Dimension
|tab5          = Zero Dimension
|tab8          = Image Gallery
}}

Whereas a character who has only had a meaningful appearance in one dimension would have one such as this:

{{Parent Tab
|backcolor     = #8A2BE2
|altbackcolor  = transparent
|textcolor     = #fff
|alttextcolor  = #000
|bordercolor   = #8A2BE2
|activeborder  = #8A2BE2
|borderradius  = 6
|height        = 2.2
|maxwidth      = 15
|tab1          = Overview
|tab2          = Quotes
|tab3          = Image Gallery
}}

• All characters use the "{{Infobox character}}" template.
  • For characters that have different forms, such as Goddess forms, the "{{Infobox character forms}}" template is used instead.
• 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 header, which is then divided into each form of the character if applicable. This section includes:
  • An Appearance header to describe how they appear in their releases in terms of features and attire. If the look varies between games, then a sub-header will be created for each outfit in which their appearance is not the same.
  • A Personality header to describe their personality. If the personality varies between games then a sub-header will be created for each game in which their personality is not the same.
• A Story section that explains the role of the character in the series of events that involve them. This section is divided up by each game.
• A Trivia section.
• Navboxes that link to other characters.

For skills

Skill pages are NEVER grouped together as one. Each skill page will ALWAYS be named in relation to their character, skill type, and video game.  (e.g. Command/Combo/Victory/Neptune). Also, for the sake of consistency, each page will be named the same despite the content (e.g. Each page related to skills will be named as Command/[Skill Type]/[Video Game]/[Character]) even if the character themselves have only one skill and not several.)

Skill pages have:

• The intro describing who's skill page it is, what type of skill page it is, and for which game. (e.g. This page lists Neptune's Combo Skills in Hyperdimension Neptunia Victory.)
• It must use the specified template created for that particular skill type for that particular game.

For equipment

Character specific

Equipment pages are NEVER grouped together as one. Each equipment page will ALWAYS be named in relation to their character, skill type, and video game. (e.g. Costume/Victory/Neptune). Also, for the sake of consistency, each page will be named the same despite the content (e.g. Each page related to equipment will be named as [Equipment]/[Video Game]/[Character]) even if the character themselves have only one piece of equipment of that particular type and not several).

• The intro describing who's equipment page it is, what type of equipment page it is, and for which game. (e.g. This page lists Neptune's Costumes in Hyperdimension Neptunia Victory.)
• It must use the specified template created for the equipment for that particular game.

General

For general equipment such as ornaments and armors, the setup is mostly the same with only minor differences. Armor and Ornament pages are categorized by the type of Armor or Ornament it is and by which game. (e.g. Armor/Victory/Bangle or Armor/Victory/Armlet). For the sake of consistency, each page will be named the same despite the content (e.g. Each page related to equipment will be named as Armor/[Video Game]/[Ornament Type]) even if the page itself only has one piece of equipment of that particular type and not several))

• The intro describing what equipment page it is, what type of equipment page it is, and for which game. (e.g. This page lists the Ring Armors in Hyperdimension Neptunia Victory.)

For locations

Location articles have two different approaches, depending on content:

Nations

For pages about nations or similar locations:

• A descriptive intro about the place
• The {{Land location}} template if an image is available
• A Story header for a summary about its role during the game(s) or other media.
  • Each story summary must be categorized by individual sub-headers for each game or miscellaneous media.
• A Trivia header.

Dungeons

There are two types of dungeon pages:

• Dungeon List: lists all the dungeons on the page in table format along with their inhabitants and other brief relevant information.
• Specific Dungeon: Pages for a specific dungeon. Dungeon Specific pages include:
  • A descriptive Intro about the dungeon.
  • If a map of the dungeon is available use the "{{Infobox dungeon}}" template.
    • The map must have indicators marked for treasure, warp points, save areas, switches, etc.
  • An Items header that lists all the available items in table format.
  • A Monsters header that lists all the enemies and their drops in table format.
  • A Story header that summarizes the events that take place in this dungeon, if any.

For game stories

When writing a story summary page for a game, they should ALWAYS be in a subpage of the main game page (e.g. Hyperdimension Neptunia/Story). They should also have the main chapters in order with full summaries for each one.

For game story chapters

A summary page for a specific chapter in a game may vary on its content. For starters, a usual chapter page has the following:

• A Plot section.
• New characters appearing.
• New quests.
• A list of side events, if any.
• Key Items acquired.
• CGs viewed, if applicable.
• The game's Navbox.

For gameplay summaries

Gameplay summary pages can vary whether it's for a game or a character. When writing about them, they are necessarily in a subpage of the main page (e.g. Hyperdimension Neptunia/Gameplay).

For video game gameplay summaries

Gameplay summary pages for video games are documented by the order listed below:

• Core gameplay (e.g. battle system, dungeon system)
• Featured mechanics
• Other mechanics not documented from official website

For character gameplay summaries

Summaries about gameplay of a specific character should have the following information:

• Sections of each game this character is playable in, if writing in their own subpage.
• Raw level parameters (meaning no equipment) that go up to the maximum level possible.
• The character's traits.
• A non-biased summary of how this character plays in-game.

For bestiaries

Bestiary pages should have the following information:

• A list of enemies with information regarding their habitat, item drops and variants, if any.
  • If enemies are grouped in a specific type (e.g. Humanoid), they should always be in their specified section and list.

For specific enemies

If by any chance a page for a specific enemy is necessary, they are ALWAYS named in relation to the video game they appear in (e.g. Bestiary/HDN/Dogoo). Also, for the sake of consistency, each page will be named the same despite the content (e.g. Each page related to the enemy will be named as Bestiary/[Video Game]/[Enemy]).

Specific enemy pages have:

• An infobox displaying the enemy's data before the Intro (e.g. {{Infobox Enemy}} or if for a specific game, {{Infobox Enemy [Game name]}}).
• A descriptive Intro about the enemy.
• Behavior of the enemy and its variants, if any.
• Related enemies.
• A trivia section (optional).

For music

Music articles have two different approaches, depending on content:

For albums

Pages for original soundtracks and albums should generally contain:

• The Infobox "{{Infobox album}}" placed and completed before the Intro.
• the descriptive Intro, describing the album in general.
• the Numbered Tracklist that includes track names, composer/arranger/artist involved and if possible track duration.

For individual tracks

• The Infobox "{{Infobox song}}" placed and completed before the Intro.
• the descriptive Intro, describing the song in general.
• A Lyrics header.
  • Lyrics are separated by the categories Romaji, Kanji, and English.
  • use the poem tags for each separate category of lyrics and label them accordingly when using the tabber tags.

The following is an example of how it should look.

RomajiKanjiEnglish

Romaji
Lyrics
Here

Kanji
Lyrics
Here

English
Lyrics
Here

For anime episodes

Pages about anime episodes should have the following information:

• An infobox (e.g. {{Infobox episode}}).
• A descriptive Intro with the first premiere date.
• A summary of the episode.
• The key events happening in that episode.
• The setting(s) of where the episode takes place.
• The list of characters, arranged in the order they appear in.
• A gallery header.
• A trivia header.

For books

Pages about books, such as manga and light novels should have the following information:

• An infobox (e.g. {{Infobox book}}).
• A descriptive Intro about the book.
• A story section, if any.
• A list of characters.
• A list of volumes or chapters.

For individual chapters

Pages about chapters in a book should have the following information:

• An infobox (e.g. {{Neptunia Manga Chapters}}).
• A synopsis or summary about the chapter.
• The key events happening in that chapter.
• The list of new characters, arranged in the order they appear in.

When writing an article

Verb tense

To determine which tense to use in articles, it is logical to describe events happening in-game in the present tense; even if a game was released decades ago, it still performs the same today as it did on release. Therefore, to simplify:

• Use present tense to describe plot and events as it happens in-game, including gameplay.
• Use past tense to describe flashbacks and events that happen prior to the game's plot.

The same applies to describing real world events. When talking about game development, releases and/or promotions, use a tense appropriate for the time period in which the event occurred eg "The PlayStation was launched in 1994" or . When describing the product itself, use present tense eg. "Hyperdimension Neptunia Re;Birth1 uses the Remake System." Exceptions are for unreleased products that use future tense, and unfinished products that use past tense.

Spelling

There have in the past been edit wars over the territorial spelling of a word (i.e. words spelled differently in between Europe and the United States). It used to be that we're not arrogant and we have no intention on starting a territorial war over something stupid like spelling, and if you had come across a word spelled the way it is in another country (for example if you see "color" spelled as "colour" or vice versa), you would have left it as it is. I.e. the person who inserted the word initially will decide how it's spelled.

However, due to consistency, "American English" spelling is the accepted language of the wiki.

Point of view

On most Wikis, there is a policy to give a "Neutral Point of View" (NPOV). This is not the case here when writing story sections of specific articles. The point of view MUST reflect how the events unfold from the article's subject's perspective. For everything else, the article must maintain NPOV.

Dates

When adding a date to an article, such as a release date, the standard practice is to omit ordinal suffixes (-st, -rd, -nd) and to use the {{Date}} template e.g. {{Date|2013|December|26}} will output as 2013 December 26. If a specific day has not been confirmed, the day parameter should be omitted e.g. {{Date|2013|December}} will output as December 2013. This should be followed both in info tables and general article information.

Working with media files

Adding images

The general practice would be to start Image placement on the right side by adding "right" in the image coding as in "[[File:Example.jpg|right]]". The next image would then be placed on the left - "[[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]]".

Image galleries should be created when a number of images in a section clutter the layout. Image galleries 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>