Jump to content

User:AndyZ/peerreviewer/guide

From Wikipedia, the free encyclopedia
< User:AndyZ | peerreviewer
(Redirected from User:AndyZ/G)
Shortcut

Introduction

[edit]

Despite its name, reviews created by this script aren't by peers, but by a JavaScript (written by peers, though). "Peer" is in there to clarify its purpose.

The suggestions generated by the script focus largely on style issues, e.g. those that can be found on WP:MOS. Other topics covered by the script include: WP:CONTEXT, WP:GTL, WP:LEAD, WP:LINK, WP:SS, WP:FOOTNOTE, WP:PDATA, WP:AWT, and several subpages of WP:MOS including WP:MOSDATE. These tips tend to appear (based on my experiences) on WP:PR, WP:FAC, and WP:FARC (most of these tips are covered by my suggestions page). Though most of the tips are generally accurate, some will not be accurate/applicable for the article in question.

Fixing the generated issues is not mandatory (for WP:FAC or WP:GAC), nor will completing them guarantee that the article will pass both. The goal of the script is to supplement the advice of manual reviews by looking for common issues often overlooked by editors, as well as setting up a starting point for problems to work on while editors review articles with more comprehensiveness. Comments/questions about the suggestions can be placed directly on the PR/A page (I'll try to address all questions placed there) or at other locations, like the actual peer review for other editors to elaborate upon or my talk page.

Note: AZPR is not a BOT – it can be considered a semi-bot. The current automated peer review listings can be found at Wikipedia:Peer review/Automated/November 2024.

Some FAQs:

Specific to this page:

Suggestions specifics

[edit]

lead

[edit]
Content User:AndyZ/PR/lead
  • 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.[?]
Description The lead should conform to guidelines at WP:LEAD; it should have enough content to adequately summarize the article.
This appears because JavaScript looks for the number of new lines starting with actual letters (other characters, like {|<'[ will be ignored).

This message appears if:

  • there is one paragraph
  • there are only two paragraphs and the article is > 30,000 characters (30kb)
Known errors If a paragraph in the lead starts with some sort of wiki-syntax (a template, bold, a comment, etc.), it might not be counted as a paragraph. It also only looks at uppercase letters; for certain articles (like iPod), this could be a problem.

leadlong

[edit]
Content User:AndyZ/PR/leadlong
  • 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.
Description The lead should conform to guidelines at WP:LEAD; the lead should be a concise but compelling summary of the article.
This appears because JavaScript looks for the number of new lines starting with actual letters (other characters, like {|<'[ will be ignored).

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)
Known errors Since this is automated, not manual, it cannot tell the different between a newline in a table/comment and an actual paragraph; if the table/comment/other syntax is written in an unique fashion, like 
{{infobox person |
name = whoever

instead of 

{{infobox person
| name = whoever

extra paragraphs may be counted.

leaddetail

[edit]
Content User:AndyZ/PR/leaddetail
  • 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]
Description
This appears because In the script, JavaScript searches for the number of paragraphs in the lead (using the method noted above). It does not actually check the content of the lead; this message only appears if the number of paragraphs in the lead exceeds 5.
Known errors See the errors listed at #leadlong.

infobox

[edit]
Content User:AndyZ/PR/infobox
Description Articles often benefit from infoboxes, which can provide quick and easy-to-see information or link to related topics.

Infoboxes are in no way mandatory or required.

This appears because In the script, JavaScript searches for an infobox (or taxobox). If it doesn't find one, it displays the note.
Known errors Many articles will not have applicable infoboxes. If so, don't waste your time searching for one. Generally, articles that parallel other articles will have infoboxes (cities, mammals, military people, etc).

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.

contxt

[edit]
Content User:AndyZ/PR/contxt
Description Articles should follow MOS:DATE and WP:CONTEXT.
This appears because In the script, JavaScript searches for stand-alone linked years (like 2024), linked days of the week (Monday), and stand-alone linked month (March).
Known errors There is considerable debate surrounding if years should be linked or not at MOS:DATE. In general, the consensus is to not link dates unless they provide context for the article.

linkdate

[edit]
Content User:AndyZ/PR/linkdate
  • Years (2008) or months (January) by themselves are typically not linked. Per Wikipedia:Context, dates should not be linked purely for autoformatting purposes. In general, dates should not be linked unless there is a reason to do so.
Description Date linking allows the users to view them different depending upon their date preferences. However, linking dates purely for the purpose of autoformatting has been deprecated. Read more at MOS:DATE.
This appears because In the script, JavaScript searches for dates with years that have not been linked (like November 17, 2024 instead of November 17, 2024).
Known errors This may occur if retrieval dates in <ref> tags or other inline citations are not linked.

dateth

[edit]
Content User:AndyZ/PR/dateth
Description Dates should not use ordinal suffices, namely [1]'st', [2]'nd', [3]'rd', [4-9]'th'.
This appears because In the script, JavaScript searches for dates in the format of: MONTH 1-2 digit NUMBER th and other layouts.
Known errors No known errors.

time

[edit]
Content User:AndyZ/PR/time
  • Per WP:MOS, avoid using words/phrases that indicate time periods relative to the current day. [3]
Description Since we wish Wikipedia to continue on until the future, don't use times that are relative to today/now.
This appears because In the script, JavaScript searches for terms like 'soon' and 'recently'. Other terms like 'last day/month/year' are no longer searched for due to heavy inaccuracy.
Known errors This is no longer used (by default) in the script. If you wish to search for this and have installed the PR script, add a new line saying

mostime_PR = true;

nbsp

[edit]
Content User:AndyZ/PR/nbsp
  • Per Wikipedia:Manual of Style (numbers), there should be a non-breaking space - &nbsp; 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.[4]
Description To prevent units of measurements from falling off onto the next line, we use a non-breaking space. This is similar to a regular space, except it prevents the next word from falling off onto the next line when viewed on the webpage. If you had a measurement of, for example, 100 centimeters (250in), write instead 100&nbsp;centimeters (250&nbsp;in).

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!
This appears because In the script, JavaScript searches for: # UNITOFMEASUREMENT\W (\W stands for any non-letter character, like a parenthesis or comma).
Known errors Before, 'in' was often interpreted as inch incorrectly. As a result, it is no longer searched for. The most common error for such would be in a link to another article (article titles don't include &nbsp;) or in an external link.

spellnum

[edit]
Content User:AndyZ/PR/spellnum
Description Spell out units in text (but not conversions). Thus, 100 centimeters (250 in), not 100 cm (250 inches).
This appears because In the script, JavaScript searches standard abbreviations following numbers that are not trailed by a closing parenthesis.
Known errors In infoboxes, tables, and other templates, space is of concern, so it is proper to use abbreviations there.

abbrev

[edit]
Content User:AndyZ/PR/abbrev
Description Use standard abbreviations for units of measurements in conversions (see example above).
This appears because In the script, JavaScript searches for measurements written out completely followed by a closing parenthesis.
Known errors No known errors.

headingthe

[edit]
Content User:AndyZ/PR/headingthe
Description To avoid redundancy, do not start headings with articles ('a', 'an', 'the') unless necessary.
This appears because In the script, JavaScript searches for headings that start with the aforementioned articles.
Known errors Sometimes, the articles are necessary; in the majority of the cases they are not.

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

headingre

[edit]
Content User:AndyZ/PR/headingre
Description Don't repeat the title of the article in headings, as the title is implied as the subject for the section. Otherwise, it would be redundant.
This appears because In the script, JavaScript searches for the title (without disambiguation parentheses information) in all lines that are headings (start with ==).
Known errors The title should be repeated for the names of proper nouns. (A fictitious example: if Washington had a heading for the capitol of the United States, it would be ==Washington D.C.==, not ==D.C.==).
[edit]
Content User:AndyZ/PR/headinglink
Description Avoid linking words in headings. This is for style and readability. Instead, use the link in the first sentence after the heading.
This appears because In the script, JavaScript searches for a [[ blah ]] in headings (lines that start with ==).
Known errors No known errors.

headingcap

[edit]
Content User:AndyZ/PR/headingcap
  • 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)
Description Only capitalize a word in a heading if it is a proper noun or if it is the first word of the heading (and of course, if the capitalization complies with standard English capitalization usage). It is not to be capitalized as is done in book titles.
This appears because In the script, JavaScript searches for a few commonly used headings, like ==External Links==, ==See Also==, and others, but seeing if the capitalization is [in]correct.
Known errors No known errors.

gtl

[edit]
Content User:AndyZ/PR/gtl
Description The order of the final few sections is:
  • See also
  • [Foot]Notes
  • References
  • Further reading
  • External links

References can also go before Notes.

This appears because In the script, JavaScript searches for the sections see also, references/footnotes, and external links, and compares their relative positions.
Known errors No known errors.
[edit]
Content User:AndyZ/PR/overlink
Description If an article was completely blue, you would not want to read it, would you?

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.

This appears because WP:MOS-L gives the suggestion that at most 10% of the words in an article should be linked. JavaScript counts the number of [[ against the number of spaces.
Known errors There will probably be minor discrepancies caused by image syntax, and there will likely be many spaces not part of the prose that are counted.
[edit]
Content User:AndyZ/PR/underlink
Description While an article shouldn't have too many links, having too little links makes the article look too plain and dull, while also making it difficult for a reader to establish context for the article and read further into the subject about topics that he/she doesn't know about. WP:BTW also notes that linking allows the encyclopedia to link relevant articles together.
This appears because WP:MOS-L gives the suggestion that at least 3% of the words in an article should be linked. JavaScript counts the number of [[ against the number of spaces.
Known errors There will probably be minor discrepancies caused by image syntax, and there will likely be many spaces not part of the prose that are counted. Also, the guidelines consider the number of words in the links, not the number of links that the script searches for; this could throw the script off considerably.

footspace

[edit]
Content User:AndyZ/PR/footspace
  • 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]
Description To keep consistent on Wikipedia, keep inline citation tags right after the punctuation mark, without a space.

Good style:

  • The Sun is larger than the moon.1

Bad styles:

  • The Sun is larger than the moon. 1
  • The Sun is larger than the moon 1.
  • The Sun is larger1 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).

This appears because In the script, JavaScript searches for ref tags that are placed such that there is a space b/w the ref tag and the punctuation mark, or ref tags that are placed right before the punctuation mark.
Known errors No known errors.

alpha

[edit]
Content User:AndyZ/PR/alpha
Description This is somewhat controversial, but occasionally it is a good idea to categorize the categories and interlanguage links. However, there are cases when prominent categories should be placed first. Wikipedia:Language order poll is oriented towards either alphabetization by the name of the language in that language or by the 2-letter language code.
This appears because The script looks at all of the categories/interlanguage links and then compares them to see if they go in alphabetical order.
Known errors This no longer appears by default. If you want your own personal reminder for this, add: cat_PR = true; for category alphabetization, and alpha_PR for interlanguage links alphabetization.

how

[edit]
Content User:AndyZ/PR/how
  • Please avoid including instruction manuals, tutorials, etc. or other 'how-to's per WP:NOT.
Description Wikipedia is WP:NOT a discriminate collection of information: more relevantly, it is not a how-to (there is a wikiHow for that though).
This appears because In the script, JavaScript searches for a section heading that starts with "How to ..."
Known errors No known errors.

ref

[edit]
Content User:AndyZ/PR/ref
  • The article will need references. See WP:CITE and WP:V for more information.
Description References are required to make sure that an article is fully verified. See more information at WP:CITE.
This appears because In the script, JavaScript searches for a heading titled with "References", "[Foot]notes", "Works cited", etc.
Known errors No known errors.
[edit]
Content User:AndyZ/PR/foot
  • 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>.[7]
Description In order for a reader to know that an article is verifiable, inline citations (WP:FOOTNOTEs) should be located throughout the article by which readers can check information with external sources. The current recommended system is the cite.php <ref> system.

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 appears because In the script, JavaScript searches for <ref tags, as well as {{ref, {{harv, and {{fn. If the system used is not the cite.php system, it posts a note suggesting it. If it can't find any of them, it suggests the addition of footnotes in general.
Known errors The article may use Harvard references without templates, which is an acceptable citation style.

fact

[edit]
Content User:AndyZ/PR/fact
User:AndyZ/PR/fact
Description In order for a reader to know that an article is verifiable, inline citations (WP:FOOTNOTEs) should be located throughout the article by which readers can check information with external sources. There should never be original research or false/unverifiable in the article. Wikipedia:Biographies of living persons states that any unverifiable information in biography articles should be removed immediately.
This appears because In the script, JavaScript searches for {{fact}} tags, as well as redirects to that template/similar templates (such as: {{citation needed}}, {{cn}}).
Known errors No known errors.

noimg

[edit]
Content User:AndyZ/PR/noimg
Description Images, though not a prerequisite for featured article status, are useful for readers to visualize information. Good graphics (of course, that don't violate WP:FUC and/or infringe image copyright rules) can help a reader to understand more about the topic.
This appears because The script searches for image: (capitalization is ignored).
Known errors Images in infoboxes and other templates may be missed if it is not necessary to type out image:.

leadimg

[edit]
Content User:AndyZ/PR/leadimg
  • See if possible if there is a free use image that can go on the top right corner of this article.[9]
Description There should be an image to the right side of the lead (usually, it should be located in the first couple of lines or in an infobox/other template). This creates a nice draw-in to the article and gives the reader a starting impression and perhaps even a summary about the subject. This image will likely be featured on the Main page if the article reaches featured article status. Note that this is from no specific guideline, but solely for style.
This appears because In the script, JavaScript searches for a image: in the first 500 characters.
Known errors Images in infoboxes and other templates may be missed if it is not necessary to type out image:. Also, images are often placed at the bottom of the lead, which usually will not be located within the first 500 characters; a simple upwards shift would solve this.

imgtag

[edit]
Content User:AndyZ/PR/imgtag
  • Images need proper image copyright tags and source information. Several images are missing proper tags.
Description Images must have proper copyright tags. The list of copyright tags is at WP:IT. Otherwise, using such images is an infringement upon copyright laws. About fair use, see #imgfu.
This appears because In the script, JavaScript picks up the names of all of the images, and then uses ajax to check the contents of the respective image pages. There, it checks for an image copyright tag or for a defunct tag (like {{pd}}).

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;.

Known errors This is not currently in use due to an unresolved error.

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)

imgfu

[edit]
Content User:AndyZ/PR/imgfu
Description Images that are claimed underneath the fair use doctrine need to have fair use rationales that explain why the image in question falls underneath WP:FUC. Specifically, it should explain WP:FU#Law.
This appears because In the script, JavaScript picks up the names of all of the images, and then uses ajax to check the contents of the respective image pages. There, it checks for a fair use image copyright tag and then searches for a fair use rationale (looking for keywords like 'fair use', 'rationale', etc).

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;.

Known errors This is not currently in use due to an unresolved error.

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

caption

[edit]
Content User:AndyZ/PR/caption
Description Images should have captions so readers can identify the subject and focus of the image. These captions should not be too long (a good rule is less than 6 lines); see WP:CAPTION for more detailed image caption guidelines.
This appears because In the script, JavaScript searches for | .jpg/.png/.(etc)/left/right/center/none/##px ]]
Known errors There are several known bugs:
  • 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]]).

ig

[edit]
Content User:AndyZ/PR/ig
Description Galleries consisting of indiscriminate collections of images are discouraged. Wikipedia is NOT a repository of images. These images, clustered together, provide little help to the reader since they are not near the relevant piece of text, and also may overwhelm a reader.

There are a couple of solutions to this problem.

  1. Move all of the images to the Wikimedia Commons, and then link to the Commons category that all of the images are in using the {{Commonscat}} tag. 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. Improve the content of the gallery in accordance with the provisions of Wikipedia:Image use policy respecting galleries.
This appears because In the script, JavaScript searches for <gallery>.
Known errors No known errors.

toc

[edit]
Content User:AndyZ/PR/toc
  • 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.[11]
Description The table of contents should not be too large. This makes the formatting neater (then, we won't have this giant list that extends down for a page alone), and allows readers to skip directly to the section that is most relevant. It also is part of Wikipedia:Summary style.

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 appears because In the script, JavaScript searches for the number of headings in the article.
Known errors Depending upon the scope of the article, an article may require a larger table of contents. It will also skip over level 1 headings (=Heading=), which shouldn't be used in the article namespace anyway.

expand

[edit]
Content User:AndyZ/PR/expand
  • 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.
Description A featured article must be comprehensive and cover the entire subject of the article with detail (while following WP:SS).
This appears because The article either has less than 7500 total characters (including whitespace) or there are less than 5 sections. There are a few exceptions, depending upon the scope of the article (there are a couple of WP:FAs that have 5-6 sections, and yet are comprehensive).
Known errors Depending upon the scope of the article, having more than 5 sections may not be feasible (though for most articles, this is not the case). The only other possibility really is if the article was just vandalized and blanked. It will also skip over level 1 headings (=Heading=), which shouldn't be used in the article namespace anyway.

sectexpand

[edit]
Content User:AndyZ/PR/sectexpand
  • There are a few sections that are too short and that should be either expanded or merged.
Description Self-explanatory: an article should be fully comprehensive and not be missing any major facet of information. If a section is a stub (by definition, doesn't cover enough), the article can't be comprehensive.
This appears because In the script, JavaScript searches for {{Sectstub}} and other related templates.
Known errors No known errors.

SS

[edit]
Content User:AndyZ/PR/SS
  • 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.
Description Though it is important for articles to be detailed, it is equally important to ensure that the size of the article is not too large. There are several difficulties to overly long articles:
  • 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)).

This appears because If the length of the article is greater than 50,000 and the {{main}} template is not used, then this appears.
Known errors No known errors.

copyedit

[edit]
Content User:AndyZ/PR/copyedit
Description Make sure that the article meets the requirement that the prose is brilliant and compelling - WP:WIAFA #1.
This appears because This appears by default. It just acts as a reminder, and in no way implies that the article is of poor quality writing.
Known errors Always appears, no matter how many times you copyedit the article...

awt

[edit]
Content User:AndyZ/PR/awt
  • 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. [13]
Description Weasel terms that seem to support a statement without using actually using verifiable sources. General phrases like "People consider that..." or "Many scientists believe..." may make an opinion seem NPOV, but is not substantiated by actual sources. Either append a citation (if there isn't already one) or remove the weasel term. They also cause a number of other problems listed here (including both grammar and style, such as readability and passive voice).
This appears because In the script, JavaScript searches for a list of common weasel words.
Known errors Weasel words located in quotes should not be deleted, as well as in titles (for example, an external link or a ref tag).

list

[edit]
Content User:AndyZ/PR/list
  • This article may be a bit list-weighty; in other words, some of the lists should be converted to prose (paragraph form). [14]
Description Lists disrupt encyclopediac prose.
This appears because This is no longer searched for due to high inaccuracy. It used to search for sections beginning with "List of..."
Known errors This is no longer searched for.

trivia

[edit]
Content User:AndyZ/PR/trivia
  • Generally, trivia sections are looked down upon; please either remove the trivia section or incorporate any important facts into the rest of the article.
Description Per WP:TRIV and WP:NOT, trivia sections should not be included in encyclopedia articles. Important information in those sections should be moved into the article or into a "In popular culture" section.
This appears because In the script, JavaScript searches for a regular expression
Known errors Certain sections will be mis-interpreted as a trivia section. Examples include "Other factories" (it sees 'Other fact') and "Miscellaneous", used in discographies.

persondata

[edit]
Content User:AndyZ/PR/persondata
  • If this article is about a person, please add {{persondata}} along with the required parameters to the article - see Wikipedia:Persondata for more information.
Description {{persondata}} is a metadata template. It does not provide any immediate benefits for Wikipedia and its readers, but may be useful in the future as a way to organize Wikipedia biography articles. For more information about this template and its syntax, see Wikipedia:Persondata.

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.

This appears because In the script, JavaScript searches first for an indication that the article is a biography article (if it has the xxxx year birth/death category or includes an infobox about a person), and then sees if {{persondata is in the article.
Known errors No known errors.

References

[edit]
  1. ^ See footnote
  2. ^ See footnote
  3. ^ See footnote
  4. ^ See footnote
  5. ^ See footnote
  6. ^ See footnote
  7. ^ See footnote
  8. ^ See footnote
  9. ^ See footnote
  10. ^ See footnote
  11. ^ See footnote
  12. ^ See footnote
  13. ^ See footnote
  14. ^ See footnote
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:AndyZ/peerreviewer/guide&oldid=1010509511"