User:Tommy-Macaroni/Objections

The following list contains numerous (but by no means all) common, nonspecific objections to nominated articles, be it a CAN, GAN, or FAN.

While I hope that with some refinement this list will become an official review board page, in the meantime, please feel free to use this page as a checklist for both writing articles and reviewing them. Bear in mind, however, that in lieu of other objections requiring more major work from the nominator, many of these smaller issues can be resolved by the reviewer as "sofixit" changes without the need for a formal objection.

Please note that while this'll probably make life easier by allowing the easy copy-pasting of objections, for the time being, the AC have agreed we don't want to see just numbers, eg "1.05," as objections.

Items to be added

1.01. Article is not detailed enough. Please look over current Featured and Good articles to see the level of detail expected.

1.02. Unreferenced section(s).

• The only part of an article that should not have a source is the introduction, image captions, and occasional sentences in the Behind the Scenes section referencing the article itself (eg "This article assumes the latter source to be correct"). All other sections must be sourced, including the body, the rest of Behind the Scenes, the infobox, and succession boxes.

1.03. Missing backup link(s).

1.04. Redlink(s) in the article need to be created. Please note that if the subject is missing a canon or Legends version of the page when one ought to be created, this counts as a redlink.

1.05. General underlinking.

1.06. Infobox/Intro exclusive information.

1.07. Intro needs to be expanded.

1.08. Article is over 165 words, not counting the "Behind the scenes" section, and so it needs to provide an intro and be sectioned.

1.09. {{Mediacat}} needs to be added.

1.10. Date refs normally require a separate ref note. Is the date's current source sufficient?

1.11. A timeframe should be provided.

1.12. Can more images or quotes be added?

1.13. Subsectioning of large section(s) required.

1.14. {{Otheruses}} or {{Youmay}} needs to be implemented.

1.15. Ensure all abridged and unabridged audiobook adaptations of novels are investigated and added to the Appearances section as necessary. Websites like https://talkingbooks.osl.state.or.us/ can be used to see if novels have audiobook adaptations

Items to be removed

2.01. Duplicate link(s).

• Duplicate links can be highlighted by going to Preferences; Gadgets; "Highlight duplicate links in articles." Duplicate links will then be highlighted in red if you activate the tool from the bottom menu.

2.02. Redirect(s).

• Redirects can be highlighted by going to Preferences; Gadgets; "Highlight all redirects orange."

2.03. Article contains consecutive duplicate references.

2.04. Trimming needed. Ideally, the subject should be mentioned at least once per paragraph. More than two consecutive sentences without mentioning the subject usually constitutes excessive context.

2.05. Articles should not link to disambiguation pages in their body.

2.06. Articles should not use "unidentified" in either their body or their infobox.

2.07. Article contains biased phrasing which needs to be removed.

Items to be modified

3.01. Images are of poor quality. This may require reuploads with Blu-Ray film or TV screenshots, digital comic captures, etc.

• Please note that if an image is from a less accessible source (eg a comic only released in Germany), lower quality can be permitted.

3.02. Audio files are poorly cropped.

3.03. Image(s) colliding with section headers/quotes.

3.04. Article needs to be correctly titled, in accordance with the Naming policy. This means specific parentheses where applicable, articles should not have "/Canon" in their title, and precedence for a title should be granted to a canon subject.

3.05. Incorrect image caption punctuation. Captions that are full sentences get a period, whereas incomplete sentences do not. An example: "The Dauntless captured a CR90 corvette." / "The Dauntless captures a CR90 corvette." / "The Dauntless capturing a CR90 corvette" The latter does not receive a period as it is not a full sentence. You could not imagine reading that sentence in a novel. The first two could be written in a novel though.

3.06. Refer to the Layout Guide for the correct section headers.

3.07. Quotes and their respective audio files need to be consistent. This means the audio file needs to vocalize the quote word for word. In order to achieve this, an audio file needs to be edited to remove narrative elements (eg "she said"), speech not in the quote (eg speech from another character not in the quote), and extraneous background noises when characters are not speaking (eg four seconds of bumps after the dialogue in the quote is over).

3.08. Numbers over ninety nine should be written out (eg "127," not "one hundred and twenty-seven").

3.09. Templates at the top of an article need to be correctly ordered as mandated by the Layout Guide. Disambiguation/redirect templates (eg {{Otheruses}}) should be placed first, then any spoiler tags (eg {{Spoiler}}), then other header templates such as {{Conjecture}} and {{Noncanon}}.

3.10. Generally, one-sentence paragraphs are discouraged, especially in the introduction. However, one-sentence paragraphs may be unavoidable in sections with limited information (eg a Skills and abilities section is allowed to comprise of just "____ was a skilled thief." if that is all relevant information). Additionally, one-sentence paragraphs are perfectly permissible in the Behind the scenes section to separate information.

Technical

4.01. When pipelinking, the linked page is always capitalised (eg [[Starship|vessel]], not [[starship|vessel]]).

4.02. When pipelinking, always place all characters inside the link brackets (eg. [[Electrum (Venator-class)|''Electrum'']], not ''[[Electrum (Venator-class)|Electrum]]''; [[TIE/ln space superiority starfighter|TIE fighters]], not [[TIE/ln space superiority starfighter|TIE fighter]]s).

4.03. Files and templates need to use underscores in place of spaces (eg [[File:Luke_Skywalker.jpg]], not [[File:Luke Skywalker.jpg]]).

4.04. HTML should be used instead of select punctuation (eg "—" instead of "—," "–" instead of "–," "…" instead of "...").

4.05. Microsoft punctuation should never be used (eg " instead of “, ' instead of ’).

4.06. The correct order for file links goes as follows: [[File_name|thumb|location|size|caption]].

4.07. Parameters in {{Top}} need to be in the correct order.

4.08. {{Interlang}} needs to be in alphabetical order.

4.09. Do not "split" links. This entails splitting up a link to an article to fit in more links (eg [[Kuat Drive Yards]], not [[Kuat]] [[Kuat Drive Yards|Drive Yards]]; [[Anakin Skywalker|Darth Vader]], not [[Darth]] [[Anakin Skywalker|Vader]]). However, you may link at a later point subjects that have yet to be linked: YT-1300 [[light freighter]].

4.10. If a subject only appears in one source in one continuity (or one source as well as its audiobook), it is unnecessary to say it first appeared, was first mentioned, or was first pictured in that source. Instead, it should simply be phrased as "[subject] appeared/was mentioned/was pictured in [source]." The use of "first" is only necessary when the subject has multiple sources (including one source in canon and one source in Legends).

Grammatical

5.01. An oxford comma needs to be implemented (eg "The ships Brentaal, Liberator, and Malevolence"; not "The ships Brentaal, Liberator and Malevolence").

5.02. American English is used over British English (eg "color," not "colour"; "analyze," not "analyse"; "defense," not "defence").

5.03. The use of "this" (and "their" when referring to individuals who do not specifically use that pronoun) is discouraged in formal writing (eg "the scout trooper," not "this scout trooper").

5.04. Contractions (eg "it's," "wouldn't") should never be used in formal writing.

5.05. Quotation marks should surround all punctuation except for the semi-colon (eg "The director has stated Snoke 'had it coming.'"; "Lucas has said the issue was 'controversial'; however, he later[…]").

5.06. Use of "however" in the middle of a sentence is incorrect. Correct: "[…]; however, [full sentence]." Correct: "[…], however, [incomplete sentence]."

5.07. Incorrect use of hyphens. See here for more information.

• Hyphenate compound adjectives; two or more words that modify a noun ("the 1,600-meter-long [noun]").
• Hyphenation is not necessary when the compound adjective follows the noun ("[noun] measured 1,600 meters long").
• Adverbs are not hyphenated in this way ("heavily armed warship").
• Hyphenate numbers from twenty-one through ninety-nine.
• If the compound adjective contains a well known phrase, do not hyphenate that phrase, but instead use an en dash to connect it to the rest of the compound adjective ("kyber crystal–powered weapon").

5.08. "By [year]" is preferable to "in or before [year]."

5.09. Incorrect use of "who"/"whom." See here for more information.

• If you can replace the word the who(m) is describing with he, she, or another subject pronoun, use who. If you can replace it with him, her, or another object pronoun, use whom.
• Find all subjects in the sentence, and correlate them to all the verbs. If the word the who(m) is describing is a subject (the one doing the action), use who. If it is an object (the one receiving the action), use whom.

5.10. "Toward," "forward," "backward," etc. is preferred to the versions ending in "s" ("towards," "forwards," "backwards").

Further advice

Beyond these points, it is further advised that when nominating and reviewing, multiple read-throughs of an article should be occurring to check for clarity and consistency. Additionally, it may be beneficial to wait a day after finishing writing an article before formally nominating it, to allow for a last read of it with fresh eyes. Also, try not to be disheartened when errors inevitably have to be fixed in copy-edits. This article interestingly explains why it is more difficult to spot errors in our own work.

While online writing services such as Grammarly are by no means extensive or even always correct, beginners may find it useful to put their article through these sites to have a pre-review check of grammar correctness, clarity, and variety of vocabulary. However, these services should be used with caution, as they can sometimes be incorrect and thus detrimental to the article. More experienced writers and reviewers will likely grow beyond having a use for such sites.

Lastly, some writing information has been provided by article review bodies. See Wookieepedia:Status article tutorials and Category:Wookieepedia status article tutorials for more information.