Pikipedia:Specific article guidelines: Difference between revisions
No edit summary |
m (Protected "Pikipedia:Specific article guidelines" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only administrators] (indefinite))) |
||
(3 intermediate revisions by one other user not shown) | |||
Line 2: | Line 2: | ||
==Disambiguation pages== | ==Disambiguation pages== | ||
Disambiguation page names should only contain the name of the ambiguous subject. Only append "(disambiguation)" to the title if a subject-only title would be better suited as a redirect to something else, or if the disambiguations pages also use something in parenthesis in their title. | {{shortcut|P:DISAMBIG}} | ||
Disambiguation page names should only contain the name of the ambiguous subject. Only append "(disambiguation)" to the title if a subject-only title is already a thing in the series, would be better suited as a redirect to something else, or if the disambiguations pages also use something in parenthesis in their title. You can create a disambiguation page for any subject, whether it has two disambiguation links or multiple, but make sure that it wouldn't be better to use a {{tem|redirects}}, {{tem|for}}, or something similar instead. | |||
Disambiguation pages for a subject that is purely a search title (like "green") should be avoided. In essence, a disambiguation page is helpful for when a reader searches for something they don't know the exact title of, and we know that there is a very high chance that they wanted this or that article. | Disambiguation pages for a subject that is purely a search title (like "green") should be avoided. In essence, a disambiguation page is helpful for when a reader searches for something they don't know the exact title of, and we know that there is a very high chance that they wanted this or that article. | ||
Line 8: | Line 9: | ||
These pages should start with one or two sentences describing why the subject is ambiguous and introducing a list of disambiguations. Examples: "The term example could refer to any of the following.", "In the ''Pikmin'' series, the following are examples:". The first mention of the subject on this opening paragraph should be bolded. | These pages should start with one or two sentences describing why the subject is ambiguous and introducing a list of disambiguations. Examples: "The term example could refer to any of the following.", "In the ''Pikmin'' series, the following are examples:". The first mention of the subject on this opening paragraph should be bolded. | ||
The list of articles should be in a bullet point format. Each bullet point starts with the article's name, in bold. If there is an icon associated with it, include it, using {{tem|icon}}. After the article's link, there should be a colon and a brief introduction to what the subject is about, and how it is different from the rest of the disambiguation links; this introduction should start in lowercase (it's still the same sentence) and end in a period. The list may have more than one level, if it makes sense organizing it that way, and if it helps readers find the page they want more quickly. | The list of articles should be in a bullet point format. Each bullet point starts with the article's name, in bold. If there is an icon associated with it, include it, using {{tem|icon}}. After the article's link, there should be a colon and a brief introduction to what the subject is about, and how it is different from the rest of the disambiguation links; this introduction should start in lowercase (it's still the same sentence) and end in a period. The list may have more than one level, if it makes sense organizing it that way, and if it helps readers find the page they want more quickly. Splitting by level is especially useful for subjects unique in each game. If the player wants to know what treasure a "ring" in ''Hey! Pikmin'' is, they can check the game's section right away instead of navigating the whole list item by item just to find the ''Hey! Pikmin'' entries. Try to sort the list alphabetically, unless it's abundantly likely that the reader wants some article more than the others. | ||
After the list, if needed, there should be a paragraph or more detailing further pages that could interest a reader that is searching for the ambiguous subject. | After the list, if needed, there should be a paragraph or more detailing further pages that could interest a reader that is searching for the ambiguous subject. | ||
Line 14: | Line 15: | ||
Throughout the page, add links like you would on a normal page, and only link to a keyword the first time it is mentioned in the page. Finally, at the end of the page, include {{tem|disambiguation}} and nothing else. | Throughout the page, add links like you would on a normal page, and only link to a keyword the first time it is mentioned in the page. Finally, at the end of the page, include {{tem|disambiguation}} and nothing else. | ||
{{ | {{guidelines}} | ||
[[Category:Guidelines]] | [[Category:Guidelines]] |
Latest revision as of 08:40, April 29, 2024
These guidelines apply to specific types of pages.
Disambiguation pages
Shortcut: |
Disambiguation page names should only contain the name of the ambiguous subject. Only append "(disambiguation)" to the title if a subject-only title is already a thing in the series, would be better suited as a redirect to something else, or if the disambiguations pages also use something in parenthesis in their title. You can create a disambiguation page for any subject, whether it has two disambiguation links or multiple, but make sure that it wouldn't be better to use a {{redirects}}, {{for}}, or something similar instead.
Disambiguation pages for a subject that is purely a search title (like "green") should be avoided. In essence, a disambiguation page is helpful for when a reader searches for something they don't know the exact title of, and we know that there is a very high chance that they wanted this or that article.
These pages should start with one or two sentences describing why the subject is ambiguous and introducing a list of disambiguations. Examples: "The term example could refer to any of the following.", "In the Pikmin series, the following are examples:". The first mention of the subject on this opening paragraph should be bolded.
The list of articles should be in a bullet point format. Each bullet point starts with the article's name, in bold. If there is an icon associated with it, include it, using {{icon}}. After the article's link, there should be a colon and a brief introduction to what the subject is about, and how it is different from the rest of the disambiguation links; this introduction should start in lowercase (it's still the same sentence) and end in a period. The list may have more than one level, if it makes sense organizing it that way, and if it helps readers find the page they want more quickly. Splitting by level is especially useful for subjects unique in each game. If the player wants to know what treasure a "ring" in Hey! Pikmin is, they can check the game's section right away instead of navigating the whole list item by item just to find the Hey! Pikmin entries. Try to sort the list alphabetically, unless it's abundantly likely that the reader wants some article more than the others.
After the list, if needed, there should be a paragraph or more detailing further pages that could interest a reader that is searching for the ambiguous subject.
Throughout the page, add links like you would on a normal page, and only link to a keyword the first time it is mentioned in the page. Finally, at the end of the page, include {{disambiguation}} and nothing else.
Pikipedia guidelines | |
---|---|
Content | Claims • General • Object list • Page title |
Specific article types |
Areas • Caves • Collectibles • Enemies • Families • Games • Pikmin types • Others |
Templates | General • Navigation box |
Conduct | Behavior |
Policies • Guidelines • Procedures • Help |