Image use policy

Privacy disclosure statement: for image file formats JPG and PNG, metadata in the uploaded image is publicly visible on the Great Library of Greyhawk and GreyhawkOnline. This includes location, the date and time the image was recorded, and the make and model of the camera or smartphone. If this is unwanted, remove this metadata from the image before uploading, wherever possible.

Copyright images

All images uploaded must follow copyright policy and Fan Content Policy guidelines.

Image location

In the body of an article, images should always be placed as thumbnail images in the right margin, unless they would extend the page past the end of the text.

In such cases, images should be added in a "Gallery" section, just before the "Bibliography".. For example:

== Gallery ==
 <gallery>
 File:FirstImageNameHere.png|Image caption here
 File:SecondImageNameHere.png|Image caption here
 File:ThirdImageNameHere.png|Image caption here
</gallery>

Required information

Two sections should be included when uploading images: "Sumamry" and "Licensing".

== Summary ==
== Licensing ==

"Summary" is a text explaining what is depicted in image itself, using detailed illustrative terms to give a descriptive or narrative idea of what is portrayed.

"Licensing" is initially a drop-down menu on the upload page.

Templates for adding a rationale for use of the image can be found in Non-free file copyright templates and examples of how to use them can be found in Use rationale examples.

The == Summary == section should always, at minimum, containing the following:

• Description: The subject of the image. This should explain what the picture is of (ideally linking the article(s) it would be used on), and other identifying information that is not covered by the bullets below. (This is different from the image's caption or alt-text, and might be more descriptive than these.)
• Creator: The original creator (e.g., author or artist's name) of the image (especially if different from the copyright holder).
• Date (year) the image was created; if available, a full date is better than simply the year.

For example, a picture of a person taken at a public event will often identify that event and the date of the event.

An image of a character might say,

"A holy symbol of Muamman Duathal—an upright wood-hafted mace in front of a single brown leather boot trimmed with fur. Art by Corey Macourek (2002)."

The == Licensing== section should always, at minimum, containing the following:

• An image copyright tag, noting the license used to include the image on the wiki.
• Rationale for use is required, if using a non-free image A separate non-free rationale is required for each use of the image on the Great Library of Greyhawk wiki. Details of what is required for the non-free rationale is described in more depth in Non-free use rationale templates.
• Origin (source): The copyright holder of the image or URL of the web page the image came from
  • For an image from the internet the URL of an HTML page containing the image is preferable to the URL for just the image itself.
  • For an image from a book this is ideally the page number and full bibliographic information (author, title, ISBN number, page number(s), date of copyright, publisher information, etc.).
  • For a self-created image, state "Own work" (in addition to an appropriate copyright tag, such as {{self}}.
• Permission: Who, or what law or policy, gives permission to post the image on GreyhawkOnline with the selected image copyright tag (such as {{CC-BY-NC-SA 4.0}} (Creative Commons), {{PD}}) (Public Domain), or {{Non-free FairUse}} ).
• Other versions of this file on GreyhawkOnline—e.g. cropped or uncro

Format

Generally:

• Photos and scanned images should be in JPG format, though a PNG may be useful as well for simple subjects (where PNG would result in a smaller file without degrading quality).

You should not contribute images consisting solely of formatted or unformatted text, tables, or mathematical formulas. In most cases these can instead be typed directly into an article in wiki markup (possibly using MediaWiki's special syntax for tables. This will make the information easier to edit, as well as make it accessible to users of screen readers and text-based browsers.

In general, if you have a good image that is in the wrong format, convert it to the correct format before uploading. However, if you find a map, flag, etc. in JPEG format, only convert it to PNG if this reduces the file size. For further advice on converting JPEG to PNG.

Try to avoid editing JPEGs too frequently—each edit creates more loss of quality. If you can find an original of a photograph in 16-bit or 24-bit PNG, edit that, and save as JPEG before you upload. A limited variety of edits (crops, rotation, flips) can be performed losslessly; try to do this where possible.

Avoid images that mix photographic and icon content.

Though CSS makes it easy to use a PNG overlay on top of a JPEG image, the Mediawiki software does not allow such a technique. Thus, both parts must be in the same file, and either the quality of one part will suffer, or the file size will be unnecessarily large.

SVG support is implemented as of September 2005. The SVG is not directly given to the browser; instead, the SVG file is dynamically rendered as a PNG at a given size, and that PNG is given to the browser.

Uploaded image size

Generally, no image to be placed in an infobox should be above 350px in width nor more than 150 dpi. 250px width is preferred for most images. If the original image was smaller than that, it can be used at 250px, as long as it is without losing quality, or becoming blurry or unviewable. This is to protect the value of the original image and follow established Fair Use doctrines.

The servers automatically handle the scaling of images (whatever their original size) to the sizes called for in particular articles, so it is neither necessary nor desirable to upload separate reduced-size or reduced-quality "thumbnail" versions, although compressing PNGs before uploading may be useful.

Cropping

Within reason, crop an image to remove irrelevant areas. Images should only contain a depiction of the subject discussed in an article.

Animated images

Inline animations should be used sparingly; a static image with a link to the animation is preferred unless the animation has a very small file size. Animated images are incompatible with print copies of the information and text-based browsers.

Image titles and file names

Image titles should be written in "camel case" without spaces. E.g.—"NewFileName.png". If a particular subject is illustrated in multiple editions, a two-digit numeral should be added to identify the image, or an underscore (_) should be used to add a disambiguator to it, while keeping them organized together. E.g.— Kyuss_SpawnofKyuss01.jpg, Kyuss_SpawnofKyuss02.jpg, and Kyuss_SpawnofKyuss03.jpg.

It may be useful to add a two-digit numeral to a file title to distinguish multiple images of a creature by using the number of the edition of D&D it was used in. In the previous example, these would be for images of the Spawn of Kyuss in first, second, and third editions.

You may use the same name in the case of a different image that replaces the old one, and also if you make an improved version of the same image – perhaps a scanned image that you scanned again with a better quality scanner, or you used a better way of reducing the original in scale – then upload it with the same title as the old one. This allows people to easily compare the two images, and avoids the need to delete images or change articles. However, this is not possible if the format is changed, since then at least the extension part of the name has to be changed.pped, retouched or unretouched.

This page uses Creative Commons Licensed content from Wikipedia (view authors).