Forum:Proposal to Organize Bracketed Addendums in Titles: Difference between revisions
From Halopedia, the Halo wiki
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Forumheader/Archive}} | {{Forumheader/Archive}} | ||
Hello there Halopedia, and addressing you today is none other than Halo-343; you know, that guy. This proposal, as its lengthy title might suggest to an attentive human being, is regarding the largely unneeded usage of bracketed addendums on Halopedia. I made a [[Talk:Main Page#Usage of bracketed addendums in article titles|similar post]] regarding this several days ago, and in response to agreement from several users, I've decided to formalize my suggestion, which this explanatory introduction now introduces. | Hello there Halopedia, and addressing you today is none other than Halo-343; you know, that guy. This proposal, as its lengthy title might suggest to an attentive human being, is regarding the largely unneeded usage of bracketed addendums on Halopedia. I made a [[Talk:Main Page#Usage of bracketed addendums in article titles|similar post]] regarding this several days ago, and in response to agreement from several users, I've decided to formalize my suggestion, which this explanatory introduction now introduces. | ||
On to the purpose of this proposal, I've recently begun to notice a large usage of illogical addendums in a sizable amount of article titles lately, particularly those with a level of the same name. To give examples of this; [[343 Guilty Spark]], [[Armory (Room)]], [[High Charity (Structure)]], [[Cairo Station (Platform)]], [[Gravemind (Form)]], [[Kizingo Boulevard (Location)]], [[Tsavo Highway|Tsavo Highway (Location)]], [[Arbiter|Arbiter (Title)]] and countless others. If several articles share the same name, the bracketed distinction should only follow the titles of those named after the primary subject. For example, there are two instances in the Halo series titled "343 Guilty Spark"; the monitor and the level. The level is named after the monitor, thus should be the only article using bracketed information in its title to distinguish it from the primary subject, with a small note at the top of the page to cover any confusion ("Were you looking for ____?"). In addition to this, real-world subjects such as levels should not hinder the titling of a primary in-canon subject. If there is more than two instances, Gravemind for instance, the same rule should apply, but with a disambiguation page made to organize the other secondarily named pages, again with a note linking to it ("For other uses of "Gravemind", see Gravemind (disambiguation)"). In addition to this, in conjunction with Dragonclaws' proposal regarding capitalization, in instances where bracketed addendums are required, such wording should be lower case, not capitalized. For example, "(level)" is correct, "(Level)" is not. | On to the purpose of this proposal, I've recently begun to notice a large usage of illogical addendums in a sizable amount of article titles lately, particularly those with a level of the same name. To give examples of this; [[343 Guilty Spark]], [[Armory (Room)]], [[High Charity (Structure)]], [[Cairo Station (Platform)]], [[Gravemind (Form)]], [[Kizingo Boulevard (Location)]], [[Tsavo Highway|Tsavo Highway (Location)]], [[Arbiter|Arbiter (Title)]] and countless others. If several articles share the same name, the bracketed distinction should only follow the titles of those named after the primary subject. For example, there are two instances in the Halo series titled "343 Guilty Spark"; the monitor and the level. The level is named after the monitor, thus should be the only article using bracketed information in its title to distinguish it from the primary subject, with a small note at the top of the page to cover any confusion ("Were you looking for ____?"). In addition to this, real-world subjects such as levels should not hinder the titling of a primary in-canon subject. If there is more than two instances, Gravemind for instance, the same rule should apply, but with a disambiguation page made to organize the other secondarily named pages, again with a note linking to it ("For other uses of "Gravemind", see Gravemind (disambiguation)"). In addition to this, in conjunction with Dragonclaws' proposal regarding capitalization, in instances where bracketed addendums are required, such wording should be lower case, not capitalized. For example, "(level)" is correct, "(Level)" is not. | ||