MarioWiki:Proposals

List of Talk Page Proposals

 * Merge Nep-Enut (Yoshi's Woolly World) with Nep-Enut (Discuss) Deadline: January 4, 2016, 23:59 GMT
 * Split from Rope (Discuss) Deadline: December 29, 2015, 23:59 GMT Extended: January 5, 2016, 23:59 GMT
 * Merge Short Fuse and Seedy Sally with Ukiki (Discuss) Deadline: January 11, 2016, 23:59 GMT
 * Merge 5 Gold Coin and 50 Gold Coin with Coin (Discuss) Deadline: January 13, 2016, 23:59 GMT
 * Use only when pages clearly have an informal appearance (Discuss) Deadline: January 15, 2016, 23:59 GMT
 * Create the page: Drilldigger (Discuss) Deadline: January 17, 2016, 23:59 GMT
 * Split the sections Attackathlon, Toad Quiz and Lakitu Info Centre into and  (Discuss) Deadline: January 18, 2016, 23:59 GMT
 * Split Gold Bar and (Discuss) Deadline: January 18, 2016, 23:59 GMT

Writing Guidelines
None at the moment.

New features
None at the moment.

Removals
None at the moment.

Prohibit the Usage of in Headers
Using in headers has a couple of issues. For one, it looks ugly and inconsistent with how other headers look like. The only acceptable text formatting in headers should be italicising as to indicate that it's a piece of fiction being talked about. Underlining text in headers is very bad. Furthermore, it breaks the Recent Changes. Using the Recent Changes, a user may jump directly to a section of an article if only a section was edited. However, should the header contain, this feature is broken. Having a feature that breaks a vital function of the Wiki should never be allowed. Sure, you could just hop to the section manually, but why would you do that when the Wiki can provide you a function that does that for you automatically?

I do realise and acknowledge that there is an issue with this: how do we notify the reader that these names are conjectural? The solution is simple.

===Thing that is conjecturally named===  is a thing blah blah blah blah

That way, we get the information that it's conjecturally named across, it doesn't break the Recent Changes, and it makes headers look consistent. This means that all information is preserved, and we don't have to implement a feature that breaks a very vital function of the Wiki. Alternatively and depending on the kind of section being worked with, the text doesn't need to be in a bold typeface. This also gives us the possibility to quickly summarise what the section is about in one sentence before describing the rest of the subject in greater detail. Furthermore, this methodology ensures no unnecessary and ugly notification templates need to be used at all. Additionally, removing does not break section linking at all, so all links that already exist and link to headers that already contain  will not be broken and still work.

But how do we go about finding these? The answer here is also simple. This is how.

Proposer: {{User|RandomYoshi}} Deadline: January 11, 2016, 23:59 GMT

Support

 * 1) – Per proposal.
 * 2) - Per RandomYoshi.
 * 3) Per RandomYoshi.
 * 4) – Per RandomYoshi.
 * 5) - Per Pi.
 * 6) - Per π
 * 7) &mdash; Per RandomYoshi.
 * 8) I hate the use of the conjectural text template in headers, it's time to end that practice once and for all.

Comments
Unfortunately MediaWiki search is broken, so the link you provided will not help us find the pages. But as far as I've seen, the only pages with conjectural section titles are the Galaxies and list of Glitches, which should be easy enough to track down. Otherwise, how is the suggested workaround going to work in the list of glitches pages? It doesn't seem efficient to specify the glitch name in every section. I think we need a better idea to over all say "Yo guys, these are all made up names so don't quote us on them will ya?".-- 12:03, 4 January 2016 (EST)
 * How about making a similar template to Template:Conjecture, but that states something like "The titles of the following sections of this article are conjectural; [and the rest is equal to the base template]"? It could have a "section=" variable that, if set to yes, states "The title of the following subsections of this section [equal to normal]". The first is used in glitch pages, the second in Galaxies pages.
 * Having additional notice templates is only going to help in increasing how messy pages look like. It's not going to be the end of the world if we repeat it for every subject we talk about. In fact, it's better to first aptly summarise a subject in one concise sentence before prattling on about the minor details of a subject: that way, readers who only wish to gain an elementary understanding of a topic can choose only to read the first sentence of a paragraph, whilst others that feel like they want a more in-depth analysis can do so by continuing to read about the subject. Because is used in the beginning of the sentence and has the subject bolded (or not), the information that they're conjecturally named is still going to be conveyed in the same way it's done at this point, except it won't break the Recent Changes and generate unprofessional-looking headers. To summarise, it won't hurt us, it won't hurt the reader, it won't hurt the page by introducing a whole batch of notice templates, and it certainly won't hurt the Recent Changes.  13:47, 4 January 2016 (EST)
 * No, it would be repetitive to state the nonofficial name of the glitch underneath every glitch section with that exact same title, it seems okay in the introduction of main articles, because you really are introducing the main element of the page, however in glitches' pages, it becomes overly annoying to read the same thing over and over again. It's like going over every section in the Mario article starting it with "[..] is a game that Mario stars in." which would be insane. Don't get me wrong, I support this proposal, because this issue is super annoying when it comes to actual editing and linking. However, the consequences of doing it this way is not something I support. I don't support the idea of the notice template either, it would be an eye catcher. However, adding it to the introduction of the list in one short sentence is not something I'm keen on, but not something I'm against either.-- 15:10, 4 January 2016 (EST)

Miscellaneous
None at the moment.