User:AndyZ/peerreviewer/guide

• Please expand the lead to conform with guidelines at Wikipedia:Lead. The article should have an appropriate number of paragraphs as is shown on WP:LEAD, and should adequately summarize the article.^[?]

This message appears if:

• there is one paragraph
• there are only two paragraphs and the article is > 30,000 characters (30kb)

• The lead of this article may be too long, or may contain too many paragraphs. Please follow guidelines at WP:LEAD; be aware that the lead should adequately summarize the article.

This message appears if:

• there are more than 4 paragraphs
• there are 4 paragraphs and the article is < 30,000 characters (30kb)
• there are 3 paragraphs and the article is < 15,000 characters (15kb)

{{infobox person |
name = whoever

instead of

{{infobox person
| name = whoever

extra paragraphs may be counted.

• The lead is for summarizing the rest of the article, and should not introduce new topics not discussed in the rest of the article, as per WP:LEAD. Please ensure that the lead adequately summarizes the article.^[1]

• There may be an applicable infobox for this article. For example, see Template:Infobox Biography, Template:Infobox School, or Template:Infobox City.^[2]

Infoboxes are in no way mandatory or required.

Also, the infobox list searched for by the script is very limited. It searches for keywords like "infobox", "taxobox", "geobox", and a few others. As a result, many more specific infoboxes are often missed. When I finally look thru WP:IB, this may be resolved.

• Per Wikipedia:Context and Wikipedia:Manual of Style (dates), months and days of the week generally should not be linked. Years, decades, and centuries can be linked if they provide context for the article.

• Per Wikipedia:Context and Wikipedia:Build the web, years with full dates should be linked; for example, link January 15, 2006.^[3]

• As per Wikipedia:Manual of Style (dates), dates shouldn't use ^th; for example, instead of using January 30^th was a great day, use January 30 was a great day.

• Per WP:MOS, avoid using words/phrases that indicate time periods relative to the current day. ^[4]

mostime_PR = true;

• Per Wikipedia:Manual of Style (numbers), there should be a non-breaking space -   between a number and the unit of measurement. For example, instead of 18mm, use 18 mm, which when you are editing the page, should look like: 18&nbsp;mm.^[5]

To resolve this problem:

1. User:Bobblewik has a script which fixes this: add {{js|User:Bobblewik/monobook.js/units nbsp.js}} to your monobook.js.
2. This script is transcluded within the PR script. After opening up the suggestions, click on the "Autoformat article per MoS" button. Be sure to carefully examine the difference!

• Per Wikipedia:Manual of Style (numbers), please spell out source units of measurements in text; for example, "the Moon is 380,000 kilometres (240,000 mi) from Earth.^[6]

• Per Wikipedia:Manual of Style (numbers), when doing conversions, please use standard abbreviations: for example, miles -> mi, kilometers squared -> km², and pounds -> lb.

• Per Wikipedia:Manual of Style (headings), headings generally do not start with the word "The". For example, ==The Biography== would be changed to ==Biography==.

Apparently, there is an error with this message in Firefox.

• Per Wikipedia:Manual of Style (headings), headings generally should not repeat the title of the article. For example, if the article was Ferdinand Magellan, instead of using the heading ==Magellan's journey==, use ==Journey==.

• As per Wikipedia:Manual of Style (headings), please do not link words in headings.

• Per WP:MOS, the first letters of words in heading should not be capitalized unless: 1) it is a proper noun or 2) it is the first word of the heading.(needs updating)

• Please reorder/rename the last few sections to follow guidelines at Wikipedia:Guide to layout.

• See also
• [Foot]Notes
• References
• Further reading
• External links

References can also go before Notes.

• Consider removing links that add little to the article or that have been repeated in close proximity to other links to the same article, as per Wikipedia:Manual of Style (links) and WP:CONTEXT.

Making too many links (especially those that don't provide additional context) distracts a reader and looks poor stylistically, especially for people who have the underlined links option turned on.

Instead, only link terms that provide valuable context. Don't link to low value links (like in the example sentence above); also, there is no need to link to certain links repeatedly in a single line or paragraph (or even section!), as these repeated links can be bothering (haven't you noticed that I linked to WP:LINK with 11 links?). Read more about links at WP:LINK.

• Consider adding more links to the article; per Wikipedia:Manual of Style (links) and Wikipedia:Build the web, create links to relevant articles.

• As done in WP:FOOTNOTE, footnotes usually are located right after a punctuation mark (as recommended by the CMS, but not mandatory), such that there is no space inbetween. For example, the sun is larger than the moon [2]. is usually written as the sun is larger than the moon.[2]

Good style:

• The Sun is larger than the moon.¹

Bad styles:

• The Sun is larger than the moon. ¹
• The Sun is larger than the moon ¹.
• The Sun is larger¹ than the moon.

This method is endorsed by the Chicago Manual of Style.

To fix this quickly, User:Gimmetrow has a replacement script that automatically places the citations in the correct place. The PR script transcludes this script (the autoformat button after you open up the suggestions).

• Please alphabetize the interlanguage links.^[7]

• Please avoid including instruction manuals, tutorials, etc. or other 'how-to's per WP:NOT.

• The article will need references. See WP:CITE and WP:V for more information.

• This article needs footnotes, preferably in the cite.php format recommended by WP:WIAFA. Simply, enclose inline citations, with WP:CITE or WP:CITE/ES information, with <ref>THE FOOTNOTE</ref>. At the bottom of the article, in a section named “References” or “Footnotes”, add <div class="references-small"><references/></div>.^[8]

For those who are unacquainted with the cite.php system, here's a quick description:

• There are two components to the cite.php system.
  • The actual <ref>FOOTNOTE CONTENTS</ref> tags go into the middle of the article. These tags include the information that should appear in the footnote. Thus, if you footnote is using {{Cite web}} (which is recommended for web references), do: According to [[John Doe]], this is true.<ref>{{cite web | author=Doe, John | title=My Favorite Things Part II | publisher=Open Publishing | date=[[2005-04-30]] | work=Encyclopedia of Things | url=http://www.example.com/ | accessdate=2005-07-06 }}</ref>
    • To re-use a footnote multiple times, use the name attribute of the ref tag (the first tag instead would be <ref name=THENAME>). Thus, According to [[John Doe]], this is true.<ref name=doe>{{cite web | author=Doe, John | title=My Favorite Things Part II | publisher=Open Publishing | date=[[2005-04-30]] | work=Encyclopedia of Things | url=http://www.example.com/ | accessdate=2005-07-06 }}</ref> He also states that it is important to do this. <ref name=doe>See above</ref>
  • In a "[foot]Notes" and/or "References" section, add <div class="references-small"><references /></div>. Without it, none of your footnotes show up!

• This article has no images. Please see if there are any free use images that fall under the Wikipedia:Image use policy and fit under one of the Wikipedia:Image copyright tags that can be uploaded. To upload images on Wikipedia, go to Special:Upload; to upload non-fair use images on the Wikimedia Commons, go to commons:special:upload.^[9]

• See if possible if there is a free use image that can go on the top right corner of this article.^[10]

• Images need proper image copyright tags and source information. Several images are missing proper tags.

To save time and disable the usage of ajax, add a line in your monobook.js or other js file saying: noXHR_PR = true;. To specifically disable this image checking but to still allow ajax, add a line stating imgCheck_PR = false;.

If it were operating normally, there still would be several bugs:

• Images on the Wikimedia Commons are not checked. Most images on the Commons are empty when you try to edit them, and the javascript will conveniently ignore these. However, some have categories/other small information, which will cause the javascript to believe that the image is not on the Commons. (User:Zocky's Picture Popups script can get around this problem, I will see if I can fix this on the PR script)

• Images with fair use tags need fair use rationales - please see WP:FUC. Several images are missing fair use rationales.

To save time and disable the usage of ajax, add a line in your monobook.js or other js file saying: noXHR_PR = true;. To specifically disable this image checking but to still allow ajax, add a line stating imgCheck_PR = false;.

A fair use rationale may be written without the keywords noted above; such a rationale will be missed.

• Per Wikipedia:What is a featured article?, Images should have concise captions.^[11]

• The image may be in an infobox, where using captions is not recommended. Js tries to ignore such, but there is no guarantee.
• Flags don't need captions, but will trigger it.
• The image syntax is written in a different manner; for example, [[Image:Smiley.jpg|This is a smiley face|right|120px]] instead of [[Image:Smiley.jpg|right|120px|This is a smiley face]] will trigger it.
• Piped wikilinks to center, none, left, right, and a number followed by 'px' will set this off (eg, the [[center of balance|center]]).

• Avoid including galleries in articles, as per Wikipedia:Galleries. Common solutions to this problem include moving the gallery to a separate page.

There are a couple of solutions to this problem.

1. Move all of the images to the Wikimedia Commons, and then link to the category that all of the songs are in. Note that the Commons does not allow fair use images no matter what the case; anyways, including fair use images in a gallery is completely unjustifiable and infringes image copyrights.
2. Move the gallery to a subpage. If the article was, for example, Birds, a gallery could be placed at Gallery of birds.
3. Keep the number of images in the gallery to a minimum; remove and/or delete (contact an adminstrator) fair use images (especially if they are high quality) if there are free use images and images of low quality/relevance, and then move images from the gallery into more relevant spots in the article.

• Per WP:WIAFA, this article's table of contents (ToC) may be too long- consider shrinking it down by merging short sections or using a proper system of daughter pages as per Wikipedia:Summary style.^[12]

In general, try to avoid using only one subheading underneath a higher level heading. Instead of using a full new section to split up the external links, bibliography, references, etc, it may be wise to use boldface (using '''bold text''' or ;bold line):

Web resources

• ...

Books

Autobiographies

• ...

• This article is a bit too short, and therefore may not be as comprehensive as WP:WIAFA critera 2(b) is looking for. Please see if anything can be expanded upon.

• There are a few sections that are too short and that should be either expanded or merged.

• This article may need to undergo summary style, where a series of appropriate subpages are used. For example, if the article is United States, than an appropriate subpage would be History of the United States, such that a summary of the subpage exists on the mother article, while the subpage goes into more detail.

• Readability. A reader is more likely to want to read through a concise but detailed article than a verbose, winding, huge article.
• Technical issues. An editor will probably not scan the entire article to see if text he/she is adding is duplicated or misplaced. Similarily, a missing piece of important information might be forgotten if an editor sees that the article is that long already. It also makes it difficult for copyeditors and fact-checkers to make it through the article.

To avoid such, use subpages: For example, instead of fitting the entire history of the United States in United States#History, just discuss the major points of US history on the main article and spin the rest of the details to History of the United States. Even there, further subdivision may be needed (History of the United States (1776-1789)).

• Please ensure that the article has gone through a thorough copyediting so that it exemplifies some of Wikipedia's best work. See also User:Tony1/How to satisfy Criterion 1a.^[13]

• There are a few occurrences of weasel words in this article- please observe WP:AWT. Certain phrases should specify exactly who supports, considers, believes, etc., such a view. ^[14]

• This article may be a bit list-weighty; in other words, some of the lists should be converted to prose (paragraph form). ^[15]

• Generally, trivia sections are looked down upon; please either remove the trivia section or incorporate any important facts into the rest of the article.

• If this article is about a person, please add {{persondata}} along with the required parameters to the article - see Wikipedia:Persondata for more information.

persondata is only to be used on biography articles. It is to be used like this (for Ferdinand Magellan):

<!-- Metadata: see [[Wikipedia:Persondata]] -->
{{Persondata
|NAME=Magellan, Ferdinand
|ALTERNATIVE NAMES=Magalhães, Fernão de (Portuguese); Magallanes, Fernando de (Spanish)
|SHORT DESCRIPTION=Sea explorer
|DATE OF BIRTH=Spring [[1480]]
|PLACE OF BIRTH=[[Sabrosa]], [[Portugal]]
|DATE OF DEATH=[[April 27]], [[1521]]
|PLACE OF DEATH=[[Mactan Island]], [[Cebu]], [[Philippines]]
}}

If the subject in question has not died yet, of if the date/place of birth/death is unknown, or if there are no alternative names, just leave that part blank (|DATE OF BIRTH=, next line, continue).

By default, persondata cannot be viewed. If you wish to see it, add the line table.persondata {display:block;} (for IE) or .table.persondata {display:table;} (for all other browsers) to your monobook.css, or other relevant css page depending upon your skin.