Editing Guidelines

From MHWiki
Revision as of 05:38, 6 November 2023 by Admin (talk | contribs) (Created page with "One of the goals of this wiki was to start over from a clean slate, as such, editors should follow these guidelines to ensure everything is in order: *'''No inline css''' (style="......") unless absolutely necessary. *'''No customizing the colors of tables''', to make sure everything works with any future themeing. *'''Keep images to a minimum''', host space is limited: **'''One set of Item Icons''', following the style of World and Rise, for now (SVG Format). **'''One...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

One of the goals of this wiki was to start over from a clean slate, as such, editors should follow these guidelines to ensure everything is in order:

  • No inline css (style="......") unless absolutely necessary.
  • No customizing the colors of tables, to make sure everything works with any future themeing.
  • Keep images to a minimum, host space is limited:
    • One set of Item Icons, following the style of World and Rise, for now (SVG Format).
    • One set of weapon and armor renders for each: the entirety of 1st and 2nd generation and Frontier, Tri, P3rd, 3U, 4U, GU, World Iceborne and Rise Sunbreak.
    • Only one render per monster unless the design changes drastically between generations (Rathalos, Diablos).
    • Only one screenshot per Location (for now), unless the design changes drastically between generations.
    • Monster Hunter Now-related pages should use World Iceborne renders and icons where possible.
    • Any other spin-off game, such as Monster Hunter Online, Monster Hunter Explore, Felyne Diary or Monstie Drop are to be worked on once the core games have been fleshed out.
  • Monster Hunter Frontier content must use official names when possible and clean, direct translations otherwise, do not marry the wiki to a single translation project.

File Nomenclatures

Following the same as the old wiki, files should be named in the following way:

[Game,Generation]-[Subject] [Render, Screenshot, Icon] [Number].[Extension]
  • Game or Generation: Shorthand for each game (MH1, MHFU, MHP3), or broad generations (1stGen, 2ndGen, 3rdGen).
  • Subject: Monster name, weapon class, locale name.
  • Render, Screenshot or Icon: Depends on the image.
  • Number: Starting from 0000.
  • Extension: File extension.

Monster Pages

Monster pages will contain the following information:

Intro (The Velocidrome is a Bird Wyvern introduced in Monster Hunter.)

Description

In-game descriptions of the monster.

Equipment

Weapons and Armor paths commonly associated with that monster.

Game Data

Per-game information regarding the monster, such as breakables, variations, HP and status resitances.

Notes

Miscellaneous notes.

See Also

Related monsters.

Weapon Pages

Weapon pages will contain the following information:

Intro (The Iron Sword is a Great Sword introduced in Monster Hunter.)

Game Data

Expandable tables containing per-game data, including raw damage, upgrades, materials needed and such.

See Also

Monsters whose materials are used, other weapons of that category.


Location Pages

Intro (The Forest and Hills is a location introduced in Monster Hunter.)

Description

Detailed description of the locale, keep speculation to a minimum.

Game Data

Per-game lists of gatherable items, veggie elder trades and such.

See Also

Monsters associated with that locale, for example.