Style Guide

Summary

This page has a collection of tips to add new content to the wiki.

Pages

Naming convention

• Make sure the name of the page identifies clearly what it will be about.
• Avoid creating pages for content that already exists or that could be part of an existing page.
  • For example, characters such as Fenrir that appears in Nexomon 1 and Nexomon: Extinction don't have separate pages for each game because he doesn't change at all, it's only a different story. However, regions such as the Frozen Tundra (Nexomon - Nexomon: Extinction) have different pages for both games because the content of those regions is completely different between them and their locations don't match at all.
• Pages can't have repeated names. If you have a situation where you need a similar name, use a suffix to distinguish it from the original page.
  • For example, we have Bedam and Bedam (Extinction).
• If you're creating a page that is part of a similar set of pages, make sure it matches any naming conventions that those may have. This helps a lot for automatically adding pages to categories based on a part of their name.
  • For example, all skill pages have the (Skill) suffix, such as Tackle (Skill) or Scratch (Skill). Character pages look like Deena (Character) or Amelie (Character).

Good practices

• Keep the content you write as neutral as possible, without introducing personal opinions that can't be backed by events within the game or references.
• When writing trivia, base it on evidence as much as you can.
  • If it's something that happened in-game, this is a valid source.
  • If there is some speculation to it, make sure to indicate it.
  • If you've found that information from an official source, such as comments from one of the game developers or designers, reference it.
  • Avoid being subjective with parallels between in-game designs with other pieces of media unless those were stated by the designers as references.
• Make use of the title hierarchy set by default in Fandom. This is important so the Contents table is generated correctly.
  • For example, this page has sections with Heading titles, subsections with Sub-heading 1 titles and then Normal text.
• Use single images if they relate to a specific paragraph. Make sure you don't abuse those to a point where the text becomes unreadable.
• Use galleries to add a long set of images that aren't related to a specific paragraph within the page. These are found within the Insert -> Gallery option. This keeps them tidy an looks better on mobile.
• Always add relevant categories to pages. This helps to find them. Avoid creating new ones unless it's strictly necessary (e.g. a new type of content, new game, etc.). Don't create a category that only applies to one or two pages.
• If you have a type of content that repeats across multiple pages with the same style and behavior, use templates. We have specific templates for most of the wiki's content, so it is recommended to check pages similar to yours to copy the template from there.
  • For example, we have templates for Nexomon data, locations, evolutions, skills, maps, items, etc. Those templates can have variants for Nexomon 1 and Nexomon: Extinction. They're usually distinguished by the EX suffix. Check Spink, Lume or Cursed Tower South to see them in action.

Images

Naming convention

• Put a meaningful name. Avoid using default names that you may have from taking a screenshot of the game.
• Use spaces or underscores if you separate words in your image name. The wiki will automatically transform spaces into underscores. It is recommended to avoid using dashes in the names, especially if the image might be used as part of a template.
  • For example, in Frozen City Camp, there is a template that references the Snush Companion item. That image is named Snush_Companion.png. If the image name was Snush-Companion.png it would appear as a broken link, because the template automatically transforms the Snush Companion text, replacing the space with an underscore and adding the .png at the end.
• Use PNG images unless a different format is required (for example, GIFs). The wiki uses the file extension as part of the image name. Templates expect images to have a PNG extension so, if they try to reference a file that has a different extension, they won't find it.
  • With the previous example of the Snush Companion, if the file was uploaded as a JPG, the template would show a broken link. And we can't change the template to use JPG because then the PNG images wouldn't work.
• If your image is part of a bigger set of similar images, make sure you follow any naming conventions those may have.
  • For example, images like Cloddy only use the Nexomon's name. But if it's the cosmic variant, then it'll be Cloddy_Cosmic.

Good practices

• Use transparent images and try to get them with the highest resolution possible.
• It is possible to extract transparent in-game images of static elements if you play on PC (e.g. items, companions, dialogue portraits of characters, etc.). If you have the files but you don't know how to extract them, refer to the video in this comment or contact User:MissKolala. Please, don't contact for images that are already in the wiki.
• It is unknown how to extract in-game images of Nexomon because the ones from the game files are all animated. When extracted, they are "in pieces", and it's not clear how to put them together.
• Avoid repeating images. If you want to improve the quality of an existing image, use the Upload a new version of this file option within the File history. If the image you're trying to upload is very similar to an existing one, the wiki will warn you. Unless there's a justified reason to have a repeated image, don't upload it again.
• If there's a lot happening in the image, make sure to add a description so it's easier to find for other users.
  • For example, in Friends Defending the Player the description specifies the characters that appear there. This way it's easier to find it later if we want to include the image in any of those characters' pages.
• If you're using in-game images, make sure to select the Fair Use license while uploading them. If you forgot or if you find any images that need it, you can select Edit Source in the image page and add {{Fairuse}} there. This will add the license.

Templates

Naming convention

• Use a meaningful name, preferably short but without risking confusion with other templates.
• If you're creating a set of related templates, make sure to name them in a way that shows they're related.
  • For example, for item location tables we have three templates with similar names that indicate each piece: ItemListStart, ItemList and ItemListEnd.
• If you're creating a template that is very similar to another but with a key difference, try to name the new one similarly and use a suffix to distinguish them.
  • For example, for the list of available skills there are two templates: SkillListEntry and SkillListEntryEX. The former is used for skills in Nexomon 1 while the latter is used for skills in Nexomon: Extinction, so their names are pretty similar except for the EX suffix. The key difference that made it worth to create a new template is that Nexomon 1 doesn't have Speed and Crit Chance data. We could have used if-else statements, but this risks breaking existing pages, so creating a new template was safer.

Good Practices

• Avoid creating a template to format content that will only be used in one or two pages. If you want to style a table that is only going to be used in a single page, you can style it on the page itself using the Edit Source.
• If you create a new template, classify it and add documentation to it. Many of our existing templates don't have those, but it's a good practice if we want other people to understand how to use them. Take WildNexomonEx/entry as an example.

Redirects

These are a special type of page that are usually created when we Move a page to rename it. Take the Nexolord Tower - Crossroads for example. If we select Edit Source in a redirect page, we can see it's just a normal page where the content has been replaced with:

#REDIRECT [[Page name to redirect to]]

If we need to create a redirect manually, we can replace the page content with the above line pointing to the exact name of the new page. However, be careful when working with them. If you chain several redirects they will stop working and the links will be broken. This usually happens when we rename multiple times a page (2-3 times is enough). A way to fix this situation is by modifying the broken redirect pages so they point to the final expected page. After you've fixed the broken redirects, make sure to delete the unnecessary ones or mark them for deletion if you don't have enough permissions.

Deleting content

To be able to delete content you will need to have a role with enough permissions, which is something usually reserved for regular contributors. If you do, the Delete option will show in the three-dots menu of the page. If you don't have enough permissions, what you can do instead is marking the page for deletion. Select the Edit Source option of the page and add the following template:

{{Delete}}

The pages marked for deletion can be later reviewed by someone with enough permissions for their removal.