MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
mNo edit summary
 
Line 1: Line 1:
{{MarioWiki:Proposals/Header}}
{{/Header}}


===List of Talk Page Proposals===
==Writing guidelines==
*Change the board table layout for [[Mario Party: Island Tour]] back to the original one ([[Talk:Mario Party: Island Tour#Board Chart|Discuss]]) '''Deadline:''' February 5, 2013, 23:59 GMT
''None at the moment.''
*Stop considering [[Mattermouth]]s as Dry Bones ([[Talk:Mattermouth#Stop considering Mattermouths as Dry Bones|Discuss]]) '''Deadline''': <s>January 16, 2014, 23:59 GMT</s> '''Extended''': <s>January 23, 2014, 23:59 GMT</s>, February 6, 2014, 23:59 GMT
*Merge [[Bat (Luigi's Mansion)]] with [[Bat (Luigi's Mansion: Dark Moon)]] ([[Talk:Bat_(Luigi%27s_Mansion:_Dark_Moon)#Merge_Luigi.27s_Mansion_Bat_with_Luigi.27s_Mansion:_Dark_Moon_Bat|Discuss]]) '''Deadline:''': February 10, 2014, 23:59 GMT


==Writing Guidelines==
==New features==
===Further separate appearance listing by medias===
===Create a template to direct the user to a game section on the corresponding List of profiles and statistics page===
{{llquote|[...]The cartoons, the movie, etc. are all different entries in the same franchise. You wouldn't lump Transformers G1, Beast Wars, Robots in Disguise, Armada, Animated and the Michael Bay movies together into one giant uncategorized mess, nor would you do the same with the Pokémon games, anime, manga, and TCG, nor would you do the same with the Sonic games, DiC cartoons, OVA, manga, Archie comic and Fleetway comic. This is why sites that catalog information on these franchises do exactly that. They separate the different entires of the franchises into categories, because even though they're all part of the same franchise they're still wholly different entities that don't cross into one another. It also makes it easier to look up informaton on something from a specific entry in a given franchise. This is how an online encyclopedia is supposed to work - it should be as easy and efficient to find the information you want as possible.|A Donkey Kong Universe poster}}
This proposal aims to create a template that directs people to a game section on a Profiles and statistics list page, saving the user the step of having to scroll for it themselves. The reason why I'm proposing this is because as more ''Super Mario'' games are released, it becomes harder to comfortably find what you're searching for in the corresponding List of profiles and statistics page, especially for [[Mario]], [[Bowser]], and many other recurring subjects.


In the early days of the wiki, appearance listing on character pages used to be separated by media (so all games were under a <nowiki>==Game==</nowiki> header, all comics under a <nowiki>==Comic==</nowiki> and so on) up until around 2008, where it was proposed to not separate things by media (the ensuing change mostly consisted of [http://www.mariowiki.com/index.php?title=Mario&oldid=764279#Super_Mario_Bros.:_The_Lost_Levels terrible attempts to link contradictory medias together]), which was further stabilized into the purely date-based listing we have now. I was pretty apathetic about the change, but the quote above made me think.
Another reason I think this would be valid is because of the fact that listing statistics in prose (e.g. 2/10 or 2 out of 10) looks off, especially if that can already be seen in the corresponding statistics box; in that case, the prose could change from "2/10" to something more vague like "very low stat", which isn't typically worded as such in the statistics box.


The current system's well-intentioned, but I feel it's misguided and that separating things by media would lead to a more user-friendly browsing experience. Here's why:
For example, let's say for [[Luigi]] in his appearance in ''[[Mario Sports Superstars]]'', there could be a disclaimer either below the section heading or in a box to the side (we can decide the specifics when the proposal passes) that informs the reader that there's corresponding section that shows his profiles/statistics corresponding. Like such:


1: It's a navigational mess. To take the [[Mario]] page for example, the main series platformers and the sports spinoff that most readers would expect to be "logically" close (due to similar styles and being, well, the same ''format'') are separated by a wall of info about the more distant DIC cartoons and obscure OVAs.  As a reader, I think it's irritating and a jarring shift.
:''For profiles and statistics of Luigi in Mario Sports Superstars, see [[List of Luigi profiles and statistics#Mario Sports Superstars|here]].''


Separating things by media would also have the effect of making the content navbar less bloated, thus making it easier to eyeball and click straight to a specific game/movie/cartoon. If I want to know about how many comics Mario has appeared in or that I want to read about a specific appearance but that I don't remember the name or publication date, it's much easier to find what I'm looking with a separated listing rather than having it lost somewhere in a huge list. It could also have the effect of making sections about obscure installments more noticeable than when they are sandwiched between the better-known and better-documented games.
The above message is not necessarily the final result (just a given example), but the disclaimer would definitely point the user to the appropriate game section on the profiles and statistics list page, should this pass.


2: One can peddle the "There's no official canon" line and that ''is'' true (and hence why I'm not proposing to give special treatment to [[Hotel Mario]], When I Grow Up, the edutainement games or other oft-disliked installments of the franchise, because that'd be dumb) – but it misses the actual point: the media tie-ins are separate ''entries'' of the franchise. Events in the other medias usually happen in their own bubble  and are not directly patterned after or "follow" the games. No characters that originated in the comics/cartoons/OVA reappears (with maybe the exception of the [[Koopa Bros.]] in a manga, but details are sketchy) appear or are even alluded to in the games. The characters/items that do appear frequently have clear differences in appearance, function, personality and sometimes names (some of that can be chalked up to early-franchise weirdness, but that only goes so far). 
'''Proposer''': {{User|Super Mario RPG}}<br>
'''Deadline''': January 1, 2025, 23:59 GMT


Even obscure, one-note games like [[Yoshi's Universal Gravitation]] and [[Wario: Master of Disguise]] have enough stylistic consistency and continuity cues that show they're meant to exist in the same "universe" as other games in their respective franchises, even if they're not referenced later. You can't say the same about the DIC cartoons vs the games.
====Support====
#{{User|Super Mario RPG}} Per.
#{{User|Hewer}} I don't really see a need to deliberately make prose less specific, but otherwise I like this idea, per proposal.


Beside, there is a precedent for splitting other medias: The characters in the 1993 movie [http://www.mariowiki.com/MarioWiki:Proposals/Archive_29#Super_Mario_Bros._Film_Information:_Where_Should_It_Go.3F are considered] to be "different" and indeed, most major elements from the film do have separate pages. If the movie is "too different" to count, then what about the Super Show with its locations that appear nowhere else in the franchise, celebrity guest stars, sizable number of characters that barely resemble their game counterpart… etc?. It takes a lot of mental gymnastic to exclude one but not the other.
====Oppose====


Separating the medias isn't saying the comics/cartoons/ovas aren't "canon", "don't count" or something like that – it's simply acknowledging they're separate entries of the greater Mario franchise, which they quite clearly are, methinks.
====Comments====
{{@|Hewer}} I don't think this would necessarily eliminate cases in which statistics are in prose, but it may be redundant if there's the link to conveniently access the statistics or profiles. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 15:15, December 18, 2024 (EST)


…[/Martin Prince voice]
===Add an abbreviation template to type out full game titles===
This proposal is about creating a template that it makes it easier to type out full game titles. Although ''The Legend of Zelda'' games generally have longer titles (and Zelda Wiki even has templates for some of their shorter titled games, like ''{{iw|zeldawiki|Hyrule Warriors}}'', {{iw|zeldawiki|Template:HW|here}}), there have still been cases in which some game titles are uncomfortably long, such as ''[[Donkey Kong Country 3: Dixie Kong's Double Trouble!]]'' or ''[[Super Mario RPG: Legend of the Seven Stars]]'', and while it may seem like not a big deal to some, it would be a small quality-of-life improvement if we could have a template where we input the abbreviation, and the output becomes the game title.


'''Proposer''': {{User|Glowsquid}}<br>
For example, <nowiki>{{a|M&LSS}}</nowiki> would result in ''Mario & Luigi: Superstar Saga'' (complete with italics formatting). Meanwhile, <nowiki>{{a|M&LSS|l}}</nowiki> to link to the game, outputting ''[[Mario & Luigi: Superstar Saga]]'', although depending on who creates the template, it could be vice versa, like it links by default and <nowiki>{{a|M&LSS|n}}</nowiki> would prevent a link.
'''Deadline''': February 19th, 2014, 23:59 GMT
 
Since ''Super Mario'' has several releases, it may get difficult maintaining with all the abbreviations, and there have been cases where two games have shared the same abbreviation. (e.g. [[SMS]] for both ''Mario Sunshine'' and ''Mario Strikers''). In that case, either <nowiki>{{a|SMS|2002}}</nowiki> (with the year of release) or a custom abbreviation (e.g. <nowiki>{{a|SMShine}}</nowiki>) would be needed (personally I'd prefer the latter).
 
Consider we already have similar templates for Princess Peach and Princess Daisy (i.e. {{tem|Peach}} and {{tem|Daisy}}), and both of their full titles (with "Princess" included) is a lot shorter than the two game titles in the first paragraph.
 
'''Proposer''': {{User|Super Mario RPG}}<br>
'''Deadline''': January 1, 2025, 23:59 GMT


====Support====
====Support====
#{{User|Glowsquid}}
#{{User|Super Mario RPG}} Per.
#{{User|Camwoodstock}} We don't see the harm in this, even if it would admittedly be fairly niche. The only real complaint we have is the lack of an additional parameter for changing the displayed text, so if we need to say something like "in the [[Paper Mario: The Thousand-Year Door (Nintendo Switch)|remake]]", we have to write that out the old-fashioned way.
#{{User|EvieMaybe}} might make some link-heavy pages lighter!
#{{User|Salmancer}} Words cannot express the relief that my fingers would feel if they never have to type out "Mario & Luigi: Bowser's Inside Story + Bowser Jr.'s Journey" again.
#{{User|Tails777}} Mario already took my example, but it still stands; the amount of times I've had to type out that title (or even the abbreviation for it) was incredibly annoying. Per all.
#{{User|Scrooge200}} Yes, these titles can be a pain to write out in full. Per all.


====Oppose====
====Oppose====


====Comments====
:{{@|Camwoodstock}} Such a parameter can always be added to the template. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 18:18, December 18, 2024 (EST)
Salmancer: ''[[Mario & Sonic at the Sochi 2014 Olympic Winter Games]]'' might be the other worst game title I've had to type out. {{User:Mario/sig}} 00:59, December 20, 2024 (EST)
:Damn it, that was gonna be my example! {{User:Tails777/sig}}15:34, December 20, 2024 (EST)
===Split image categories into separate ones for assets, screenshots, and artwork===
This proposal will address the bloat some image categories have and make them easier to navigate.
Why is this useful? It makes adding to galleries or finding images to replace much easier. If you want to retake screenshots from a game, you can go to the screenshots category to find them. If you have sprite rips to replace, there's a category for that. The same goes for finding images from a game that aren't on the gallery already and being able to sort them more efficiently. This is also how we divide up character galleries already, such as [[Gallery:Mario (2010-2019)]].
Now, I can see a few edge cases, like when games have screenshots of themselves for credits images (i.e. ''[[Paper Mario: The Thousand-Year Door (Nintendo Switch)]]''). I would still classify these as assets, since they are ripped from the game. Artwork that is used in smaller forms in-game, such as in ''[[Super Mario Maker 2]]'', would be classified as artwork if externally released or an asset if it was ripped from the game files. Edge cases shouldn't be too common and they're easy to work out: it's not too different from how we license images or put them in character or subject galleries.
I think the name "assets" would be more useful in shorthand than "sprites and models," in addition to covering textures, so I propose for the category to be called that, but I can change it if there's opposition. The global images category can still exist in the case there's scans, merchandise, video screenshots, or such images that cannot be further categorized.
'''Proposer''': {{User|Scrooge200}}<br>
'''Deadline''': January 5, 2025, 23:59 GMT
====Support====
#{{User|Scrooge200}} Per proposal.
====Oppose====


====Comments====
====Comments====
I dunno if the [[Super Mario-Kun]] is part of this: what the manga is about is that it adapts events straight out of the game and puts its own twist to it, unlike most other forms of media where they just do their own thing. But otherwise, yeah, I see where you're going with this. {{User|Baby Luigi}}
:The ''Super Mario-Kun'' is probably part of it because it also follows a slightly different story that no other games gave a nod to, and the characters are given distinct personalities never seen in the games. You'll probably never catch Mario cross-dressing or molding a Star to the shape of a revolver, do you? Nevertheless, ''Super Mario-Kun'''s character designs are usually spot-on with their video game counterparts, even getting the details correct (while adapting its own style) {{User|Mario}}


So, Glowsquid, what will you propose to do? Split Mario's article into separate articles by media? I'll very much like the idea (I also agree that the History's organization seems sporadic and jarring, especially to readers... and plus, Mario's article gets trimmed even more! YES! Same goes for Luigi, Toad, Bowser, Wario, Boo, etc.), but I also like to see the formatting layouts because that means we can also go into detail about episodes and certain comic volumes and issues without cluttering up the page.
==Removals==
''None at the moment.''


A ''serious'' flaw from this proposal is the smaller articles. Minor ''Mario'' characters such as [[Tryclyde]], [[Tweeter]], [[Panser]], [[Wanda]], [[Jō]], and much more also make appearances in non-game media, yet their articles are smaller than the main ones that really need this solution. Even one-timers such as [[Lavalava Island]] and [[Golden Diva]] make a non-game appearance from Super Mario-Kun. Even further, we've seen some extraordinary appearances such as [[Bluster Kong]], who made an appearance in ''Super Mario-Kun'', although he originated in a TV show. What may happen from this proposal is separating information from already-small articles into even smaller articles. There isn't anything in your proposal to address that, so... {{User|Mario}}
==Changes==
===Broaden the scope of the <nowiki>{{rewrite}}</nowiki> template and its variations===
With the [[Template talk:Unreferenced#Delete or be more specific|previous proposal]] having passed with being more specific as the most voted, I've come up with a proposal about the possibility to make the {{tem|rewrite}}, {{tem|rewrite-expand}}, and {{tem|rewrite-remove}} templates more specific. As you can see, these templates are missing some smaller text. As such, I am just wondering if there is a possibility to have the smaller text added to the <nowiki>{{rewrite}}</nowiki>, <nowiki>{{rewrite-expand}}</nowiki>, and <nowiki>{{rewrite-remove}}</nowiki> templates.


I brought up the Movie thing to show that the current system is inconsistent rather than to say "That? We should do that for ''everything''". The idea is that currently, all medias are under one header, like this;
First of all, the <nowiki>{{rewrite}}</nowiki> template currently reads as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>
</pre>


--History--<br>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
---Main Platformers---<br>---Super Mario Land---<br>---DIC Cartoons---<br>---Obscure OVAs---<br>---Educational Games---
It has been requested that this article be '''rewritten'''.
</div>
----
However, once the proposal passes, the <nowiki>{{rewrite}}</nowiki> template will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}}.</small>
</div>
</pre>


With the proposal, the page sections would be formated like this:<br>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
-History-<br>
It has been requested that this article be '''rewritten''' for the following reason(s): <reason(s)>.<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}}.</small>
--Games--<br>
</div>
---Main Platformers---<br>
----
---Super Mario Land---<br>
And another thing—the <nowiki>{{rewrite-expand}}</nowiki> template currently reads as follows:
---Educational Games---<br>
----
--Animation--<br>
<pre>
---DIC Cartoons---<br>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
---Obscure OVAs---<br>
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
I'm not saying the DIC, Valiant... etc portrayals of Mario should get separate pages, though for what it's worth, Steve wants the detailled episode-by-episode summaries to be on separate pages ([[List of Donkey Kong Country episodes featuring Donkey Kong|like this]]), so for major characters, the main page could have a general description of their portrayal and general storyline, with the individual episode summaries being linked via <nowiki>{{main}}</nowiki>. The idea could be extended to other long-running medias like Super Mario-kun and the Valiant comics. And of course secondary characters shouldn't be split, that'd be dumb. --[[User:Glowsquid|Glowsquid]] ([[User talk:Glowsquid|talk]]) 07:07, 6 February 2014 (EST)
</div>
:Huh, I had the wrong idea, then. It must've been that "separate" word that gotten to me. {{User|Mario}}
</pre>


==New features==
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
===Create an [unconfirmed glitch] template===
It has been requested that this article be '''rewritten''' and '''expanded''' to include more information.
[[ForumLink:index.php?topic=28897|Collab Link]]
</div>
----
However, once this proposal passes, the <nowiki>{{rewrite-expand}}</nowiki> will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information.{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by filling in the missing details.</small>
</div>
</pre>


While navigating through glitches pages, I came across several glitches which I was unable to perform, nor did I managed to find any proof that this glitch is real or fake. So instead of [[MarioWiki:Proposals/Archive_34#Remove_all_unsourced_information_from_glitches_and_beta_elements_pages|removing all unsourced glitches]], we would simply add a small notice like this<sup class="noprint">&#91;''unconfirmed glitch''&#93;</sup>. This way we will still have the information, while avoiding any bogus glitches (because the reader would be already aware that this glitch was not tested, unproved).
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' and '''expanded''' to include more information for the following reason(s): <reason(s)>.<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}} by filling in the missing details.</small>
</div>
----
Lastly, the <nowiki>{{rewrite-remove}}</nowiki> currently reads as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have <u>{{{content|{{{1|content<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}</u> '''removed''' for the following reason(s): {{{reason|{{{2|???<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}
</div>
</pre>


I already aware that there is a template called {{tem|refneeded}}. However this is a different thing: not every glitch need a reference. they need just an screenshot, a video, or in some cases, discussion on the talk page may be very enough if provided with some proof. Also having a different template and a different category is better for organizing, this way we can look in the category to find all glitches pages ''only'' which contains glitches need confirmation.
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' to have <u>content</u> '''removed''' for the following reason(s): ???
</div>
----
However, once this proposal passes, the <nowiki>{{rewrite-remove}}</nowiki> will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have {{#if:{{{content|{{{1|}}}}}}|<u>{{{content|{{{1}}}}}}</u>|content}} '''removed'''{{#if:{{{reason|{{{2|}}}}}}|<nowiki/> for the following reason(s):{{{reason|{{{2}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by removing the unnecessary details.</small>
</div>
</pre>


'''Draft:'''
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
<pre><sup class="noprint">&#91;''unconfirmed glitch''&#93;</sup><includeonly>[[Category:Glithes need confirmation]]</includeonly><noinclude>[[Category:Formatting Templates|{{PAGENAME}}]]</noinclude>
It has been requested that this article be '''rewritten''' to have content '''removed''' for the following reason(s): <reason(s)>.<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}} by removing the unnecessary details.</small>
</pre>
</div>
----
That will be a perfect idea to make the <nowiki>{{rewrite}}</nowiki> template and its variations as more specific as the {{tem|media missing}} and {{tem|unreferenced}} templates. That way, we'll be able to add smaller text to the remaining [[:Category:Notice templates|notice templates]] in the future.


'''Proposer''': {{User|Megadardery}}<br>
'''Proposer''': {{User|GuntherBayBeee}}<br>
'''Deadline''': <s>February 3, 2014, 23:59 GMT</s>, Extended: February 10, 2014, 23:59 GMT
'''Deadline''': December 23, 2024, 23:59 GMT


====Support====
====Support====
#{{User|Megadardery}}
#{{User|GuntherBayBeee}} Per proposal
#{{User|Baby Luigi}} Per Meggy
#{{User|Randombob-omb4761}} Per proposal
#{{user|Mario7}} Per proposal. I think this would be a great idea.
#{{user|Green 6017 King Of The Slowpoke}} Per all. This is a great idea, especialy for a glitch hunter like me.
#{{User|Robecuba}} Per proposal


====Oppose====
====Oppose====
#{{User|Walkazo}} - Just use {{tem|refneeded}}: an unconfirmed glitch is no different from any other unconfirmed bit of info, and needs to be backed up by the exact same kind of sources. Furthermore, the template would just categorize the whole list page, not the specific glitch: in all likelihood, every long page will end up languishing in the category, probably from multiple templates (not that you could tell from looking at the category), which isn't useful: better to just use the collab to keep track of things.
#{{User|Altendo}} As far as I can tell, the proposal that was linked added parameters that allowed what was supposed to be referenced to be referenced. This one simply adds a subtitle to the bottom of each template. "Be more specific" does not mean saying general information and helpful links, but rather exactly what needs to be done; in terms of that, the existing templates not only all already have parameters, but [[MarioWiki:Proposals/Archive/61#Discourage drive-by templating|filling them out is enforced]]. As [[User:Nightwicked Bowser|Nightwicked Bowser]] said, "Be more specific - Similar to [[MarioWiki:Proposals/Archive/61#Discourage drive-by templating|this proposal]], what exactly needs references must be specified in the template when putting it in the article. A parameter for this will still need to be added." This only adds a subtitle and does not make this "more specific". As for the changes, this is actually harmful in some way, as the <nowiki>(tagged on {{{date|{{{3}}}}}})</nowiki> tag will be added to the subtitle, rather than the main body, which could make it more confusing in my opinion. Feel free to update this and add in what "more specific" actually means, or just change this to "add subtitles" and change the location of <nowiki>(tagged on {{{date|{{{3}}}}}})</nowiki> to the main body, but until then, my vote is staying here.
#{{User|Pinkie Pie}} Per all.
#{{User|Mario}} Best to keep things simple with these improvement templates.
#{{User|Lord Grammaticus}} - Per Walkazo, this proposal looks to me like it's basically founded on a bunch of semantic issues.
#{{User|Mario}} Uploading a screenshot and a video should be enough to remove both templates, so the proposed template will be pretty much redundant.
#{{User|driftmaster130}} Per all.
#{{User|Yoshi876}} Per all.
#{{User|Marshal Dan Troop}} Per all.
#{{User|Mario4Ever}} Per all.
#{{User|Jazama}} Per all


====Comments====
====Comments====
Screenshots and videos ''are'' references, and citing discussions isn't ideal even for glitches (although citing discussions beats no citations at all, of course). And what do you mean by "scrawny" "sourcing thing"? Citations are used ''all over'' the wiki, and so they should: they lend credibility to the database. Whoever told you references are only for upcoming games and beta elements is grievously mistaken. - {{User|Walkazo}}
:Sorry, I was mistaken. After reading [[MarioWiki:Citation_Policy]] in depth again, I knew that information can be taken directly from the game without the need of external resources. Whatever, I guess this proposed feature should be separated from the {{tem|refneeded}}, this way the category will contain all the pages that weren't tested by our users thus they aren't confirmed. About the citing discussion, take Flip'd-up Mario 1 as an example, a user confirmed this on the talk pages even describing it more, another user confirmed the glitch and confirmed his description (both users do not have capture cards), thus the glitch is confirmed, BUT it needs a reference. so replacing the {{tem|UnconfirmedGlitch}} with the {{tem|refneeded}}. Take Bananaport Glitch as an example, it does have an image, however I started a discussion on the talk page saying that it never happened for me, some more users said so. The {{tem|UnconfirmedGlitch}} get added to the glitch, even when it really has an image (a reference. {{User|Megadardery}}
::You can still use {{tem|refneeded}} in cases where some evidence is provided but more is needed. And more than anything, the story about "Flip'd-up Mario 1" just proves that the differences in use between the established template and the proposed addition is splitting hairs and adding unnecessary complications to the straightforward process of confirming glitches (nothing<sup>refneeded</sup> -> disucssion-but-no-hard-proof<sup>cite talk page so readers can decide for themselves if they trust us</sup> -> hard-evidence<sup>cite ''that'' and be happy</sup>). - {{User|Walkazo}}


:A new template sounds redundant, but maybe {{tem|refneeded}} could be modified to read "unconfirmed glitch" or something? {{user|driftmaster130}}
Here's how I would fix some things:


:::Sorry, but I don't quite understand you.{{User|Megadardery}}
First of all, the <nowiki>{{rewrite}}</nowiki> template currently reads as follows:
::::Which part? - {{User|Walkazo}}
----
:::::"(nothingrefneeded -> disucssion-but-no-hard-proofcite talk page so readers can decide for themselves if they trust us -> hard-evidencecite that and be happy)"{{User|Megadardery}}
<pre>
::::::@Walkazo Like this: <sup class="noprint">&#91;[[MarioWiki:Citation Policy|''unconfirmed glitch, citation needed'']]&#93;</sup><includeonly>[[Category:Citation needed]]</includeonly><noinclude>[[Category:Formatting Templates|{{PAGENAME}}]]</noinclude>; and it could be modified like {{tem|Userspace}} was for double usage. I don't know if that seems redundant or not but at least it highlights glitches more. {{user|driftmaster130}}
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
:::::::But don't you think that's getting a wee bit long and unseemly? Anyway, what I meant was that first, if someone adds a glitch with no refs or anything, you can just label it with {{tem|refneeded}}. Then maybe it gets discussed on the talk page and people convincingly vouch for its existence - then you cite the discussion, and it's up to the readers to look at the citation and decide whether they believe our info despite us not having any hard evidence. Then you ''do'' find some hard evidence and can cite that instead, and when readers see that, they won't have any reason to doubt us (i.e. everybody's happy). No need for a clunky extra template or template parameter: you either have a reference, or ya don't. It also just occurred to me that if you really want to keep track of unconfirmed glitches and don't trust a list on the wiki collabs board, why not use {{tem|talk}} or a template spun off of that to put on the talk pages? You'd still get the useless category problem, but at least the templates will draw attention to the appropriate sections on the talk page once folks wander in. - {{User|Walkazo}}
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>
</pre>


==Removals==
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten'''.
</div>
----
However, once the proposal passes, the <nowiki>{{rewrite}}</nowiki> template will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}}.</small>
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' for the following reasons:<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}}.</small>
</div>
----
And another thing—the <nowiki>{{rewrite-expand}}</nowiki> template currently reads as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' and '''expanded''' to include more information.
</div>
----
However, once this proposal passes, the <nowiki>{{rewrite-expand}}</nowiki> will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by filling in the missing details.</small>
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' and '''expanded''' to include more information for the following reasons:<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}} by filling in the missing details.</small>
</div>
----
Lastly, the <nowiki>{{rewrite-remove}}</nowiki> currently reads as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have <u>{{{content|{{{1|content<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}</u> '''removed''' for the following reason(s): {{{reason|{{{2|???<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' to have <u>content</u> '''removed''' for the following reason(s): ???
</div>
----
However, once this proposal passes, the <nowiki>{{rewrite-remove}}</nowiki> will read as follows:
----
<pre>
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have {{#if:{{{content|{{{1|}}}}}}|<u>{{{content|{{{1}}}}}}</u>|content}} '''removed''' {{#if:{{{reason|{{{2|}}}}}}|<nowiki/> for the following reasons:{{{reason|{{{2}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by removing the unnecessary details.</small>
</div>
</pre>
 
<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this article be '''rewritten''' to have content '''removed''' for the following reason(s):<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this article}} by removing the unnecessary details.</small>
</div>
 
This should fix some things, and I also recommend you change the title or at least context of this proposal. If so, then I might change my vote. [[User:Altendo|Al]][[User talk:Altendo|ten]][[Special:Contributions/Altendo|do]] 19:58, December 9, 2024 (EST)
:I {{plain link|https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&diff=prev&oldid=4457576|fixed this problem}} for you. How does it look? {{User:GuntherBayBeee/sig}} 09:40, December 10, 2024 (EST)
 
===Decide what to do with Template:Move infobox===
A while ago (November 4th, specifically), I created [[Template:Move infobox]]. After all, we had templates for essentially all the Browse tabs on the wiki sidebar, except for moves. There WERE templates about specific types of moves, such as [[Template:M&L attack infobox]], but no general template in the same vein as items, characters, species, games, locations, etc.
 
I discussed it on the Discord briefly, nobody said no, and a bit of feedback later about how it should look and what it should have, I created it. It has since been applied to exactly four pages at the time of writing, half of which I was the one to apply it to. In hindsight, this could've used with a proposal instead of me just making it, so here's a belated one.
 
Should we keep '''Template:Move infobox''' around? If we do keep it, is it good as is, or does it need changes?
 
'''Proposer''': {{User|EvieMaybe}}<br>
'''Deadline''': January 1st, 2025, 23:59 GMT
 
====Keep Move infobox, as is====
#{{User|Sparks}} I can see this template working really well for moves that aren't in every ''Mario'' game, like [[Spin]]. This has lots of potential!
#{{User|Nintendo101}} Per proposal.
#{{User|Camwoodstock}} We don't see why not--having a dedicated Moves infobox could come in handy, especially if we get any more Mario RPGs in the wake of the weird little renaissance period we've been getting with the back-to-back-to-back SMRPG remake, TTYD remake, and release of Brothership. Per proposal.
#{{User|Pseudo}} Per proposal.
#{{User|Technetium}} Per proposal.
 
====Keep Move infobox, but with changes====
 
====Delete Move infobox====


==Changes==
====Move infobox Comments====
===Move substantial "Official profiles and statistics" sections to a separate page===
Considering the nature of the attack infoboxes, wouldn't it be weird to have moves all in purple but a Mario & Luigi attack use yellow and green and a Paper Mario attack use white and green? Should there be variants of the Move infobox to match the color schemes of existing templates? If an article is covering multiple related moves, how will the infobox work? (ex. [[Handstand]], [[Cap Throw]], [[Roll]], [[Slide Kick]]... there's more of these than I thought). What happens when a move is referenced in somewhat less "move-y" ways? Okay, that last one is kinda strange, but basically I mean "dashing" in Super Mario Run is just a fancy animation, Mario & Luigi Dream Team has an animation where Giant Luigi crouches (with posing and skidding clearly meant to be a platformer callback), to slide under an attack. Do these instances get incorporated into the infobox? Continuing the train of thought, what about sports games? Yoshi can Flutter Jump as his special action on Mario & Sonic games. Does that count as a method of input for a Flutter Jump? [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 21:35, December 19, 2024 (EST)
[[Mario]], [[Luigi]], [[Princess Peach]], [[Toad]], [[Bowser]], [[Yoshi]], [[Donkey Kong]]. One thing in common is that their pages are incredibly huge, and loading them may be a chore for the computer. My proposal is to move some information, specifically large "Official profiles and statistics" sections, from these pages to another page, much as how "Gallery" and "Quotes" have their own page. While this may not be a surefire way to get these pages loading a bajillion times quicker, every little bit helps so we can get potential editors rather than having their browsers crash from the immense size.
:that's a lot of very interesting questions!
:*i went with purple to set it apart from the already taken light red (game), green and white (character), blue (level), pink (location), grey (item) and navy/grey (species) infoboxes. changing the color could be a good idea.
:*as for sorting which moves "count" or not, we have to decide these things for other types of subject too, after all, and they get infoboxes. it's a valid concern, though! {{User:EvieMaybe/sig}} 15:09, December 20, 2024 (EST)


Baby Luigi and I then decided that we should move the "Official profiles and statistics" section to its own page. Now, just as with galleries and list of quotes, not EVERY article will be affected by it; only articles that have a substantial amount of information (decided by a case-by-case basis) will have the information moved.
===Allow blank votes and reclassify them as "per all"===
There are times when users have nothing else to add and agree with the rest of the points. Sure, they can type "per all", but wouldn't it be easier to not to have to do this?


Reasonably reducing the strain these pages do on browsers should be a plus for all of us editors here.
Yeah sure, if the first oppose vote is just blank for no reason, that'll be strange, but again, it wouldn't be any more strange with the same vote's having "per all" as a reasoning. I've never seen users cast these kinds of votes in bad faith, as we already have rules in place to zap obviously bad faith votes.


Update: In addition, profiles and statistics from RPG games, such as ''Paper Mario'', ''Mario & Luigi'' and ''Super Mario RPG'' will be moved into these pages as well.
This proposal wouldn't really change how people vote, only that they shouldn't have to be compelled to type the worthless "per all" on their votes.


'''Proposer''': {{User|Mario}}<br>
'''Proposer''': {{User|Mario}}<br>
'''Deadline''': February 9, 2014, 23:59 GMT
'''Deadline''': January 1, 2025, 23:59 GMT
 
====Blank support====
#{{User|Mario}} Per all.
#{{User|Ray Trace}} Casting a vote in a side is literally an action of endorsement of a side. We don't need to add verbal confirmation to this either.
#{{User|PopitTart}} <small>(This vote is left blank to note that I support this option but any commentary I could add would be redundant.)</small>
#{{User|Altendo}} <small>(Look at the code for my reasoning)</small><!---It might not seem annoying, but over time, or answering multiple proposals at once, it can start putting stress. Copy-pasting can be done, but it is just much easier to not type anything at all.---->
#{{User|FanOfYoshi}}
#{{User|OmegaRuby}} While on the outset it may seem strange to see a large number of votes where people say "per all" and leave, it's important to understand that the decision was made because the user either outright agrees with the entire premise of the proposal, or has read discussion and points on both sides and agrees more with the points made by the side they choose. And if they really ''are'' just mindlessly voting "per all" on proposals with no second thought, we can't police that at ''all.'' <small>(Doing so would border on FBI-agent-tech-magic silliness and would also be extremely invading...)</small> <!---Silent per all.---->
#{{User|Shy Guy on Wheels}} I've always thought of not allowing blank votes to be a bit of a silly rule, when it can so easily be circumvented by typing two words. I think it's better to assume good faith with voting and just let people not write if they don't have anything to add, it's not as if random IPs are able to vote on this page.
#{{user|TheDarkStar}} - Dunno why I have to say something if I agree with an idea but someone's already said what I'm thinking. A vote is a vote, imo.
#{{user|Ninja Squid}} Per proposal.
#{{User|Tails777}} It's not like we're outright telling people not to say "Per all", it's just a means of saying you don't have to. If the proposal in question is so straight forward that nothing else can be said other than "Per proposal/Per all", it's basically the same as saying nothing at all. It's just a silent agreement. Even so, if people DO support a specific person's vote, they can still just "Per [Insert user's name here]". I see no problem with letting people have blank votes, especially if it's optional to do so in the first place.
 
====Blank Oppose====
#{{user|Doc von Schmeltwick}} - Honestly? I'd prefer to get rid of "per all" votes since they're primarily used for the "I don't/like this idea" type of thing that has historically been discouraged. If you don't care enough to explain, you don't care enough to cast IMO.
#{{User|Technetium}} I don't think typing "per all" is that much of an annoyance (it's only two words), and I like clearly seeing why people are voting (for instance, I do see a difference between "per proposal" and "per all" - "per all" implies agreeing with the comments, too). I just don't think this is something that needs changing, not to mention the potential confusion blank votes could cause.
#{{User|Camwoodstock}} Maybe we're a little petty, but we prefer a "per all" vote to a blank one, even if "per all" is effectively used as a non-answer, because it still requires that someone ''does'' provide an answer, even if it's just to effectively say "ditto". You know what to expect with a "per all" vote--you don't really get that information with a fully blank vote.
#{{User|Ahemtoday}} {{color|white|Forgive me for the gimmicky formatting, but I want to make a point here — when you see a blank oppositional vote, it's disheartening, isn't it? Of course, it's always going to be that way when someone's voting against you, but when it doesn't come with any other thoughts, then you can't at all address it, debate it, take it into account — nothing. This also applies to supporting votes, if it's for a proposal you oppose. Of course, this is an issue with "per all" votes as well. I don't know if I'd go as far as Doc would on that, but if there's going to be these kinds of non-discussion-generating votes, they can at least be bothered to type ''two words''.}}
#{{User|Jdtendo}} Per all <small>(is it too much to ask to type just two words to explicitely express that you agree with the above votes?)</small>
#{{User|Axii}} Requiring people to state their reason for agreeing or disagreeing with a proposal leads to unnecessary repetition (in response to Doc). Letting people type nothing doesn't help us understand which arguments they agreed with when deciding what to vote for. The proposer? Other people who voted? Someone in particular, maybe? Maybe everyone except the proposer? It's crucial to know which arguments were the most convincing to people.
#{{User|Pseudo}} Per Technetium, Camwoodstock, and Axii.
#{{User|Hooded Pitohui}} I admit this vote is based on personal preference as any defensible reasoning. To build on Camwoodstock and Ahemtoday's points, though, the way I see it, "per all" at least provides ''some'' insight into what has persuaded a voter, if only the bare minimum. "Per all" is distinct at least from "per proposal", suggesting another voter has persuaded them where the original proposal did not by itself. A blank vote would not provide even that distinction.
#{{User|Mister Wu}} Asking for even a minimal input from the user as to why they are voting is fundamental, it tells us what were the compelling points that led to a choice or the other. It can also aid the voters in clarifying to themselves what they're agreeing with. Also worth noting that the new editors simply can't know that blank means "per all", even if we put it at the beginning of this page, because new editors simply don't know the internal organization of the wiki. Blank votes would inevitably be used inappropriately, and not in bad faith.
#{{user|DesaMatt}} Per all and per everyone and per everything. Per.
 
====Blank Comments====
I don't think banning "per all" or "per proposal" is feasible nor recommended. People literally sometimes have nothing else to add; they agree with the points being made, so they cast a vote. They don't need to waste keystrokes reiterating points. My proposal is aiming to just streamline that thought process and also save them some keystrokes. {{User:Mario/sig}} 20:34, December 17, 2024 (EST)
:I think every sort of vote (on every level, on every medium) should be written-in regardless of whether something has been said already or not; it demonstrates the level of understanding and investment for the issue at hand, which in my opinion should be prerequisite to voting on any issue. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 20:53, December 17, 2024 (EST)
::There is no way to actually determine this: we are not going to test voters or commenters their understanding of the subject. Someone can read all of the arguments and still just vote for a side because there's no need to reiterate a position that they already agree with. {{User:Ray Trace/sig}} 20:55, December 17, 2024 (EST)
:::My personal belief is that "test[ing] voters or commenters their understanding of the subject" is exactly what should be done to avoid votes cast in misunderstanding or outright bandwagoning. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 23:06, December 17, 2024 (EST)
::::My personal view is that a change like the one you are suggesting potentially increases the  odds of inexperienced or new users feeling too intimidated to participate because they feel like they do not have well articulated stances, which would be terrible. I think concerns about "bandwagoning" are overstated. However, more pressingly, this proposal is not even about this concept and it is not even one of the voting options, so I recommend saving this idea for another day. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 23:32, December 17, 2024 (EST)
:{{@|Mario}} I agree. Banning people from saying that in proposals is restricting others from exercising their right to cast a vote in a system that was designed for user input of any time. I'd strongly oppose any measure to ban "per" statements in proposals. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 00:11, December 18, 2024 (EST)
 
Technetium: I understand, but blank votes are a fairly common practice in other wikis, and it's clearly understood that the user is supporting the proposal in general. {{User:Mario/sig}} 20:36, December 17, 2024 (EST)
:Fair point, I didn't know that. Not changing my vote just yet, but I'll keep this in mind as the proposal continues. [[User:Technetium|Technetium]] ([[User talk:Technetium|talk]]) 20:48, December 17, 2024 (EST)
:There's a lot of variation in how other wikis do it. WiKirby, for example, doesn't even allow "per" votes last I checked. {{User:Hewer/sig}} 04:13, December 18, 2024 (EST)
 
I'm not really much of a voter, but I'm of the opinion "it's the principle of the matter". Requiring ''a'' written opinion, of any kind, at least encourages a consideration of the topic. [[User:Salmancer|Salmancer]] ([[User talk:Salmancer|talk]]) 21:35, December 19, 2024 (EST)
 
===Stop integrating templates under the names of planets and areas in the ''Super Mario Galaxy'' games===
{{early notice|December 25}}
The aims of this proposal is to repeal [[MarioWiki:Proposals/Archive/69#Decide how to handle conjectural sections about Super Mario Galaxy planets/areas|this one]] that passed earlier this year. I will reiterate my position here:
<blockquote>The planetary bodies in galaxies do not just "lack" publicly accessible names - they are straight up not supposed to have names. The Shogakukan guidebook for ''Mario Galaxy'' does not give planets name. The game does not give planets name. The instruction booklet does not give planets name. The only "source" that applies discrete names for planets are from the developers and we have no reason to think these were intended to be the planets. These galaxy articles are generally a bit outdated, and I think the mistake in the first place was suggesting that some of the planets have real names "except where otherwise noted." They largely do not. I think it would would healthier to recognize that they are just different sections of a greater whole, much like areas in courses for the earlier 3D games, and apply titles accordingly.</blockquote>
To elaborate on my perspective, I think using dev data to provide names for these planets is completely fine, and I understand the desire to do so. Citing the Prima Games guidebooks for potential names for these areas is fine. That is not what this proposal is about. Rather, integrating the ''templates'' themselves - be it for conjectural or dev data-derived names - underneath the individual headers for each planet, in my view, looks very poor, as you can see here for [[Yoshi Star Galaxy#Planets|Yoshi Star Galaxy]] and [[Honeyhive Galaxy#Planets/Areas|Honeyhive Galaxy]]. They are detractingly eye-catching and break these articles without substantive benefit. I think having a nonintrusive note at the top or bottom of these articles - as was the case before the proposal I link to above passed - is perfectly sufficient and healthier for these articles.
 
I provide two options:
#'''Support: Do not put conjectural and dev-data name templates beneath the names of individual planets and areas in  the ''Super Mario Galaxy'' games''': This is a full repeal of the proposal I link to above.
#'''Oppose: Change nothing'''
 
'''Proposer''': {{User|Nintendo101}}<br>
'''Deadline''': January 1, 2025, 23:59 GMT
 
====Support: Do not put templates underneath the name's of planets and areas====
#{{User|Nintendo101}} Per proposal.
#{{User|1468z}} Per proposal.
#{{User|Waluigi Time}} The previous solution looked a lot nicer. I also agree with Nintendo101 that we should rethink how we approach planet names in general. They don't necessarily "need" names any more than specific portions of levels in other games do.
#{{User|Jdtendo}} I still don't agree with the "planets are not supposed to have names" argument, but I do agree that having templates beneath every section heading is excessive.
#{{User|Camwoodstock}} Per all, especially Waluigi time. The overall assumption that the planets have names unless otherwise stated feels like the consequence of a decision made very, very early on into the wiki, that's just kind of gone unquestioned or unnoticed until very recently. This won't stop that particular case of WikiJank™ completely, but it's a step in the right direction.
#{{User|Sparks}} Per all.
#{{User|EvieMaybe}} if all the names are unofficial, then we only need to say it once. if there's an official name, we can just say "all names are unofficial unless specified" and specify in the one planet that has a name (is there any planets with names even???). having the template on each individual section is both ugly and inefficient
#{{User|Mario}} Yeah, the setup before this was satisfactory. Per Evie, but I also agree with Waluigi Time that we probably don't need to require naming these parts of the level either.
#{{User|Ray Trace}} I always thought assigning these objects meant to be part of the environment conjectural templates has always struck me as odd and I don't know why only Super Mario Galaxy gets singled out out of all games. We don't name the rooms the Mario Party minigames take place in.
#{{User|Tails777}} I was sincerely confused when I saw the templates put back on the various galaxy articles and questioned "Why? It was better beforehand." Per all.
#{{User|Hooded Pitohui}} In the longer-term, WT and Nintendo101 bring up points which ought to be considered. In the shorter term, this would be a beneficial first step to de-cluttering these sections for better readability.
#{{User|Ninja Squid}} Per all.
#{{User|Technetium}} Per Nintendo101, Waluigi Time, and Porple's comment below.
#{{User|MCD}} Per N101, WT and Porple below. I also agree our attitude on what counts as "conjectural" when it comes to naming planets needs a rethink, i.e. it's not conjecture to call the planet the player starts on the "starting planet" because that's just a factual description. (Also, why does [[Starting Planet]] just redirect to a random galaxy? lol)
 
====Oppose: Keep the templates====
#{{User|Ahemtoday}} I'm opposing this proposal ''as currently slated to be implemented'' — as in, just removing [[Template:Conjecture]] and [[Template:Dev data]] from these sections and leaving it at that. These need to be marked, and I don't feel that an "unless otherwise noted" disclaimer is an elegant way to do that. However. There is a way of accomplishing this that I ''would'' be amenable to: replacing those templates with [[Template:Conjectural]] or a new dev data equivalent to it. This is the same way our glitch pages do it, for exactly the same reason you want to get rid of these templates on the galaxy pages. I think it makes perfect sense to use this convention here as well to solve this problem.
 
====Comments on the planet template proposal====
I agree that we don't need the repeated templates, and the whole naming situation of the planets is a bit odd. Rather than giving the planets capitalized "names" (e.g. "Starting Planet") and noting them as conjectural, they should just be described in sentence case, at which point it should be somewhat obvious that it's a description and not a "name". For example, section heading "Starting planet" and text "The starting planet has..." You could do a single {{tem|conjecture|2=subsections=yes}} under the "Planets" heading if you really wanted to, but I think if we removed all the inappropriate capitalization then even that wouldn't be necessary. --{{User:Porplemontage/sig}} 20:11, December 19, 2024 (EST)
 
===Set Vector-2010 to the default wiki skin===
This proposal is about setting the 2010 [[mw:Skin:Vector|Vector]] as the default wiki skin ([https://web.archive.org/web/20160207064154/https://upload.wikimedia.org/wikipedia/foundation/4/44/Logo_new-vector_screenshot.png screenshot here]) for desktop users, with the focus being on people who are new to wikis in particular, while obviously keeping the existing MonoBook skin as an option. What made me think to create this proposal is when I made a [[Talk:Main Page]] proposal about the to-do list tasks and how they are more accessible than clicking the "Wiki maintenance" on the sidebar, I had to uncomfortably squint to find "Wiki maintenance" on the wiki sidebar. But Vector-2010 has the sidebar links slightly larger and a bit more spaced out. With the existing interface, there could be some who may struggle to find options listed on the sidebar.
 
While we're clearly different from Wikipedia (that's why I'm not Vector-2022, since it'd be too much of a departure and likely uncomfortable for several), I do want to refer to [http://web.archive.org/web/20180213165624/https://blog.wikimedia.org/2010/05/13/a-new-look-for-wikipedia/ this page], which summarizes why Wikipedia transitioned to it. Though it is vague, they cite accessibility as the reason, which I think this wiki has been taking steps toward doing.
 
I'll cite my reasons for preferring Vector and applying this to possible people who are visiting a wiki for the first time. The text is larger, which is especially important for larger screen monitors, some of the lesser used tabs are collapsible on the sidebar, summarizing the most commonly used options, and the user links at the top right are also more noticeable and less close to the body of the article where the content is read.
 
Though it could take time getting used to the Edit button being on the right (not to mention the search button), the button is at least larger, making it more usable on even lower quality screen monitors, and I like how it's separate from the Page and discussion options, meaning that options that involve viewing articles are on the left while options that involve editing or changing the page in some form are on the right.
 
If this proposal passes and others don't like the change, they can always return to the MonoBook option in their [[Special:Preferences#mw-prefsection-rendering|preferences]].
 
'''Proposer''': {{User|Super Mario RPG}}<br>
'''Deadline''': January 1, 2025, 23:59 GMT


====Support====
====Support====
#{{User|Mario}} It's a pain in the ass to visit these articles I mentioned. Every little bit of trimming will be highly appreciated, so moving this information to another article will be nice.
#{{User|Super Mario RPG}} Per.
#{{User|Pinkie Pie}} In 2006, all the page were short like a daisy. Now, it a garbage dump today. We should move the profiles to another page. Reader could get tired of reading long articles. I said we go back to 2006. Per all.
#{{User|Walkazo}} - YES! I've wanted to see this happen for ''years'', but was always too lazy to to do more than mention it [http://www.mariowiki.com/index.php?title=Talk%3ABowser&diff=1596307&oldid=1596290 every now and then]. As well as shortening the length of the page as a whole, it'll also halve the amount of entries in the Table of Contents for these big pages, making navigation easier (plus, then there won't be so many headers sharing names and potentially complicating section-linking). The articles will also look better without the messy lists dragging along after the prose content.
#{{User|GBAToad}} I strongly support this. Per Mario and Walkazo.
#{{User|Tails777}} Yes, just yes. Maybe this can also help towards featuring these kinds of articles (maybe). Per all.
#{{User|Yoshi876}} Per all.
#{{user|driftmaster130}} Great idea for improving organization, per all.
#{{User|Robecuba}} Per Mario and Pinkie
#{{User|Mario7}} Per all. I think that the "big" pages need to be cleaned up a lot.
#{{User|Randombob-omb4761}} Per Pinkie Pie
#{{User|Icemario}} This should at least lessen the constipation devices go through when they try loading one of these pages. Per Mario and Walkazo.
#{{User|Baby Luigi}} Per all
#{{User|Iggy Koopa Jr}} It hurts trying to read the Mario page.
#{{user|Green 6017 King Of The Slowpoke}} Per all.
#{{User|Jazama}} Per all
#{{User|Megadardery}} Per all, it is making the page Bowser on the top of the [[Special:LongPages|Long Pages]] list. It makes the page more organized.
#{{User|Lord Grammaticus}} Definite per all.
#{{User|Mario4Ever}} Per all.
#{{User|Coooool123}} Per all.


====Oppose====
====Oppose====
#{{User|SeanWheeler}} - I have no problem loading these pages. And the profiles and statistics are ''shorter'' than the history. I don't think removing a small section would help your loading times.
#{{User|Camwoodstock}} Admittedly, this vote is largely a matter of preference--we just don't like Vector that much--but we can't think of any real reason to switch to Vector 2010 as the default over the current Monobook beyond the mentioned text spacing; while that is a nice boon, we personally find the weird gradient buttons for the various tabs up top a little grating looking, and we're a fan of the more compact design that Monobook provides--though, this is likely a byproduct of our personal preference for more neatly packed web design. And uh, the less said about the other two options (Vector 2022, and. Timeless. <s>Which is the most dated theme possible, namely to mid-2010s mobile web design.</s>), the better. If you like Vector 2010, that's great, and we're fine with that! Heck, if anyone likes Vector 2022 or Timeless, that's cool too, and more power to them! Variety is the spice of life, after all. But switching it to the default is something that should not be taken lightly, and the reasons for a switch in this proposal feel a little too loosey-goosey for us, we're sorry.
#{{User|DryBonesBandit}} Per Camwoodstock.
#{{User|Nintendo101}} I like how MonoBook looks a little more than Vector. It is what I am comfortable with. If it ain't broke, don't fix it.
#{{User|Drago}} Per Nintendo101. I actually prefer the smaller text of Monobook since you can see more of the page at once. I also want to point out that although logged-in users like us can change the skin in preferences, we'd still be forcing the change on logged-out users.
#{{User|Ahemtoday}} Per Drago.
#{{User|Technetium}} Per Nintendo101 and Drago. I just don't see any reason to make this change.
#{{User|Altendo}} I'm saying this as a Vector-2010 skin user, and I'll say that people have their preferences. I live Vector-2010 because that is how Wikipedia at least used to look before they switched to Vector (2022); On Wikipedia, Vector was renamed to Vector legacy (2010), while Vector 2022 is named Vector (2022). Although I do prefer Vector-2010, I know a lot of people that prefer Monobook, and even if not, this can be changed in the preferences. No need to change the default skin. I get that IPs can't change their appearance, but aside from that, users can, and what they see doesn't have to be default on the wiki. Everyone can change what they specifically see.


====Comments====
====Comments====
I think it would be a good idea to also say that ''all'' the official profiles and stats should go on the not-subpages - i.e. instead of having some of the RPG infoboxes in the History sections, etc. That way, everything would be in one place, and it would also make the History sections more uniform and less crowded (as they can get when they have multiple boxes in close proximity). One question, tho: what would the new pages be named? "List of profiles and statistics of X" would be consistent with [[MarioWiki:Subpages_Policy|other "subpages"]], and doesn't see, ''too'' wordy after the "official" bit's removed. But I dunno, maybe there's a better choice? - {{User|Walkazo}}
{{@|Camwoodstock}} That is true that it's a major change. It's based mainly upon impression from newcomers from them seeing a more prominent edit tab, slightly larger text size, and other minor details like tab names that are easier to read (including a collapsible feature for the lesser used tab). The skin change was based on old Wikipedia research at the time (like how WikiLove was a result of their research). I have no strong feelings whether this passes or not. Although it's vague, since there's no way to tell the statistics (and the wiki's already successful at the moment), I still have a feeling it could help some, but to each their own. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 18:32, December 18, 2024 (EST)
:I added some more provisions, thanks to your suggestions. Also, I think the "profiles and statistics" part can be shortened to just one word, but I'm not exactly sure what single word can replace that lengthy phrase. Maybe "List of data of this guy person" or simply "List of profiles of this guy person". {{User|Mario}}
:We feel like if anybody would be capable of providing any statistics on skin usage, it'd be Porple, but even then, we don't actually know if that's one of the things he tracks, and it feels a little silly to pester him over this of all things... ;p {{User:Camwoodstock/sig}} 18:55, December 18, 2024 (EST)
::SeanWheeler, if we don't move the stat to another page, the reader might rage quit on this wiki. {{User|Pinkie Pie}} 12:01, 2 February 2014 (EST)
 
:::That's extreme; the worst I'd do is refuse to click on those specific pages at all. {{User|Baby Luigi}}
I'm okay with opposition, but in case of misunderstanding, this proposal isn't about personal preferences so much as what I believe to be a more ergonomic interface to a wider audience. I know we're not Wikipedia, but there's also the consideration that they've used the Vector skin longer than they had for MonoBook. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 13:45, December 19, 2024 (EST)
:I like "List of {character} profiles and statistics". - {{User|Porplemontage}}
:If it's what "you believe", then it ultimately (and probably unavoidably) is about personal preferences. Anyway, another consideration is the fact that people often prefer what they're used to. I feel like how long this wiki has used its skin is more relevant than how long Wikipedia has. {{User:Hewer/sig}} 16:39, December 19, 2024 (EST)
SeanWheeler, just compare the loading time of Waluigi to Bowser. There is a noticeable difference. In every computer I've used, Bowser takes a painfully longer time to load. Also, you should be more considerate about those with weaker computers than yours. Just because YOU don't have a problem doesn't mean EVERYONE won't. I've also mentioned explicitly that the action will not make the page load a million times faster, but trimming reasonably will improve loading times nevertheless. {{User|Mario}}
::{{@|Hewer}} I suppose I'm overthinking the ergonomic interface. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 15:19, December 20, 2024 (EST)
:I think the reason why he said it's fine, is because he has a high-performance PC that load pages faster. Check other computers with low-performance SeanWheeler, the pages take almost 1 minute to load. {{User|Pinkie Pie}} 18:38, 4 February 2014 (EST)
::I'm using a computer with an i7 processor and the Mario page still makes my browser hang for 10 seconds. You need a REALLY high-performance PC that doesn't make a difference. SeanWheeler's reasoning is weak: "I don't have problems and it won't reduce loading time drastically, so I will oppose." {{User|Mario}}
:::SeanWheeler might have a REALLY high-performance PC. Also, I'm with Mario: SeanWheeler's oppose is weak. {{User|Pinkie Pie}} 15:52, 5 February 2014 (EST)
::::It's a quad-core CPU with 1.7 gH I believe. It's not gaming-quality (doesn't run Dolphin Emulator GCN games such as Mario Party at full speed), but it's still decent. {{User|Baby Luigi}}
:::::Loading a page shouldn't take a $10,000 premium-performance shiny spankin' new computer for goodness sake. {{User|Mario}}
Also, even though the long page load faster, scrolling down is a pain to look at. {{User|Pinkie Pie}} 16:22, 5 February 2014 (EST)


==Miscellaneous==
==Miscellaneous==
===Create a Page for the Toadette Species===
===Use official alt text as a source===
{{early notice|December 24}}
What I refer to here as "{{wp|alt attribute|alt text}}" is text that is either:
*shown in place of a file, such as an image, when the file doesn't load;
*shown as a small note when you hover your mouse on an image on PC. See for yourself with this pic: [[File:Artwork - SUPER STAR.svg|30px|This is a Mario Star.]]
 
To quote the Wiki article I linked above, alt text "is used to increase accessibility and user friendliness, including for blind internet users who rely on special software for web browsing."
 
Nintendo's web content makes hefty use of this feature, particularly in [[Cat Transformation Center#Decorations|activities]] [[Holiday Create-a-Card (2024)#Decorations|on the]] [[Paper Mario: The Origami King Collage Maker#Decorations|Play Nintendo]] [[Nintendo Online Calendar Creator#Decorations 3|site]], where it is employed for decorative stickers users can select and manipulate. Alt text is certainly a unique means to convey information that, currently, is not treated in any the entries laid out in the wiki's "[[MarioWiki:Naming#Acceptable sources for naming|acceptable sources for naming]]", including entry 2 concerning web material, and hasn't been discussed to my knowledge. Since alt text can bear information of its own, as explained below, it might be time we decided if this quaint thing should be supported in the policy.
 
The following aspects should be kept in mind as a decision is made on this topic:
*tempting as it may be, alt text cannot be construed as internal material in the way filenames are. A filename, whether pertaining to a file in a video game or [[MarioWiki:Proposals/Archive/63#Reconsider_Nintendo's_website_filenames_being_used_as_a_source|a file on a web page]], serves a utilitarian purpose that is, above all, an organizational tool meant to aid the developers of said game or website. Contrarily, the very purpose of alt text is to be seen by the end user (that is, the regular Joe or Jane the product is being shown to) under special circumstances.
*on the other hand, alt text may display some level of unprofessionality or unfamiliarity with the source material on the part of its author--that is to say, it can lend to some pretty weird information about a given subject. The few examples I've come across are an [https://web.archive.org/web/20221204022632/https://play.nintendo.com/activities/play/nintendo-holiday-ornament-creator/ ornament resembling a mushroom item being referred to as a "Toad ornament"] <small>(play.nintendo.com via archive.org)</small>, [[Koopa Paratroopa]] [https://web.archive.org/web/20210810004641/https://play.nintendo.com/activities/play/nintendo-online-calendar-creator being called a "Koopa Flying Trooper"] <small>(play.nintendo.com via archive.org)</small>, and [[Meowser]] [https://play.nintendo.com/activities/play/bowsers-fury-cat-photo-booth/ being called "Cat Bowser"] <small>(play.nintendo.com)</small>. I'd like to stress that '''this is far from the norm''', as evident in those links--Mario is called "Mario", Goomba is "Goomba" etc., heck, some lesser known characters like {{iw|nookipedia|Lottie}}, {{iw|nookipedia|Wardell}}, and {{iw|nookipedia|Niko}} from ''Animal Crossing'' are correctly identified in that Ornament Creator activity--, but I believe it's fair of me to show you a comprehensive image of the situation.


It's been shown within games such as [[Mario & Luigi: Bowser's Inside Story]] and [[Super Mario Galaxy]] that there are multiple female toads. These should be appropriately called Toadettes. (Kind of like Smurfs and Smurfettes. It's a stupid comparison, I know...) Therefore, I propose that, since there is a page for the Toad species, there should likewise be one for the Toadette species.
Most importantly, beyond the typical "they offer unique names and spellings" claptrap, I've noticed that citing such material is genuinely practical in select situations. The one recent example that comes to mind is that the alt text of some Play Nintendo activities helped me delineate [[Gallery:Super Star#Notes|a few otherwise non-descript stars shown at Gallery:Super Star]]. The [[Super Star]] item, the one used in games to make player characters invincible, has in the past shared 2D graphics with the [[Power Star]] collectable McGuffins from 3D titles, so when identifying a given {{file link|MH Oct 4.svg|Star graphic}} with zero context to its nature, all bets are off; rather than resort to speculation and potentially erroneously place a [[Gallery:Miscellaneous stars|non-descript star graphic]] in the Super Star's gallery (as previously done), one can look up the graphic's alt text on Nintendo's website and use that as a crutch, if there's absolutely nothing else.


Now, some may argue that there isn't enough information for that, but I do think that there will be plenty of facts to make sure that this article is not a stub.
I propose three options for handling material presented in this manner.
#'''Cite alt text the same way media, including other web content, is typically cited.''' This means that if a Goomba's alt text is "Toothy Mushroom" in a context where most or every other element from the Mario series is given their usual names, then "Toothy Mushroom" is treated as a valid alternate name for the Goomba, shown on the Goomba article, and referenced from the aforementioned alt text. As argued above, alt text is meant to be seen by the end user, placing it somewhere above level 6 (concerning internal game filenames) of the current [[MarioWiki:Naming#Acceptable sources for naming|source priority policy]] under this option.
##Some exceptions can be made in this scenario. If, for instance, wiki users deem that a discrete piece of web content handles alt text in an overwhelmingly unprofessional manner, they may choose not to cite it. As a concrete example, the [https://web.archive.org/web/20241215120155/https://play.nintendo.com/activities/play/nintendo-online-calendar-creator/ 2024 Calendar Creator] activity at Play Nintendo reuses the exact same alt text from its 2023 iteration for its decorative stickers, even though said stickers changed. According to that activity, [[Cheep Cheep]]s are also called "[[Monty Mole]]s" and [[Pokey]]s are also called "[[Chain Chomp]]s". This obviously represents some level of carelessness that shouldn't be reflected on the wiki even if the content is technically official. However, it's also the exception, not the rule.
#'''Cite alt text only for redirects and/or when no other source is available for a given thing.''' This means that "Koopa Flying Trooper" and "Cat Bowser" will be removed from the [[Koopa Paratroopa]] and [[Meowser]] pages respectively, but will remain as redirects to these pages. The explanations at [[Gallery:Super Star#Notes]] and [[Gallery:Miscellaneous mushrooms#Notes]] will remain as well, because alt text is currently the only means to identify certain graphics on those pages as being a particular type of star or mushroom.
#'''Do not cite alt text in any of the ways described above.'''


However, I'm also open to the idea, should the community not want to create an entire page, that we add additional information under the [[Toad (species)]] segment about the female toad species, of which there is none. There's also the possibility to add this under [[Toadette]]. Either one works for me.
'''Note:''' The articles concerning the Play Nintendo activities mentioned above ([[Cat Transformation Center]], [[Paper Mario: The Origami King Collage Maker]] etc.) will continue to list the alt text of each graphic as captions regardless of the proposal's outcome. This provides quick cross-referencing to someone who really wants to know how a decoration is called in those activities.


'''Proposer''': {{User|Coooool123}}<br>
'''Proposer''': {{User|Koopa con Carne}}<br>
'''Deadline''': February 13, 2014, 23:59 GMT
'''Deadline''': December 31, 2024, 23:59 GMT


====Create a New Page for the Toadette Species====
====Support: cite alt text for everything, including unique names====
#{{User|Coooool123}} Per proposal
#{{User|Koopa con Carne}} <!--This image contains alt text that shows my support of the proposal. It is not just a random pic.-->[[File:Go Mario.png|40px|Per proposal!]]
#{{User|Hewer}} I'd think alt text would be covered under "web content" in the naming policy. There's no reason for it not to be, given that it's official text, and is more intended to be seen by the end user than image filenames, which [[MarioWiki:Proposals/Archive/63#Reconsider_Nintendo's_website_filenames_being_used_as_a_source|we already agreed are fine]]. If something's obviously a mistake, we can say that without discrediting the whole source, like we already do with other sources (e.g. the [[Cleft]] article acknowledging the "Moon Cleft" name from Super Paper Mario despite deeming it "mistaken").
#{{User|Camwoodstock}} <!--Same bit as KCC's vote, don't remove it please.-->[[File:WL4-Smile.png|The future is now, old man! We're in an era of Bluesky and screen reader compatibility! Okay, jokes aside, we're a little surprised that alt text hasn't been accounted for already, given it has been around the internet for a very, very long time. Still, better late than never, we suppose. Per proposal, and Hewer especially!]]
#{{User|EvieMaybe}} per Hewer
#{{User|Altendo}} Per all.
#{{User|Nintendo101}} [[File:Yoshijumpjoy.gif|Per Hewer.]]
#{{User|Super Mario RPG}} Per everyone.
#{{User|FanOfYoshi}} [[File:Spear Guy.gif]]
#{{User|OmegaRuby}} <!--Same bit as the others with alt texts!!--> [[File:Poisonl.gif|It's kind of surprising how this hasn't been implemented nor standard in some way yet - there's no reason that it isn't! I'm all for increased accessibility and the use of accessibility features such as alt text. Per all.]]
#{{User|Technetium}} [[File:HM Proto Toad.gif|Per all.]]
#{{User|Pseudo}} [[File:ToadetteYakumanDS.gif|50px|Per all.]]
#{{User|Axii}} [[File:MKSC Luigi Blimp.png|85px|Per proposal.png]]


====Create a section in the Toad Species for the female toad counterpart species====
====Support: only cite alt text for redirects and/or if there is no other source available====


====Create a section under Toadette for the female toad counterpart species====
====Oppose: do not cite alt text at all====


====Don't create anything====
====Comments (alt text proposal)====
RE the "Toad Ornament": I think it's worth mentioning that calling some type of mushroom item a "Toad" is [[1-Up Mushroom#Hotel Mario|not unheard of]] in official works. But ok, it's less likely the typist of that Play Nintendo activity was thinking of Hotel Mario, and more likely they just confused Super Mushrooms with Toads due to their similar appearances. {{User:Koopa con Carne/Sig}} 16:45, December 17, 2024 (EST)


====Comments====
[[File:SMBS Icicle Sharp X1.png|frame|left]]
@OmegaRuby: The proposal itself is about allowing alt text to be considered a valid source, not broadening usage of alt text as a whole. ''That being said'', on that note, I do wonder if we could perhaps do just that (likely as part of another proposal), mostly in the context of sprites--such as this example on the left from the [[Icicle]] article. A usual caption would absolutely not fit on this, but alt text could help provide something for a screenreader to read out. The main issue is that, to my knowledge, the "frame" parameter inherently means the alt text ''is'' the caption, which could cause issues if we need the actual, well, frame... {{User:Camwoodstock/sig}} 12:43, December 18, 2024 (EST)

Latest revision as of 00:51, December 23, 2024

Image used as a banner for the Proposals page
Current time:
Monday, December 23rd, 13:33 GMT
Proposals can be new features, the removal of previously-added features that have tired out, or new policies that must be approved via consensus before any action is taken.
  • Voting periods last for two weeks, but can close early or be extended (see below).
  • Any autoconfirmed user can support or oppose, but must have a strong reason for doing so.
  • All proposals must be approved by a majority of voters, including proposals with more than two options.
  • For past proposals, see the proposal archive and the talk page proposal archive.

If you would like to get feedback on an idea before formally proposing it here, you may do so on the proposals talk. For talk page proposals, you can discuss the changes on the talk page itself before creating the TPP there.

How to

If someone has an idea about improving the wiki or managing its community, but feel that they need community approval before acting upon that idea, they may make a proposal about it. They must have a strong argument supporting their idea and be willing to discuss it in detail with other users, who will then vote on whether or not they think the idea should be implemented. Proposals should include links to all relevant pages and writing guidelines. Proposals must include a link to the draft page. Any pages that would be largely affected by the proposal should be marked with {{proposal notice}}.

Rules

  1. Only autoconfirmed users may create or vote on proposals. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
  2. Proposals conclude at the end of the day (23:59) two weeks after voting starts (all times GMT).
    • For example, if a proposal is added at any time on Monday, August 1, 2011, the voting starts immediately and the deadline is two weeks later on Monday, August 15, at 23:59 GMT.
  3. Users may vote for more than one option, but they may not vote for every option available.
  4. Every vote should have a strong, sensible reason accompanying it. Agreeing with a previously mentioned reason given by another user is acceptable (including "per" votes), but tangential comments, heavy sarcasm, and other misleading or irrelevant quips are just as invalid as providing no reason at all.
  5. Users who feel that certain votes were cast in bad faith or which truly have no merit can address the votes in the comments section. Users can ask a voter to clarify their position, point out mistakes or flaws in their arguments, or call for the outright removal of the vote if it lacks sufficient reasoning. Users may not remove or alter the content of anyone else's votes. Voters can remove or rewrite their own vote(s) at any time, but the final decision to remove another user's vote lies solely with the wiki staff.
    • Users can also use the comments section to bring up any concerns or mistakes in regards to the proposal itself. In such cases, it's important the proposer addresses any concerns raised as soon as possible. Even if the supporting side might be winning by a wide margin, that should be no reason for such questions to be left unanswered. They may point out any missing details that might have been overlooked by the proposer, so it's a good idea as the proposer to check them frequently to achieve the most accurate outcome possible.
  6. If a user makes a vote and is subsequently blocked for any amount of time, their vote is removed. However, if the block ends before the proposal ends, then the user in question holds the right to re-cast their vote. If a proposer is blocked, their vote is removed and "(blocked)" is added next to their name in the "Proposer:" line of the proposal, which runs until its deadline as normal. If the proposal passes, it falls to the supporters of the idea to enact any changes in a timely manner.
  7. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
  8. If one week before a proposal's initial deadline, the first place option is ahead of the second place option by eight or more votes and the first place option has at least 80% approval, then the proposal concludes early. Wiki staff may tag a proposal with "Do not close early" at any time to prevent an early close, if needed.
    • Tag the proposal with {{early notice}} if it is on track for an early close. Use {{proposal check|early=yes}} to perform the check.
  9. Any proposal where none of the options have at least four votes will be extended for another week. If after three extensions, no options have at least four votes, the proposal will be listed as "NO QUORUM." The original proposer then has the option to relist said proposal to generate more discussion.
  10. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  11. If a proposal reaches its deadline and the first place option is ahead of the second place option by three or more votes, then the first place option must have over 50% approval to win. If the margin is only one or two votes, then the first place option must have at least 60% approval to win. If the required approval threshold is not met, then the proposal is extended for another week.
    • Use {{proposal check}} to automate this calculation; see the template page for usage instructions and examples.
  12. Proposals can be extended a maximum of three times. If a consensus has not been reached by the fourth deadline, then the proposal fails and cannot be re-proposed until at least four weeks after the last deadline.
  13. All proposals are archived. The original proposer must take action accordingly if the outcome of the proposal dictates it. If it requires the help of an administrator, the proposer can ask for that help.
  14. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
  15. If the wiki staff deem a proposal unnecessary or potentially detrimental to the upkeep of the Super Mario Wiki, they have the right to cancel it at any time.
  16. Proposals can only be rewritten or canceled by their proposer within the first four days of their creation. However, proposers can request that their proposal be canceled by a staff member at any time, provided they have a valid reason for it. Please note that canceled proposals must also be archived.
  17. Unless there is major disagreement about whether certain content should be included, there should not be proposals about creating, expanding, rewriting, or otherwise fixing up pages. To organize efforts about improving articles on neglected or completely missing subjects, try setting up a collaboration thread on the forums.
  18. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
  19. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  20. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal formatting

Below is an example of what your proposal must look like. If you are unsure how to set up this format, simply copy the following and paste it into the fitting section. When updating the bracketed variables with actual information, be sure to replace the whole variable including the square brackets, so "[insert info here]" becomes "This is the inserted information" and not "[This is the inserted information]". Proposals presenting multiple alternative courses of action can have more than two voting options, but the objective(s) of each voting option must be clearly defined. Such options should also be kept to a minimum, and if something comes up in the comments, the proposal can be amended as necessary. 

===[insert a title for your proposal here]===
[describe what issue this proposal is about and what changes you think should be made to improve how the wiki handles that issue]

'''Proposer''': {{User|{{subst:REVISIONUSER}}}}<br>
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

====[option title (e.g. Support, Option 1)]: [brief summary of option]====
#{{User|{{subst:REVISIONUSER}}}} [make a statement indicating that you support your proposal]

====[option title (e.g. Oppose, Option 2)]: [brief summary of option]====

====Comments ([brief proposal title])====

Autoconfirmed users will now be able to vote on your proposal. Remember that you can vote on your own proposal just like the others.

To vote for an option, just insert #{{User|[your username here]}} at the bottom of the section of your choice. Just don't forget to add a valid reason for your vote behind that tag if you are voting on another user's proposal. If you are voting on your own proposal, you can simply say "Per proposal".

Talk page proposals

Proposals concerning a single page or a limited group of pages are held on the most relevant talk page regarding the matter. All of the above proposal rules also apply to talk page proposals. Place {{TPP}} under the section's header, and once the proposal is over, replace the template with {{settled TPP}}. Proposals dealing with a large amount of splits, merges, or deletions across the wiki should still be held on this page.

All active talk page proposals must be listed below in chronological order (new proposals go at the bottom) using {{TPP discuss}}. Include a brief description of the proposal while also mentioning any pages affected by it, a link to the talk page housing the discussion, and the deadline. If the proposal involves a page that is not yet made, use {{fake link}} to communicate its title in the description. Linking to pages not directly involved in the talk page proposal is not recommended, as it clutters the list with unnecessary links.

List of ongoing talk page proposals

Unimplemented proposals

Proposals

Break alphabetical order in enemy lists to list enemy variants below their base form, EvieMaybe (ended May 21, 2024)
Standardize sectioning for Super Mario series game articles, Nintendo101 (ended July 3, 2024)
^ NOTE: Not yet integrated for the Super Mario Maker titles, Super Mario Run, and Super Mario Bros. Wonder.
Create new sections for gallery pages to cover "unused/pre-release/prototype/etc." graphics separate from the ones that appear in the finalized games, Doc von Schmeltwick (ended September 2, 2024)
Add film and television ratings to Template:Ratings, TheUndescribableGhost (ended October 1, 2024)
Use the classic and classic-link templates when discussing classic courses in Mario Kart Tour, YoYo (ended October 2, 2024)
Clarify coverage of the Super Smash Bros. series, Doc von Schmeltwick (ended October 17, 2024)
Remove all subpage and redirect links from all navigational templates, JanMisali (ended October 31, 2024)
Prioritize MESEN/NEStopia palette for NES sprites and screenshots, Doc von Schmeltwick (ended November 3, 2024)
Stop considering reused voice clips as references (usually), Waluigi Time (ended November 8, 2024)
Allow English names from closed captions, Koopa con Carne (ended November 12, 2024)
^ NOTE: A number of names coming from closed captions are listed here.
Split off the Mario Kart Tour template(s), MightyMario (ended November 24, 2024)
Split major RPG appearances of recurring locations, EvieMaybe (ended December 16, 2024)

Talk page proposals

Split all the clothing, Doc von Schmeltwick (ended September 12, 2021)
Split machine parts, Robo-Rabbit, and flag from Super Duel Mode, Doc von Schmeltwick (ended September 30, 2022)
Make bestiary list pages for the Minion Quest and Bowser Jr.'s Journey modes, Doc von Schmeltwick (ended January 11, 2024)
Allow separate articles for Diddy Kong Pilot (2003)'s subjects, Doc von Schmeltwick (ended August 3, 2024)
Create articles for specified special buildings in Super Mario Run, Salmancer (ended November 15, 2024)
Expand and rename List of characters by game to List of characters by first appearance, Hewer (ended November 20, 2024)
Determine how to handle the Tattle Log images from Paper Mario: The Thousand-Year Door (Nintendo Switch), Technetium (ended November 30, 2024)
Merge False Character and Fighting Polygon/Wireframe/Alloy/Mii Teams into List of Super Smash Bros. series bosses, Doc von Schmeltwick (ended December 2, 2024)

Writing guidelines

None at the moment.

New features

Create a template to direct the user to a game section on the corresponding List of profiles and statistics page

This proposal aims to create a template that directs people to a game section on a Profiles and statistics list page, saving the user the step of having to scroll for it themselves. The reason why I'm proposing this is because as more Super Mario games are released, it becomes harder to comfortably find what you're searching for in the corresponding List of profiles and statistics page, especially for Mario, Bowser, and many other recurring subjects.

Another reason I think this would be valid is because of the fact that listing statistics in prose (e.g. 2/10 or 2 out of 10) looks off, especially if that can already be seen in the corresponding statistics box; in that case, the prose could change from "2/10" to something more vague like "very low stat", which isn't typically worded as such in the statistics box.

For example, let's say for Luigi in his appearance in Mario Sports Superstars, there could be a disclaimer either below the section heading or in a box to the side (we can decide the specifics when the proposal passes) that informs the reader that there's corresponding section that shows his profiles/statistics corresponding. Like such:

For profiles and statistics of Luigi in Mario Sports Superstars, see here.

The above message is not necessarily the final result (just a given example), but the disclaimer would definitely point the user to the appropriate game section on the profiles and statistics list page, should this pass.

Proposer: Super Mario RPG (talk)
Deadline: January 1, 2025, 23:59 GMT

Support

  1. Super Mario RPG (talk) Per.
  2. Hewer (talk) I don't really see a need to deliberately make prose less specific, but otherwise I like this idea, per proposal.

Oppose

Comments

@Hewer I don't think this would necessarily eliminate cases in which statistics are in prose, but it may be redundant if there's the link to conveniently access the statistics or profiles. Super Mario RPG (talk) 15:15, December 18, 2024 (EST)

Add an abbreviation template to type out full game titles

This proposal is about creating a template that it makes it easier to type out full game titles. Although The Legend of Zelda games generally have longer titles (and Zelda Wiki even has templates for some of their shorter titled games, like Hyrule Warriors, here), there have still been cases in which some game titles are uncomfortably long, such as Donkey Kong Country 3: Dixie Kong's Double Trouble! or Super Mario RPG: Legend of the Seven Stars, and while it may seem like not a big deal to some, it would be a small quality-of-life improvement if we could have a template where we input the abbreviation, and the output becomes the game title.

For example, {{a|M&LSS}} would result in Mario & Luigi: Superstar Saga (complete with italics formatting). Meanwhile, {{a|M&LSS|l}} to link to the game, outputting Mario & Luigi: Superstar Saga, although depending on who creates the template, it could be vice versa, like it links by default and {{a|M&LSS|n}} would prevent a link.

Since Super Mario has several releases, it may get difficult maintaining with all the abbreviations, and there have been cases where two games have shared the same abbreviation. (e.g. SMS for both Mario Sunshine and Mario Strikers). In that case, either {{a|SMS|2002}} (with the year of release) or a custom abbreviation (e.g. {{a|SMShine}}) would be needed (personally I'd prefer the latter).

Consider we already have similar templates for Princess Peach and Princess Daisy (i.e. {{Peach}} and {{Daisy}}), and both of their full titles (with "Princess" included) is a lot shorter than the two game titles in the first paragraph.

Proposer: Super Mario RPG (talk)
Deadline: January 1, 2025, 23:59 GMT

Support

  1. Super Mario RPG (talk) Per.
  2. Camwoodstock (talk) We don't see the harm in this, even if it would admittedly be fairly niche. The only real complaint we have is the lack of an additional parameter for changing the displayed text, so if we need to say something like "in the remake", we have to write that out the old-fashioned way.
  3. EvieMaybe (talk) might make some link-heavy pages lighter!
  4. Salmancer (talk) Words cannot express the relief that my fingers would feel if they never have to type out "Mario & Luigi: Bowser's Inside Story + Bowser Jr.'s Journey" again.
  5. Tails777 (talk) Mario already took my example, but it still stands; the amount of times I've had to type out that title (or even the abbreviation for it) was incredibly annoying. Per all.
  6. Scrooge200 (talk) Yes, these titles can be a pain to write out in full. Per all.

Oppose

Comments

@Camwoodstock Such a parameter can always be added to the template. Super Mario RPG (talk) 18:18, December 18, 2024 (EST)

Salmancer: Mario & Sonic at the Sochi 2014 Olympic Winter Games might be the other worst game title I've had to type out. Mario (Santa)'s map icon from Mario Kart Tour Mario-HOHO! (Talk / Stalk) 00:59, December 20, 2024 (EST)

Damn it, that was gonna be my example! Sprite of Yoshi's stock icon from Super Smash Bros. Ultimate Tails777 Talk to me!Sprite of Daisy's stock icon from Super Smash Bros. Ultimate15:34, December 20, 2024 (EST)

Split image categories into separate ones for assets, screenshots, and artwork

This proposal will address the bloat some image categories have and make them easier to navigate.

Why is this useful? It makes adding to galleries or finding images to replace much easier. If you want to retake screenshots from a game, you can go to the screenshots category to find them. If you have sprite rips to replace, there's a category for that. The same goes for finding images from a game that aren't on the gallery already and being able to sort them more efficiently. This is also how we divide up character galleries already, such as Gallery:Mario (2010-2019).

Now, I can see a few edge cases, like when games have screenshots of themselves for credits images (i.e. Paper Mario: The Thousand-Year Door (Nintendo Switch)). I would still classify these as assets, since they are ripped from the game. Artwork that is used in smaller forms in-game, such as in Super Mario Maker 2, would be classified as artwork if externally released or an asset if it was ripped from the game files. Edge cases shouldn't be too common and they're easy to work out: it's not too different from how we license images or put them in character or subject galleries.

I think the name "assets" would be more useful in shorthand than "sprites and models," in addition to covering textures, so I propose for the category to be called that, but I can change it if there's opposition. The global images category can still exist in the case there's scans, merchandise, video screenshots, or such images that cannot be further categorized.

Proposer: Scrooge200 (talk)
Deadline: January 5, 2025, 23:59 GMT

Support

  1. Scrooge200 (talk) Per proposal.

Oppose

Comments

Removals

None at the moment.

Changes

Broaden the scope of the {{rewrite}} template and its variations

With the previous proposal having passed with being more specific as the most voted, I've come up with a proposal about the possibility to make the {{rewrite}}, {{rewrite-expand}}, and {{rewrite-remove}} templates more specific. As you can see, these templates are missing some smaller text. As such, I am just wondering if there is a possibility to have the smaller text added to the {{rewrite}}, {{rewrite-expand}}, and {{rewrite-remove}} templates.

First of all, the {{rewrite}} template currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>

It has been requested that this article be rewritten.

However, once the proposal passes, the {{rewrite}} template will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}}.</small>
</div>

It has been requested that this article be rewritten for the following reason(s): <reason(s)>.
Please review the Manual of Style and good writing standards and help improve this article.

And another thing—the {{rewrite-expand}} template currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>

It has been requested that this article be rewritten and expanded to include more information.

However, once this proposal passes, the {{rewrite-expand}} will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information.{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by filling in the missing details.</small>
</div>

It has been requested that this article be rewritten and expanded to include more information for the following reason(s): <reason(s)>.
Please review the Manual of Style and good writing standards and help improve this article by filling in the missing details.

Lastly, the {{rewrite-remove}} currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have <u>{{{content|{{{1|content<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}</u> '''removed''' for the following reason(s): {{{reason|{{{2|???<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}
</div>

It has been requested that this article be rewritten to have content removed for the following reason(s): ???

However, once this proposal passes, the {{rewrite-remove}} will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have {{#if:{{{content|{{{1|}}}}}}|<u>{{{content|{{{1}}}}}}</u>|content}} '''removed'''{{#if:{{{reason|{{{2|}}}}}}|<nowiki/> for the following reason(s):{{{reason|{{{2}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by removing the unnecessary details.</small>
</div>

It has been requested that this article be rewritten to have content removed for the following reason(s): <reason(s)>.
Please review the Manual of Style and good writing standards and help improve this article by removing the unnecessary details.

That will be a perfect idea to make the {{rewrite}} template and its variations as more specific as the {{media missing}} and {{unreferenced}} templates. That way, we'll be able to add smaller text to the remaining notice templates in the future.

Proposer: GuntherBayBeee (talk)
Deadline: December 23, 2024, 23:59 GMT

Support

  1. GuntherBayBeee (talk) Per proposal

Oppose

  1. Altendo (talk) As far as I can tell, the proposal that was linked added parameters that allowed what was supposed to be referenced to be referenced. This one simply adds a subtitle to the bottom of each template. "Be more specific" does not mean saying general information and helpful links, but rather exactly what needs to be done; in terms of that, the existing templates not only all already have parameters, but filling them out is enforced. As Nightwicked Bowser said, "Be more specific - Similar to this proposal, what exactly needs references must be specified in the template when putting it in the article. A parameter for this will still need to be added." This only adds a subtitle and does not make this "more specific". As for the changes, this is actually harmful in some way, as the (tagged on {{{date|{{{3}}}}}}) tag will be added to the subtitle, rather than the main body, which could make it more confusing in my opinion. Feel free to update this and add in what "more specific" actually means, or just change this to "add subtitles" and change the location of (tagged on {{{date|{{{3}}}}}}) to the main body, but until then, my vote is staying here.
  2. Mario (talk) Best to keep things simple with these improvement templates.

Comments

Here's how I would fix some things:

First of all, the {{rewrite}} template currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>

It has been requested that this article be rewritten.

However, once the proposal passes, the {{rewrite}} template will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten'''{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}}.</small>
</div>

It has been requested that this article be rewritten for the following reasons:
Please review the Manual of Style and good writing standards and help improve this article.

And another thing—the {{rewrite-expand}} template currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information. {{#if:{{{reason|{{{1|}}}}}}|'''Reason:''' {{{reason|{{{1}}}}}}|<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}
</div>

It has been requested that this article be rewritten and expanded to include more information.

However, once this proposal passes, the {{rewrite-expand}} will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' and '''expanded''' to include more information{{#if:{{{reason|{{{1|}}}}}}|<nowiki/> for the following reason(s): {{{reason|{{{1}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{2|}}}}}}|<nowiki/> (tagged on {{{date|{{{2}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by filling in the missing details.</small>
</div>

It has been requested that this article be rewritten and expanded to include more information for the following reasons:
Please review the Manual of Style and good writing standards and help improve this article by filling in the missing details.

Lastly, the {{rewrite-remove}} currently reads as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have <u>{{{content|{{{1|content<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}</u> '''removed''' for the following reason(s): {{{reason|{{{2|???<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}}}}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}
</div>

It has been requested that this article be rewritten to have content removed for the following reason(s): ???

However, once this proposal passes, the {{rewrite-remove}} will read as follows: 

<div class="notice-template maintenance" style="background:#9CF;border:1px solid #000">
It has been requested that this {{#if:{{{section|}}}|section|article}} be '''rewritten''' to have {{#if:{{{content|{{{1|}}}}}}|<u>{{{content|{{{1}}}}}}</u>|content}} '''removed''' {{#if:{{{reason|{{{2|}}}}}}|<nowiki/> for the following reasons:{{{reason|{{{2}}}}}}|.<includeonly>{{#switch:{{NAMESPACE}}||Gallery=[[Category:Articles with incomplete maintenance tags]]}}</includeonly>}}{{#if:{{{date|{{{3|}}}}}}|<nowiki/> (tagged on {{{date|{{{3}}}}}})}}<br><small>Please review the [[MarioWiki:Manual of Style|Manual of Style]] and [[MarioWiki:Good writing|good writing standards]] and help {{plain link|{{fullurl:{{FULLPAGENAME}}|action=edit}}|improve this {{#if:{{{section|}}}|section|article}}}} by removing the unnecessary details.</small>
</div>

It has been requested that this article be rewritten to have content removed for the following reason(s):
Please review the Manual of Style and good writing standards and help improve this article by removing the unnecessary details.

This should fix some things, and I also recommend you change the title or at least context of this proposal. If so, then I might change my vote. Altendo 19:58, December 9, 2024 (EST)

I fixed this problem for you. How does it look? GuntherBayBeee.jpgGuntherBayBeeeGravity Rush Kat.png 09:40, December 10, 2024 (EST)

Decide what to do with Template:Move infobox

A while ago (November 4th, specifically), I created Template:Move infobox. After all, we had templates for essentially all the Browse tabs on the wiki sidebar, except for moves. There WERE templates about specific types of moves, such as Template:M&L attack infobox, but no general template in the same vein as items, characters, species, games, locations, etc.

I discussed it on the Discord briefly, nobody said no, and a bit of feedback later about how it should look and what it should have, I created it. It has since been applied to exactly four pages at the time of writing, half of which I was the one to apply it to. In hindsight, this could've used with a proposal instead of me just making it, so here's a belated one.

Should we keep Template:Move infobox around? If we do keep it, is it good as is, or does it need changes?

Proposer: EvieMaybe (talk)
Deadline: January 1st, 2025, 23:59 GMT

Keep Move infobox, as is

  1. Sparks (talk) I can see this template working really well for moves that aren't in every Mario game, like Spin. This has lots of potential!
  2. Nintendo101 (talk) Per proposal.
  3. Camwoodstock (talk) We don't see why not--having a dedicated Moves infobox could come in handy, especially if we get any more Mario RPGs in the wake of the weird little renaissance period we've been getting with the back-to-back-to-back SMRPG remake, TTYD remake, and release of Brothership. Per proposal.
  4. Pseudo (talk) Per proposal.
  5. Technetium (talk) Per proposal.

Keep Move infobox, but with changes

Delete Move infobox

Move infobox Comments

Considering the nature of the attack infoboxes, wouldn't it be weird to have moves all in purple but a Mario & Luigi attack use yellow and green and a Paper Mario attack use white and green? Should there be variants of the Move infobox to match the color schemes of existing templates? If an article is covering multiple related moves, how will the infobox work? (ex. Handstand, Cap Throw, Roll, Slide Kick... there's more of these than I thought). What happens when a move is referenced in somewhat less "move-y" ways? Okay, that last one is kinda strange, but basically I mean "dashing" in Super Mario Run is just a fancy animation, Mario & Luigi Dream Team has an animation where Giant Luigi crouches (with posing and skidding clearly meant to be a platformer callback), to slide under an attack. Do these instances get incorporated into the infobox? Continuing the train of thought, what about sports games? Yoshi can Flutter Jump as his special action on Mario & Sonic games. Does that count as a method of input for a Flutter Jump? Salmancer (talk) 21:35, December 19, 2024 (EST)

that's a lot of very interesting questions!
  • i went with purple to set it apart from the already taken light red (game), green and white (character), blue (level), pink (location), grey (item) and navy/grey (species) infoboxes. changing the color could be a good idea.
  • as for sorting which moves "count" or not, we have to decide these things for other types of subject too, after all, and they get infoboxes. it's a valid concern, though! eviemaybe (talk / contributions) 15:09, December 20, 2024 (EST)

Allow blank votes and reclassify them as "per all"

There are times when users have nothing else to add and agree with the rest of the points. Sure, they can type "per all", but wouldn't it be easier to not to have to do this?

Yeah sure, if the first oppose vote is just blank for no reason, that'll be strange, but again, it wouldn't be any more strange with the same vote's having "per all" as a reasoning. I've never seen users cast these kinds of votes in bad faith, as we already have rules in place to zap obviously bad faith votes.

This proposal wouldn't really change how people vote, only that they shouldn't have to be compelled to type the worthless "per all" on their votes.

Proposer: Mario (talk)
Deadline: January 1, 2025, 23:59 GMT

Blank support

  1. Mario (talk) Per all.
  2. Ray Trace (talk) Casting a vote in a side is literally an action of endorsement of a side. We don't need to add verbal confirmation to this either.
  3. PopitTart (talk) (This vote is left blank to note that I support this option but any commentary I could add would be redundant.)
  4. Altendo (talk) (Look at the code for my reasoning)
  5. FanOfYoshi (talk)
  6. OmegaRuby (talk) While on the outset it may seem strange to see a large number of votes where people say "per all" and leave, it's important to understand that the decision was made because the user either outright agrees with the entire premise of the proposal, or has read discussion and points on both sides and agrees more with the points made by the side they choose. And if they really are just mindlessly voting "per all" on proposals with no second thought, we can't police that at all. (Doing so would border on FBI-agent-tech-magic silliness and would also be extremely invading...)
  7. Shy Guy on Wheels (talk) I've always thought of not allowing blank votes to be a bit of a silly rule, when it can so easily be circumvented by typing two words. I think it's better to assume good faith with voting and just let people not write if they don't have anything to add, it's not as if random IPs are able to vote on this page.
  8. TheDarkStar (talk) - Dunno why I have to say something if I agree with an idea but someone's already said what I'm thinking. A vote is a vote, imo.
  9. Ninja Squid (talk) Per proposal.
  10. Tails777 (talk) It's not like we're outright telling people not to say "Per all", it's just a means of saying you don't have to. If the proposal in question is so straight forward that nothing else can be said other than "Per proposal/Per all", it's basically the same as saying nothing at all. It's just a silent agreement. Even so, if people DO support a specific person's vote, they can still just "Per [Insert user's name here]". I see no problem with letting people have blank votes, especially if it's optional to do so in the first place.

Blank Oppose

  1. Doc von Schmeltwick (talk) - Honestly? I'd prefer to get rid of "per all" votes since they're primarily used for the "I don't/like this idea" type of thing that has historically been discouraged. If you don't care enough to explain, you don't care enough to cast IMO.
  2. Technetium (talk) I don't think typing "per all" is that much of an annoyance (it's only two words), and I like clearly seeing why people are voting (for instance, I do see a difference between "per proposal" and "per all" - "per all" implies agreeing with the comments, too). I just don't think this is something that needs changing, not to mention the potential confusion blank votes could cause.
  3. Camwoodstock (talk) Maybe we're a little petty, but we prefer a "per all" vote to a blank one, even if "per all" is effectively used as a non-answer, because it still requires that someone does provide an answer, even if it's just to effectively say "ditto". You know what to expect with a "per all" vote--you don't really get that information with a fully blank vote.
  4. Ahemtoday (talk) Forgive me for the gimmicky formatting, but I want to make a point here — when you see a blank oppositional vote, it's disheartening, isn't it? Of course, it's always going to be that way when someone's voting against you, but when it doesn't come with any other thoughts, then you can't at all address it, debate it, take it into account — nothing. This also applies to supporting votes, if it's for a proposal you oppose. Of course, this is an issue with "per all" votes as well. I don't know if I'd go as far as Doc would on that, but if there's going to be these kinds of non-discussion-generating votes, they can at least be bothered to type two words.
  5. Jdtendo (talk) Per all (is it too much to ask to type just two words to explicitely express that you agree with the above votes?)
  6. Axii (talk) Requiring people to state their reason for agreeing or disagreeing with a proposal leads to unnecessary repetition (in response to Doc). Letting people type nothing doesn't help us understand which arguments they agreed with when deciding what to vote for. The proposer? Other people who voted? Someone in particular, maybe? Maybe everyone except the proposer? It's crucial to know which arguments were the most convincing to people.
  7. Pseudo (talk) Per Technetium, Camwoodstock, and Axii.
  8. Hooded Pitohui (talk) I admit this vote is based on personal preference as any defensible reasoning. To build on Camwoodstock and Ahemtoday's points, though, the way I see it, "per all" at least provides some insight into what has persuaded a voter, if only the bare minimum. "Per all" is distinct at least from "per proposal", suggesting another voter has persuaded them where the original proposal did not by itself. A blank vote would not provide even that distinction.
  9. Mister Wu (talk) Asking for even a minimal input from the user as to why they are voting is fundamental, it tells us what were the compelling points that led to a choice or the other. It can also aid the voters in clarifying to themselves what they're agreeing with. Also worth noting that the new editors simply can't know that blank means "per all", even if we put it at the beginning of this page, because new editors simply don't know the internal organization of the wiki. Blank votes would inevitably be used inappropriately, and not in bad faith.
  10. DesaMatt (talk) Per all and per everyone and per everything. Per.

Blank Comments

I don't think banning "per all" or "per proposal" is feasible nor recommended. People literally sometimes have nothing else to add; they agree with the points being made, so they cast a vote. They don't need to waste keystrokes reiterating points. My proposal is aiming to just streamline that thought process and also save them some keystrokes. Mario (Santa)'s map icon from Mario Kart Tour Mario-HOHO! (Talk / Stalk) 20:34, December 17, 2024 (EST)

I think every sort of vote (on every level, on every medium) should be written-in regardless of whether something has been said already or not; it demonstrates the level of understanding and investment for the issue at hand, which in my opinion should be prerequisite to voting on any issue. Doc von Schmeltwick (talk) 20:53, December 17, 2024 (EST)
There is no way to actually determine this: we are not going to test voters or commenters their understanding of the subject. Someone can read all of the arguments and still just vote for a side because there's no need to reiterate a position that they already agree with. BabyLuigiFire.pngRay Trace(T|C) 20:55, December 17, 2024 (EST)
My personal belief is that "test[ing] voters or commenters their understanding of the subject" is exactly what should be done to avoid votes cast in misunderstanding or outright bandwagoning. Doc von Schmeltwick (talk) 23:06, December 17, 2024 (EST)
My personal view is that a change like the one you are suggesting potentially increases the odds of inexperienced or new users feeling too intimidated to participate because they feel like they do not have well articulated stances, which would be terrible. I think concerns about "bandwagoning" are overstated. However, more pressingly, this proposal is not even about this concept and it is not even one of the voting options, so I recommend saving this idea for another day. - Nintendo101 (talk) 23:32, December 17, 2024 (EST)
@Mario I agree. Banning people from saying that in proposals is restricting others from exercising their right to cast a vote in a system that was designed for user input of any time. I'd strongly oppose any measure to ban "per" statements in proposals. Super Mario RPG (talk) 00:11, December 18, 2024 (EST)

Technetium: I understand, but blank votes are a fairly common practice in other wikis, and it's clearly understood that the user is supporting the proposal in general. Mario (Santa)'s map icon from Mario Kart Tour Mario-HOHO! (Talk / Stalk) 20:36, December 17, 2024 (EST)

Fair point, I didn't know that. Not changing my vote just yet, but I'll keep this in mind as the proposal continues. Technetium (talk) 20:48, December 17, 2024 (EST)
There's a lot of variation in how other wikis do it. WiKirby, for example, doesn't even allow "per" votes last I checked. Hewer (talk · contributions · edit count) 04:13, December 18, 2024 (EST)

I'm not really much of a voter, but I'm of the opinion "it's the principle of the matter". Requiring a written opinion, of any kind, at least encourages a consideration of the topic. Salmancer (talk) 21:35, December 19, 2024 (EST)

Stop integrating templates under the names of planets and areas in the Super Mario Galaxy games

Based on the vote so far, this proposal may be eligible to close one week early. Please use {{proposal check|early=yes}} on December 25 at 23:59 GMT and close the proposal if applicable.

The aims of this proposal is to repeal this one that passed earlier this year. I will reiterate my position here:

The planetary bodies in galaxies do not just "lack" publicly accessible names - they are straight up not supposed to have names. The Shogakukan guidebook for Mario Galaxy does not give planets name. The game does not give planets name. The instruction booklet does not give planets name. The only "source" that applies discrete names for planets are from the developers and we have no reason to think these were intended to be the planets. These galaxy articles are generally a bit outdated, and I think the mistake in the first place was suggesting that some of the planets have real names "except where otherwise noted." They largely do not. I think it would would healthier to recognize that they are just different sections of a greater whole, much like areas in courses for the earlier 3D games, and apply titles accordingly.

To elaborate on my perspective, I think using dev data to provide names for these planets is completely fine, and I understand the desire to do so. Citing the Prima Games guidebooks for potential names for these areas is fine. That is not what this proposal is about. Rather, integrating the templates themselves - be it for conjectural or dev data-derived names - underneath the individual headers for each planet, in my view, looks very poor, as you can see here for Yoshi Star Galaxy and Honeyhive Galaxy. They are detractingly eye-catching and break these articles without substantive benefit. I think having a nonintrusive note at the top or bottom of these articles - as was the case before the proposal I link to above passed - is perfectly sufficient and healthier for these articles.

I provide two options:

  1. Support: Do not put conjectural and dev-data name templates beneath the names of individual planets and areas in the Super Mario Galaxy games: This is a full repeal of the proposal I link to above.
  2. Oppose: Change nothing

Proposer: Nintendo101 (talk)
Deadline: January 1, 2025, 23:59 GMT

Support: Do not put templates underneath the name's of planets and areas

  1. Nintendo101 (talk) Per proposal.
  2. 1468z (talk) Per proposal.
  3. Waluigi Time (talk) The previous solution looked a lot nicer. I also agree with Nintendo101 that we should rethink how we approach planet names in general. They don't necessarily "need" names any more than specific portions of levels in other games do.
  4. Jdtendo (talk) I still don't agree with the "planets are not supposed to have names" argument, but I do agree that having templates beneath every section heading is excessive.
  5. Camwoodstock (talk) Per all, especially Waluigi time. The overall assumption that the planets have names unless otherwise stated feels like the consequence of a decision made very, very early on into the wiki, that's just kind of gone unquestioned or unnoticed until very recently. This won't stop that particular case of WikiJank™ completely, but it's a step in the right direction.
  6. Sparks (talk) Per all.
  7. EvieMaybe (talk) if all the names are unofficial, then we only need to say it once. if there's an official name, we can just say "all names are unofficial unless specified" and specify in the one planet that has a name (is there any planets with names even???). having the template on each individual section is both ugly and inefficient
  8. Mario (talk) Yeah, the setup before this was satisfactory. Per Evie, but I also agree with Waluigi Time that we probably don't need to require naming these parts of the level either.
  9. Ray Trace (talk) I always thought assigning these objects meant to be part of the environment conjectural templates has always struck me as odd and I don't know why only Super Mario Galaxy gets singled out out of all games. We don't name the rooms the Mario Party minigames take place in.
  10. Tails777 (talk) I was sincerely confused when I saw the templates put back on the various galaxy articles and questioned "Why? It was better beforehand." Per all.
  11. Hooded Pitohui (talk) In the longer-term, WT and Nintendo101 bring up points which ought to be considered. In the shorter term, this would be a beneficial first step to de-cluttering these sections for better readability.
  12. Ninja Squid (talk) Per all.
  13. Technetium (talk) Per Nintendo101, Waluigi Time, and Porple's comment below.
  14. MCD (talk) Per N101, WT and Porple below. I also agree our attitude on what counts as "conjectural" when it comes to naming planets needs a rethink, i.e. it's not conjecture to call the planet the player starts on the "starting planet" because that's just a factual description. (Also, why does Starting Planet just redirect to a random galaxy? lol)

Oppose: Keep the templates

  1. Ahemtoday (talk) I'm opposing this proposal as currently slated to be implemented — as in, just removing Template:Conjecture and Template:Dev data from these sections and leaving it at that. These need to be marked, and I don't feel that an "unless otherwise noted" disclaimer is an elegant way to do that. However. There is a way of accomplishing this that I would be amenable to: replacing those templates with Template:Conjectural or a new dev data equivalent to it. This is the same way our glitch pages do it, for exactly the same reason you want to get rid of these templates on the galaxy pages. I think it makes perfect sense to use this convention here as well to solve this problem.

Comments on the planet template proposal

I agree that we don't need the repeated templates, and the whole naming situation of the planets is a bit odd. Rather than giving the planets capitalized "names" (e.g. "Starting Planet") and noting them as conjectural, they should just be described in sentence case, at which point it should be somewhat obvious that it's a description and not a "name". For example, section heading "Starting planet" and text "The starting planet has..." You could do a single {{conjecture|subsections=yes}} under the "Planets" heading if you really wanted to, but I think if we removed all the inappropriate capitalization then even that wouldn't be necessary. --Steve (talk) Get Firefox 20:11, December 19, 2024 (EST)

Set Vector-2010 to the default wiki skin

This proposal is about setting the 2010 Vector as the default wiki skin (screenshot here) for desktop users, with the focus being on people who are new to wikis in particular, while obviously keeping the existing MonoBook skin as an option. What made me think to create this proposal is when I made a Talk:Main Page proposal about the to-do list tasks and how they are more accessible than clicking the "Wiki maintenance" on the sidebar, I had to uncomfortably squint to find "Wiki maintenance" on the wiki sidebar. But Vector-2010 has the sidebar links slightly larger and a bit more spaced out. With the existing interface, there could be some who may struggle to find options listed on the sidebar.

While we're clearly different from Wikipedia (that's why I'm not Vector-2022, since it'd be too much of a departure and likely uncomfortable for several), I do want to refer to this page, which summarizes why Wikipedia transitioned to it. Though it is vague, they cite accessibility as the reason, which I think this wiki has been taking steps toward doing.

I'll cite my reasons for preferring Vector and applying this to possible people who are visiting a wiki for the first time. The text is larger, which is especially important for larger screen monitors, some of the lesser used tabs are collapsible on the sidebar, summarizing the most commonly used options, and the user links at the top right are also more noticeable and less close to the body of the article where the content is read.

Though it could take time getting used to the Edit button being on the right (not to mention the search button), the button is at least larger, making it more usable on even lower quality screen monitors, and I like how it's separate from the Page and discussion options, meaning that options that involve viewing articles are on the left while options that involve editing or changing the page in some form are on the right.

If this proposal passes and others don't like the change, they can always return to the MonoBook option in their preferences.

Proposer: Super Mario RPG (talk)
Deadline: January 1, 2025, 23:59 GMT

Support

  1. Super Mario RPG (talk) Per.

Oppose

  1. Camwoodstock (talk) Admittedly, this vote is largely a matter of preference--we just don't like Vector that much--but we can't think of any real reason to switch to Vector 2010 as the default over the current Monobook beyond the mentioned text spacing; while that is a nice boon, we personally find the weird gradient buttons for the various tabs up top a little grating looking, and we're a fan of the more compact design that Monobook provides--though, this is likely a byproduct of our personal preference for more neatly packed web design. And uh, the less said about the other two options (Vector 2022, and. Timeless. Which is the most dated theme possible, namely to mid-2010s mobile web design.), the better. If you like Vector 2010, that's great, and we're fine with that! Heck, if anyone likes Vector 2022 or Timeless, that's cool too, and more power to them! Variety is the spice of life, after all. But switching it to the default is something that should not be taken lightly, and the reasons for a switch in this proposal feel a little too loosey-goosey for us, we're sorry.
  2. DryBonesBandit (talk) Per Camwoodstock.
  3. Nintendo101 (talk) I like how MonoBook looks a little more than Vector. It is what I am comfortable with. If it ain't broke, don't fix it.
  4. Drago (talk) Per Nintendo101. I actually prefer the smaller text of Monobook since you can see more of the page at once. I also want to point out that although logged-in users like us can change the skin in preferences, we'd still be forcing the change on logged-out users.
  5. Ahemtoday (talk) Per Drago.
  6. Technetium (talk) Per Nintendo101 and Drago. I just don't see any reason to make this change.
  7. Altendo (talk) I'm saying this as a Vector-2010 skin user, and I'll say that people have their preferences. I live Vector-2010 because that is how Wikipedia at least used to look before they switched to Vector (2022); On Wikipedia, Vector was renamed to Vector legacy (2010), while Vector 2022 is named Vector (2022). Although I do prefer Vector-2010, I know a lot of people that prefer Monobook, and even if not, this can be changed in the preferences. No need to change the default skin. I get that IPs can't change their appearance, but aside from that, users can, and what they see doesn't have to be default on the wiki. Everyone can change what they specifically see.

Comments

@Camwoodstock That is true that it's a major change. It's based mainly upon impression from newcomers from them seeing a more prominent edit tab, slightly larger text size, and other minor details like tab names that are easier to read (including a collapsible feature for the lesser used tab). The skin change was based on old Wikipedia research at the time (like how WikiLove was a result of their research). I have no strong feelings whether this passes or not. Although it's vague, since there's no way to tell the statistics (and the wiki's already successful at the moment), I still have a feeling it could help some, but to each their own. Super Mario RPG (talk) 18:32, December 18, 2024 (EST)

We feel like if anybody would be capable of providing any statistics on skin usage, it'd be Porple, but even then, we don't actually know if that's one of the things he tracks, and it feels a little silly to pester him over this of all things... ;p ~Camwoodstock (talk) 18:55, December 18, 2024 (EST)

I'm okay with opposition, but in case of misunderstanding, this proposal isn't about personal preferences so much as what I believe to be a more ergonomic interface to a wider audience. I know we're not Wikipedia, but there's also the consideration that they've used the Vector skin longer than they had for MonoBook. Super Mario RPG (talk) 13:45, December 19, 2024 (EST)

If it's what "you believe", then it ultimately (and probably unavoidably) is about personal preferences. Anyway, another consideration is the fact that people often prefer what they're used to. I feel like how long this wiki has used its skin is more relevant than how long Wikipedia has. Hewer (talk · contributions · edit count) 16:39, December 19, 2024 (EST)
@Hewer I suppose I'm overthinking the ergonomic interface. Super Mario RPG (talk) 15:19, December 20, 2024 (EST)

Miscellaneous

Use official alt text as a source

Based on the vote so far, this proposal may be eligible to close one week early. Please use {{proposal check|early=yes}} on December 24 at 23:59 GMT and close the proposal if applicable.

What I refer to here as "alt text" is text that is either:

  • shown in place of a file, such as an image, when the file doesn't load;
  • shown as a small note when you hover your mouse on an image on PC. See for yourself with this pic: This is a Mario Star.

To quote the Wiki article I linked above, alt text "is used to increase accessibility and user friendliness, including for blind internet users who rely on special software for web browsing."

Nintendo's web content makes hefty use of this feature, particularly in activities on the Play Nintendo site, where it is employed for decorative stickers users can select and manipulate. Alt text is certainly a unique means to convey information that, currently, is not treated in any the entries laid out in the wiki's "acceptable sources for naming", including entry 2 concerning web material, and hasn't been discussed to my knowledge. Since alt text can bear information of its own, as explained below, it might be time we decided if this quaint thing should be supported in the policy.

The following aspects should be kept in mind as a decision is made on this topic:

  • tempting as it may be, alt text cannot be construed as internal material in the way filenames are. A filename, whether pertaining to a file in a video game or a file on a web page, serves a utilitarian purpose that is, above all, an organizational tool meant to aid the developers of said game or website. Contrarily, the very purpose of alt text is to be seen by the end user (that is, the regular Joe or Jane the product is being shown to) under special circumstances.
  • on the other hand, alt text may display some level of unprofessionality or unfamiliarity with the source material on the part of its author--that is to say, it can lend to some pretty weird information about a given subject. The few examples I've come across are an ornament resembling a mushroom item being referred to as a "Toad ornament" (play.nintendo.com via archive.org), Koopa Paratroopa being called a "Koopa Flying Trooper" (play.nintendo.com via archive.org), and Meowser being called "Cat Bowser" (play.nintendo.com). I'd like to stress that this is far from the norm, as evident in those links--Mario is called "Mario", Goomba is "Goomba" etc., heck, some lesser known characters like Lottie, Wardell, and Niko from Animal Crossing are correctly identified in that Ornament Creator activity--, but I believe it's fair of me to show you a comprehensive image of the situation.

Most importantly, beyond the typical "they offer unique names and spellings" claptrap, I've noticed that citing such material is genuinely practical in select situations. The one recent example that comes to mind is that the alt text of some Play Nintendo activities helped me delineate a few otherwise non-descript stars shown at Gallery:Super Star. The Super Star item, the one used in games to make player characters invincible, has in the past shared 2D graphics with the Power Star collectable McGuffins from 3D titles, so when identifying a given Star graphicMedia:MH Oct 4.svg with zero context to its nature, all bets are off; rather than resort to speculation and potentially erroneously place a non-descript star graphic in the Super Star's gallery (as previously done), one can look up the graphic's alt text on Nintendo's website and use that as a crutch, if there's absolutely nothing else.

I propose three options for handling material presented in this manner.

  1. Cite alt text the same way media, including other web content, is typically cited. This means that if a Goomba's alt text is "Toothy Mushroom" in a context where most or every other element from the Mario series is given their usual names, then "Toothy Mushroom" is treated as a valid alternate name for the Goomba, shown on the Goomba article, and referenced from the aforementioned alt text. As argued above, alt text is meant to be seen by the end user, placing it somewhere above level 6 (concerning internal game filenames) of the current source priority policy under this option.
    1. Some exceptions can be made in this scenario. If, for instance, wiki users deem that a discrete piece of web content handles alt text in an overwhelmingly unprofessional manner, they may choose not to cite it. As a concrete example, the 2024 Calendar Creator activity at Play Nintendo reuses the exact same alt text from its 2023 iteration for its decorative stickers, even though said stickers changed. According to that activity, Cheep Cheeps are also called "Monty Moles" and Pokeys are also called "Chain Chomps". This obviously represents some level of carelessness that shouldn't be reflected on the wiki even if the content is technically official. However, it's also the exception, not the rule.
  2. Cite alt text only for redirects and/or when no other source is available for a given thing. This means that "Koopa Flying Trooper" and "Cat Bowser" will be removed from the Koopa Paratroopa and Meowser pages respectively, but will remain as redirects to these pages. The explanations at Gallery:Super Star#Notes and Gallery:Miscellaneous mushrooms#Notes will remain as well, because alt text is currently the only means to identify certain graphics on those pages as being a particular type of star or mushroom.
  3. Do not cite alt text in any of the ways described above.

Note: The articles concerning the Play Nintendo activities mentioned above (Cat Transformation Center, Paper Mario: The Origami King Collage Maker etc.) will continue to list the alt text of each graphic as captions regardless of the proposal's outcome. This provides quick cross-referencing to someone who really wants to know how a decoration is called in those activities.

Proposer: Koopa con Carne (talk)
Deadline: December 31, 2024, 23:59 GMT

Support: cite alt text for everything, including unique names

  1. Koopa con Carne (talk) Per proposal!
  2. Hewer (talk) I'd think alt text would be covered under "web content" in the naming policy. There's no reason for it not to be, given that it's official text, and is more intended to be seen by the end user than image filenames, which we already agreed are fine. If something's obviously a mistake, we can say that without discrediting the whole source, like we already do with other sources (e.g. the Cleft article acknowledging the "Moon Cleft" name from Super Paper Mario despite deeming it "mistaken").
  3. Camwoodstock (talk) The future is now, old man! We're in an era of Bluesky and screen reader compatibility! Okay, jokes aside, we're a little surprised that alt text hasn't been accounted for already, given it has been around the internet for a very, very long time. Still, better late than never, we suppose. Per proposal, and Hewer especially!
  4. EvieMaybe (talk) per Hewer
  5. Altendo (talk) Per all.
  6. Nintendo101 (talk) Per Hewer.
  7. Super Mario RPG (talk) Per everyone.
  8. FanOfYoshi (talk) Spear Guy.gif
  9. OmegaRuby (talk) It's kind of surprising how this hasn't been implemented nor standard in some way yet - there's no reason that it isn't! I'm all for increased accessibility and the use of accessibility features such as alt text. Per all.
  10. Technetium (talk) Per all.
  11. Pseudo (talk) Per all.
  12. Axii (talk) Per proposal.png

Support: only cite alt text for redirects and/or if there is no other source available

Oppose: do not cite alt text at all

Comments (alt text proposal)

RE the "Toad Ornament": I think it's worth mentioning that calling some type of mushroom item a "Toad" is not unheard of in official works. But ok, it's less likely the typist of that Play Nintendo activity was thinking of Hotel Mario, and more likely they just confused Super Mushrooms with Toads due to their similar appearances. -- KOOPA CON CARNE 16:45, December 17, 2024 (EST)

Tsurara

@OmegaRuby: The proposal itself is about allowing alt text to be considered a valid source, not broadening usage of alt text as a whole. That being said, on that note, I do wonder if we could perhaps do just that (likely as part of another proposal), mostly in the context of sprites--such as this example on the left from the Icicle article. A usual caption would absolutely not fit on this, but alt text could help provide something for a screenreader to read out. The main issue is that, to my knowledge, the "frame" parameter inherently means the alt text is the caption, which could cause issues if we need the actual, well, frame... ~Camwoodstock (talk) 12:43, December 18, 2024 (EST)

Retrieved from "https://www.mariowiki.com/index.php?title=MarioWiki:Proposals&oldid=4469951"