PikminFanon:File guidelines

From Pikmin Fanon
Pikilogo.png
This page contains information relating to Pikmin Fanon's policies and guidelines.
Pikilogo.png

Uploading files, including images and audio files, is possible at Pikmin Fanon although it is restricted to autoconfirmed users only. This help page is a set of guidelines for contributing files to the wiki. For help on how to place files in articles, see here.

Uploading

The most common files on the wiki are concept art and screenshots from the Pikmin games, but box-shots, maps, diagrams, and other relevant files are allowed too. The following are instructions and guidelines on how to properly upload a quality file, and failure to follow them could result in its deletion. Pikmin Fanon uses a custom script on the upload page that makes some steps automatic and simpler, amongst other improvements. Although unlikely, the script might not be running, but that should not matter.

You may upload sound effects or parts of songs, but only if adding them improves the understanding of a subject. For parts of game tracks, they can not be over thirty seconds in length, and should not have sound effects. When adding an audio file to an article, use {{listen}}.

Additionally, you can upload images that are not related to the wiki or the series, especially if you only plan on using them for yourself, but remember to not overdo it. We're not an image hosting platform. You may only have five user images at a time.

Filetypes

Your file must have a proper format. The most common filetypes used on Pikmin Fanon are:

  • PNG: for maps and diagrams, images with a transparent background, or images where it's very important to keep a high quality on the small details.
  • JPG: for screenshots and photos. All instances of "JPEG" become this.
  • GIF: for animations and simple images.
  • SVG: a vector format for diagrams and logos.
  • OGG: for audio files.

If an image you are about to upload has many small details that need to be kept, try to keep it high-resolution. If not, try to avoid uploading images that have a high resolution; resize if necessary. If you are ever unsure, always save an image as a PNG file, as this is a lossless file format, which means that you will not lose image quality, and someone else can alter the image for you.

File name

Files should be named after the article's title, even if the name of the subject differs from it, such as if the subject has a new name given to it by its creator. Please do not upload files with extremely long names, gibberish names, or names unrelated to the main subject. If you think that somebody could upload a similar image in the future, or has already, disambiguate your file's name some more, like adding the initials of a game's name to it. If someone's game has the same initials as yours, please include your full username after it.

Think about it this way: if you wanted to search for images with certain content, your image should appear on the search results. It won't show up if its name is just garbage.

Description

Quickly describe what the image contains or what the audio file is for. You don't need to go into a lot of detail if you don't want to. Try to link to relevant articles, also.

Categorization

All files should be in the proper categories. If on the upload page, you see boxes asking you for the image type, the game, the area, and so on, that means that Pikmin Fanon's custom upload script is running and you shouldn't worry about categorizing manually. Otherwise, read on.

You should place the file in the applicable categories. Whenever possible, it should be under the most specific, or deepest, categories available. Use the following checklist to decide what categories to use. See here, and in its subcategories, for a complete collection of file categories.

Type
Subject

Game

What game, if any, the file is being used for.

Source

Where the file originates from.

License

Each type of file requires a different licensing template. For most types of files, the license is chosen automatically when you select the appropriate type, but if you are ever given the question about what the license should be, please pick from these options, which could vary depending on some conditions:

  • "Video game screenshot" for when it's an in-game screenshot.
  • "Concept art" for official concept art or artwork made by the developers of a game.
  • "Audio" for audio files.
  • "User image" for an image that is irrelevant to the series, and is to be used by users only.
  • "Texture" for an image that comes directly from the game's files or is created specifically for a game.
  • "Public domain" for when the image doesn't have any licensing. Only pick this if you know what you're doing.
  • "Copyrighted" for files that belong to somebody else, but are meant to be used fairly on the wiki.
  • "Free licenses" for specific licenses, when you know what they are.

Videos

Videos from many sorts of hosting sites can be embedded on a page using EmbedVideo extension. To learn more about it, click the provided link.

The entire skeleton looks like this:

{{#ev:service|id|dimensions|alignment|description|container|urlargs|autoresize|valignment}}

Below is an explanation of each part of the entire code:

  • service: the platform the video is hosted on.
  • id: the raw ID of the video.
  • dimensions: the size, in pixels, of the embed container. Can be typed as <width>, <width>x<height>, or x<height>.
  • alignment: horizontal alignment. Possible options are left, center, right, and inline. Inline allows multiple videos to be embedded side by side without forced line breaks.
  • description: displays the provided description under the embed container.
  • container: specifies the container type to use for the embed. Inputting frame wraps the embed in the standard MediaWiki thumbnail box.
  • urlargs: allows additional arguments to be appended to the generated embed URL.
  • autoresize: automatically resizes the videos when their size would cause them to break out of their container. To disable, input false.
  • valignment: vertical alignment. Possible options are top, middle, bottom, and baseline. Using this parameter forces the horizontal alignment parameter to be inline.

The number of videos used in articles should be kept to a minimum, and used only where necessary and useful.