Draft:Project Games/Structure

This is an instruction manual describing the conventions that Bulbapedia follows when writing about the Pokémon core series games. If there are any unresolved questions regarding adherence to this style, please consult an appropriate staff member or raise the issue on the article’s talk page.

General conventions

The {{Project Games notice}} should be included in all articles under Project Games for consistency and navigation, along with {{Core series}}. Incomplete articles should also be tagged with {{stub|Game}} to identify areas that need expansion.

Infobox guidelines

Place the {{Infobox game}} template at the top of each article with key details, and include all the relevant information in the infobox:

  • English and Japanese names
  • Release dates
  • Platforms, developers, and publishers
  • Ratings (ESRB, PEGI, etc.)
  • Separate Japanese and English box art images and captions for each version, represented with its distinguishing elements (e.g., mascots, version colors).

In the case of contradictory information, contributors are encouraged to use "footnotes" to provide clarity and maintain accuracy for additional context:

  • Conflicting dates: For example, when a game has multiple release dates due to announcements, distribution methods (e.g., mail-order vs. retail), or re-releases.
  • Contradictory official sources: If official materials present differing information, clarify which source is being cited and provide context for the discrepancy.

Article structure

The structure of a Pokémon core series game article should have a good readability flow, starting with the correct headers for the sections. The headings and subheadings must follow a logical hierarchy, starting with level-2 headings (==) and progressing to level-3 (===) or level-4 (====) as needed. Avoid including links or unnecessary formatting within headings. Keep the section naming concise and descriptive. For extensive topics such as major game mechanics in detail, consider splitting content into sub-articles. Provide a concise summary in the main article, linking to the detailed sub-articles for further reading.

It is generally a good practice to follow this format for clarity and consistency:

Introduction

The introduction should provide a concise overview of the game’s key features, its notability in the Pokémon franchise, and its significance in the core series without duplicating the full details. It must establish context and relevance for all readers, regardless of their familiarity with the series.

  • Start with the official English and Japanese titles of the game.
  • Specify the console(s), release date(s), and the relevant Pokémon generation.
  • Highlight any novel game mechanics, regional details, or noteworthy features.
  • Ensure that all major points in the lead are expanded upon in the body of the article.

Plot

  • Provide a concise and chronological summary of the game’s narrative. Ensure each paragraph develops a single idea, with clear transitions between points.
  • Use the {{spoilers}} template to indicate sections with significant plot details.
  • Avoid overly long paragraphs or bulleted lists that may disrupt readability, and divide the plot into logical subsections, where applicable, such as:
    • Main storyline
    • Subplots (e.g., Victory Road, Path of Legends)
    • Post-game content
    • DLC or expansion content

Features

  • Detail new gameplay mechanics (e.g., Terastal Phenomenon) and major innovations (e.g., open-world exploration, Paradox Pokémon).
  • Include information about version-exclusive Pokémon and features, if applicable.

Compatibility

  • Explain how this game interacts with others in the series, such as trading, battling, or content unlocking.
  • Highlight tools like Pokémon HOME and Pokémon GO, and describe save data bonuses where relevant.

Localization changes

  • Document localization differences or quirks in a dedicated section. Prioritize changes that affect gameplay, the player experience, or cultural references.
  • Use bullet points for clarity and avoid overly detailed technical explanations.
  • For example, describe notable changes in dialogue or cultural references between regions (e.g., 'Onigiri' changed to 'Donut').

Reception

  • Summarize critical reviews from notable outlets (e.g., Famitsu, IGN) and community feedback in a balanced manner. If reviews conflict or the reception is mixed, provide a fair summary.
  • Highlight both the positive (e.g., innovative gameplay) and criticisms or controversial aspects (e.g., performance issues), and any key point of fan reception, if relevant.
  • Present official sales figures, if available, to show the game’s commercial performance.

Staff

Include developers, publishers, and other key contributors to the game.

Music

List details of the game’s soundtrack, notable tracks, and composers, if available.

Version history

Include a summary of updates, patches, or post-release changes.

Gallery

Game articles typically feature several relevant artworks or images; use galleries to showcase visual elements, such as:

  • Include official box art, screenshots, and promotional artwork relevant to the game.
  • Position images close to the relevant text they illustrate, and provide clear, informative captions that explain their significance.
  • Avoid using too many decorative or redundant images that do not add value to the reader's understanding.

You can implement the <gallery> tag by using:

<gallery>
File:ExampleBoxArt.png|Caption
</gallery>

Trivia

  • Trivia should emphasize meaningful or unique facts about a game.
  • Avoid generic or overly specific technical details unless they are highly notable (e.g., glitches or missing Pokémon mechanics).
  • Highlight translation-related quirks only if they provide insight into localization processes.

In other languages

Add translations in an 'In other languages' section, following Bulbapedia’s standard langtable format.

See also

Note the relevant articles from Bulbapedia here, such as Walkthrough for the respective game.

References

Add {{reflist}}, if references are used in the article.

External links

Provide links to official websites, trailers, or other credible resources.

Categorization

Ensure articles are assigned to relevant categories:


<ENDS HERE>

As a new section on the main Project Games page
Abbreviated

It is generally a good practice to follow this format for clarity and consistency, but it is not a hard-and-fast rule:

==Introduction==
==Plot==
==Features==
==Compatibility==
==Localization changes==
==Reception==
==Staff==
==Music==
==Version history==
==Gallery==
==Trivia==
==In other languages==
==See also==
==References==
==External links==