MarioWiki:Proposals: Difference between revisions

From the Super Mario Wiki, the Mario encyclopedia
Jump to navigationJump to search
No edit summary
No edit summary
 
Line 1: Line 1:
{{MarioWiki:Proposals/Header}}
{{/Header}}
==Writing guidelines==
''None at the moment.''
 
==New features==
===Establish a format for poll proposals on the archive lists===
Something that's slipped through the cracks when we invented poll proposals was what we do when we add them to [[MarioWiki:Proposals/Archive|these]] [[MarioWiki:Proposals/TPP_archive|pages]]. We can't simply have one link to the poll proposal — the entire purpose of the format is that different parts of it can pass and fail independently of one another. What color do we put a proposal where one thing fails and another thing succeeds in?
 
I have several pitches for you.
 
<big>'''''OPTION ZERO'''''</big><br>
Do nothing. I'm putting this at the front because I want to leave room for any good-sounding solutions beyond the four I'm about to suggest. It's here on the proposal at all because I'm pretty sure I'm legally obligated to put it here, but I'll be honest — I'm not entirely sure what this winning would... mean. Our hand will eventually be forced when our first poll proposal fully resolves, so a format will be established one way or the other.
 
<big>'''''OPTION ONE'''''</big><br>
The different issues of a poll proposal share a number corresponding to when the first issue closes. They're listed separately, and distinguished from each other via letters. As an example, the three parts of [[Talk:Yoshi_(species)#Properly_define_Brown_Yoshi|the Brown Yoshi proposal]] would slot in at #83A, #83B, and #83C. (That would shove some other proposals down; we could also just append them to the end of the list like normal and brush off the inconsistency if y'all prefer.)
 
The Brown Yoshi proposal is also a handy demonstration of an edge case we have to contend with — if this proposal passed ''right now'', we would list #83A as red and #83B as gray, but what would happen with #83C, which is still ongoing? This is the aspect on which Options One and Two differ. In Option One, issues are not added to the archive page until they close. The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later


===List of Talk Page Proposals===
I would like to note that the Brown Yoshi proposal is a remarkably well-behaved example. If the issues were ordered differently, we may at one point have #83A and #83C on the list with no #83B until later.
*Merge [[Kat and Ana's Swords]] with [[Kat and Ana]] ([[Talk:Kat and Ana's Swords#Merge with Kat and Ana|Discuss]]) '''Passed'''
*Merge [[Dribble and Spitz's taxi]] with [[Dribble and Spitz]] ([[Talk:Dribble and Spitz's taxi#Merge with Dribble and Spitz|Discuss]]) '''Passed'''
*Merge [[The Goodwill Ambassador]] to [[Cackletta]] ([[Talk:The Goodwill Ambassador#Merge with Cackletta|Discuss]]) '''Deadline:''' July 19, 2014, 23:59 GMT
*Split [[Red Luma]], [[Green Luma]] and [[Blue Luma]] from [[Luma (species)]] ([[Talk:Luma (species)#Split certain colored Lumas from Luma article.|Discuss]]) '''Deadline:''' July 19, 2014, 23:59 GMT


==Writing Guidelines==
<big>'''''OPTION TWO'''''</big><br>
''None at the moment.''
Option Two is identical to Option One except in how it handles open issues on partially closed poll proposals. In this option, they ''are'' added to the list alongside the other issues, and marked with a new color — let's say black.


==New features==
This prevents the awkward gaps we would be susceptible to in Option One, but it ''is'' introducing a whole color for a temporary edge case.
===Have a EULA system for users to sign before joining this wiki===
 
I have seen that a lot of users day by day when they join they immediately start vandalizing articles and blanking pages and are ignorant. I've been thinking we should implement a End User License Agreement system in our user creation system that the user should read and agree with while they are creating their account. At least that will let the user know what our expectations are while they are creating their account so that they don't shoot their foot off and vandalize this wiki. You know we should have it set up that the user can only hit I agree after he/she reads the entire thing just like how Windows NT 4.0 and 3.XX 's eulas work.
<big>'''''OPTION THREE'''''</big><br>
Option Three is simpler. We create a new color in the archive for poll proposals — I guess let's say black again. Poll proposals get added to the archive when all issues on them are closed.
 
This saves space (the other options will have to give fourteen entries to [[Talk:List_of_references_on_the_Internet#Determine_what_memes_should_be_on_the_Internet_references_page|this proposal]], but it means the entry on the list doesn't reflect anything about any individual issue's status, such as whether it's been implemented or not.
 
''EDIT: Camwoodstock's pitch below of using three colors (and, implicitly, adding the poll proposal to the archive when it has any closed issues) doesn't entirely eliminate that negative, but it does seem much more useful than just having the one color.''
 
<big>'''''OPTION FOUR'''''</big><br>
Option Four is simpler still. Each issue is treated as if it were an entirely separate proposal. Each gets numbered and appended to the list when it closes regardless of what anything else in the poll proposal is up to.
 
The negative of this way of doing it is that the issues of a poll proposal may end up strewn about the list in a way that doesn't really reflect that they're a related thing.
 
'''Proposer''': {{User|Ahemtoday}}<br>
'''Deadline''': March 18, 2025, 23:59 GMT
 
====Option Zero====
====Option One====
#{{User|Ahemtoday}} It's either this or Option Two for me — it's important to me that the issues end up next to each other on the archive ''and'' that the status of each one is visible on the page.
====Option Two====
#{{User|Ahemtoday}} See my note about Option One.
#{{User|Camwoodstock}} Secondary option, but we do think darker shades of the colors (a-la our pitch for Option Three) would be nice. Helps distinguish at a glance what was a poll proposal.
====Option Three====
#{{User|Camwoodstock}} We would like to pitch a more sophisticated variant of this; 3 new colors. One for a poll that has concluded, one for a poll that is partially concluded, partially ongoing, and one for a poll that has been partially overturned by a future proposal. Maybe dark green, dark gray, and a dark yellow? The darker colors, of course, to contrast with the non-poll proposals.
====Option Four====
====Comments====
{{@|Camwoodstock}} — I definitely think your pitch for Option Three is better than the version I was suggesting. I'm not really sure about the pitch for Option Two, though — the letters already distinguish them, and I feel like they'd seem more like separate states rather than a "modifier" on some of the existing ones. Not to mention, wouldn't we need a darker version of every single color just in case? That's a lot of changes to make, and we'd end up running into problems with dark blue, teal, and dark teal; or "dark white", gray, and dark gray. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 03:20, March 4, 2025 (EST)
 
I don't quite understand option one and two, as the above rules for poll proposals state "A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done." --[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 07:09, March 4, 2025 (EST)
:Could you explain the contradiction in greater detail? I don't see what you mean. [[User:Ahemtoday|Ahemtoday]] ([[User talk:Ahemtoday|talk]]) 12:01, March 4, 2025 (EST)
 
==Removals==
''None at the moment.''


[[File:WinNT_4.0_EULA_demo.png|200px]]  
==Changes==
===Include italics for category page titles for media that normally uses it===
Shouldn't category pages for media that uses italics (such as games, shows, movies, etc.) use italics for their category pages? I did start adding it to some pages already, but I thought it was worth proposing about it, possibly to make it policy. I feel like italics should be used though, as it is used everywhere else. For example, the page titled [[:Category:Donkey Kong 64]] should be [[:Category:Donkey Kong 64|Category:''Donkey Kong 64'']].


'''Proposer''': {{User|Pwwnd123}}<br>
'''Proposer''': {{User|Kaptain Skurvy}}<br>'''Deadline''': <s>February 20, 2025, 23:59 GMT</s> <s>Extended to February 27, 2025, 23:59 GMT</s> Extended to March 6, 2025, 23:59 GMT
'''Deadline''': July 23, 2014, 23:59 GMT


====Have====
====Support====
#{{User|Pwwnd123}} Per my proposal and my comments below.
#{{User|Kaptain Skurvy}} Per proposal.
#{{User|Camwoodstock}} Wait, this isn't already policy??? We think this lack of parity speaks a lot to how neglected categories can be in some regards. While yes, the category description isn't really meant to be the main point, we don't think ''slightly slanted text'' is distracting from the actual list of articles in the category, and just because categories are more utility than text doesn't excuse the text that ''is'' there looking below the standard of a usual article for being "lesser".
#{{User|Super Mario RPG}} Nothing wrong with having more consistency around the wiki.
#{{User|GuntherBayBeee}} Per all.
#{{User|Salmancer}} It is easier to figure out what the standards are from context alone when the standards are applied in every instance.
#{{User|Hewer}} The proposer has confirmed on their talk page that the goal of the proposal is just to put [[Template:Italic title]] on category pages, so concerns about formatting the category links on articles are moot (and I'm not sure applying it there would even be possible anyway). With that cleared up, per all, I don't see the harm in some more consistency.
#{{User|EvieMaybe}} per Hewer
#{{User|Shy Guy on Wheels}} sure, for consistencies sake
#{{User|LadySophie17}} Per Hewer, then.


====Don't Have====
====Oppose====
#{{User|Randombob-omb4761}} Per Glowsquid in the comments.
#{{User|Nintendo101}} Categories are supposed to provide simple, direct, and utilitarian functions, not something to be read or presented to readers. I don't think italicizing them is necessary and would detract from their simplicity.
#{{User|Walkazo}} - Per Glowsquid and Baby Luigi in the comments. This is completely pointless.
#{{User|Sparks}} Per Nintendo101. It doesn't feel necessary.
#{{User|Koopakoolklub}} Per Glowsquid and myself.
#{{User|OmegaRuby}} What is this supposed to change, exactly? Yes, it's in line with how pages about games are to have the subject italicized, but the change feels unneeded and especially arduous to implement for pretty much no reason. Per Nintendo101.
#{{User|Vommack}} Per comments. If people join up to vandalize, an EULA isn't going to stop them. Writing and enforcing one of these would just be a huge waste of time.
#{{User|SolemnStormcloud}} Per all.
#{{User|Ghost Jam}} Per all. It's a formality that holds no actual weight and it going to be more trouble than it's worth to set up.
#{{User|Rykitu}} Per Nintendo101
#{{User|Mario4Ever}} Per all.
#{{User|Mushroom Head}} Per all
#{{User|MichiganMarioFan}} Per all. This will not make the registration process any harder than it currently is.
#{{User|Technetium}} Per all.
#{{User|'Shroom64}} Just because we have many screenfulls of words people will "have to" read, doesn't mean people ''will'' read it and listen to it. They're probably going to vandalize anyway. Per all.
#{{User|Pseudo}} Per Nintendo101.
#{{User|Yoshi876}} Per Glowsquid in the comments.
#{{User|Baby Luigi}} if you like to cut down vandal traffic, legal stuff won't stop them. this is a free-edit wiki site, and its purpose should remain stuff. if you really want to stop vandals, spend your time making a ClueBot-like bot or something.
#{{User|Mario}} These are like License Agreements, except License Agreements are intentionally written in a way that hardly anyone will ever read them.


====Comments====
====Comments====
But if a user immediatelty starts vandalizing articles, that's probably just what they are: vandalists who join just to cause trouble. I don't think they'd care much about what we expect. --{{User:Koopakoolklub/sig}} 10:38, 16 July 2014 (EDT)
@Nintendo101: In that case, why do we italicise game titles in category descriptions? (Genuine question, I'm undecided on this proposal.) {{User:Hewer/sig}} 08:58, February 7, 2025 (EST)
:Because that is a proper sentence. It is not the tool itself. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 20:15, February 7, 2025 (EST)
::We mean... Wiki policy is to italicize game titles on their articles' names using <nowiki>{{Italic title}}</nowiki>, too, and those aren't proper sentences. They're article names. {{User:Camwoodstock/sig}} 19:00, February 8, 2025 (EST)
:::That's not the same situation in my eyes because the articles are what the site is for. That is what we are writing and presenting to the public. Of course we would italicize those. The categories are a tool, chiefly for site editors, not readers. We do not really gain anything from italicizing their titles. If anything, I worry this would lead to a lot of work to implement, either burdening site editors, porplemontage, or both. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 16:05, February 9, 2025 (EST)
::::So category names are just tools not meant for readers, but category descriptions aren't? {{User:Hewer/sig}} 18:08, February 9, 2025 (EST)
:::::The descriptions are just sentences, and I feel inclined to render those they way we would a sentence anywhere else on the site, be it on articles or in the description for image files. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 19:49, February 9, 2025 (EST)
::::We disagree with the notion categories are more for editors and not readers; while yes, all of the categories on the front page are maintenance categories from the to-do list, the sheer quantity of proposals for categories wouldn't make sense if they were moreso for editors, rather than your average reader; moves such as the reforms for the Look-alikes categories or the Thieves category wouldn't make sense if these weren't meant to be public-facing. And of course, there are the various categories that exist for users, but do ''not'' serve a utility purpose, such as the [[:Category:User es|various "users that know a given language" categories]].<br>As for difficulty implementing, considering the recent success stories with images without descriptions and categories without descriptions having gone from 4000+ and ≈100, to 0 and 0 respectively, we have it in good faith that this wouldn't be ''that'' hard to implement. Monotonous? Yes. But difficult? It's nothing a bit of caffeine and music can't solve. {{User:Camwoodstock/sig}} 18:22, February 9, 2025 (EST)
:::::Not only for editors, but chiefly for them. I don't exclude the idea of more curious readers utilizing them, but I suspect they are exceptions. I maintain that their ease of implementation is more important to the site than the formatting inconsistency. Like, are we to be expected to format category ourselves as "<nowiki>[[Category:Super Mario World screenshots|Category:''Super Mario World'' screenshots]]</nowiki>" instead of just "<nowiki>[[Category:Super Mario World screenshots]]</nowiki>" going forward? Would we do this for the articles that are in dozens of categories? Why? I would not want to do that, and I don't find the inconsistency a good enough reason to roll something like that out, and only brings downsides. It makes the tool where one types "<nowiki>[[Category:</nowiki>" almost entirely moot because we would still need to write out the whole name just to format it this way. Others are welcomed to think differently, but I personally think the way we format these names now in categories is perfectly fine. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 19:49, February 9, 2025 (EST)
even if this proposal doesn't pass, i think we should use [[Template:Italic title]] in the category pages. {{User:EvieMaybe/sig}} 10:16, February 12, 2025 (EST)
:I thought that was the whole proposal. {{User:Hewer/sig}} 03:32, February 13, 2025 (EST)
::@Kaptain Skurvy: Could you please clarify whether the proposal's goal is simply to add italic title to categories, or to also do something else as well? {{User:Hewer/sig}} 20:14, February 17, 2025 (EST)
:The proposer has clarified on their talk page that adding the italic title template to categories is all the proposal would do if it passed. {{User:Hewer/sig}} 15:21, February 23, 2025 (EST)
 
===Make a standard for citing different pages/sections of the same source across an article, codify it at [[MarioWiki:Citations]]===
The formatting of citations has been a recurring, if sometimes contentious, topic of discussion around here. What I describe in the proposal's heading is something that happens more often than you'd expect, so it wouldn't hurt to reach a consensus over this practice.
 
If you're required to cite a source multiple times across an article, the Citations policy already explains a way to link to one instance of that citation multiple times, without the need to copy and paste the entire thing each time. However, this is not practical when you need to cite distinct parts of one source to support different claims across an article. For example, you may need to cite different pages from an issue of Nintendo Power on one article. The same issue may arise even when citing different quotes from a singular page of that publication.
 
I consulted a few American style guides over the topic, and found their recommendations quite practical. [[User talk:Mario#Special:Diff/4429551|These were my observations:]]
<blockquote>I looked up some time ago how official American style guides do it and found [https://web.archive.org/web/20221203145608/https://www.studyhood.com/english/mla_style.htm this] <small>(studyhood.com, section "ORDER OF ELEMENTS FOR A BOOK REFERENCE" (2nd))</small> for MLA and [https://libguides.up.edu/chicago/short_form this] <small>(libguides.up.edu)</small> for Chicago Manual of Style. To synthetize what both these guides recommend: the first time a source is cited, list the rigmarole that you normally would (author last name, author first name, publication date, title, publisher etc.); if the document then requires that you cite a different page from the same source, use a shortened form that contains the bare necessities.<br>The two style guides may prioritize different such "bare necessities" for shortform citations. MLA dictates that you should use the author's last name and the relevant page if you source only one work by that author, and additionally list a shortened form of the work's title if you cite multiple works by that author on the same document. Chicago, on the other hand, dictates that you always use the author's last name, title of work (again, a short form!), and page name even if you only cite one work by that author.</blockquote>
 
In my opinion, the ideal approach on this wiki would be to blend these two guidelines as such: '''fully elaborate on the source the first time it is cited, as is typically done. For subsequent references to that source, list a condensed version with only the bare minimum (title, page/section) to set them apart from other sources in the article, including the specific page or section cited. If the source shares a title with another work, consider adding a distinguishing detail in its condensed version, such as the author's last name or date of publication, at your discretion.''' The best justification for this practice is that it helps cut down on redundant information: the reader doesn't need to digest the particulars of a source, such as its authors, ISBN, website, language etc, more than once on a given page. You can view early applications of this standard at [[Stretch_Shroom#References|Stretch Shroom]] and [[Big Penguin#References|Big Penguin]]. The template {{tem|cite}} can be used in this case as with any other citation.
 
I noticed that some users prefer to '''instead fully list the details of that source each time it is referenced'''. This may be beneficial to better identify a source when it isn't referenced in close succession, but in disparate areas of an article. For this reason, the supporting option is divided between these two approaches. The winning option becomes the standard and is included in the wiki's policy for citations.
 
Edit (18:00, February 22, 2025 (EST)): Added another option to '''integrate Wikipedia's "{{wp|Template:Reference page|reference page}}" system''', per {{user|Nintendo101}}'s suggestion in the comments section. In short, you call a source multiple times in the article using the "name" parameter (optionally listing all the pages you wish to cite throughout the article within the citation), and append the page number or section to a desired reference link to that source in superscript. To exemplify with a fictional source:
*one instance<ref name=SMB-guide>Smith, John (1985). ''Super Mario Bros. Official Guide''. ''McPublisher Publishing'' ISBN 0000-0000-0000. Pages 18, 20.</ref><sup>:18</sup>
*another instance<ref name=SMB-guide/><sup>:20</sup>
 
<references/>
 
'''Proposer''': {{User|Koopa con Carne}}<br>
'''Deadline''': March 8, 2025, 23:59 GMT
 
====Option 1: Fully list the details of a source upon its first reference, condense its subsequent references to mostly its title and relevant page/section====
#{{User|Koopa con Carne}} Per proposal.
 
====Option 2: Fully list the details of a source in repeated references====
#{{User|Ahemtoday}} Option 1 seems inconsistent — I'm not a fan of the concept of citing the same source in two different ways within the same article. It'd be jarring when they're next to each other and it'd be difficult to find the missing information when they're far apart. Option 2 has neither of these issues.
 
====Option 3: integrate Wikipedia's "reference page" system====
#{{User|Koopa con Carne}} Per Nintendo101.
#{{User|Nintendo101}} Per my suggestion below.
#{{User|Camwoodstock}} Per Nintendo101; this feels like the best compromise between curbing redundancy, while being more specific on a citation-by-citation basis.
#{{User|Ahemtoday}} This also seems like a reasonable way of doing this.
#{{User|EvieMaybe}} makes sense!
#{{User|Super Mario RPG}} This is a great idea, as it will help refine our citation system.
#{{User|Mario}} [[File:Club Nintendo Classic SMB2 01.png|70px]]  Let's not forget to cite this proposal once it's listed in the policy page.
#{{User|GuntherBayBeee}} Per all.
#{{User|PaperSplash}} No reason to stray from Wikipedia's system IMO if it works.
 
====Don't make a standard====
 
====Comments (citing multiple parts of a single source)====
On Wikipedia, as demonstrated [https://en.wikipedia.org/wiki/Citizen_Kane#Production here], they have a system for articles where you write out a citation once, and can convey the individual page numbers in a superscript next to the spots it is invoked in the article. I have long thought that is a great system and could help reduce redundancies on Super Mario Wiki. Do you think this could be reflected in the proposal? - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 17:33, February 22, 2025 (EST)
:I encountered this system before, but completely forgot about it for some reason. Seems like an excellent system for pages and even {{wp|Template:Reference page#How to use|other non-numeric parts of a source}} that could outshine the other candidates in the proposal. Still, what do you do, for instance, if you want to cite different quotes from the same page of a book? It's a bit of a fringe scenario, which is why I'm not stressing it in the proposal, but it's not far-fetched either. You can't rely on an in-line superscript, that would be unwieldy. {{User:Koopa con Carne/Sig}} 18:00, February 22, 2025 (EST)
::Good question. I think given the general lack of recurrence, It's okay treat them as different citations like normal. My personal preference is to cite more specific details pertaining to a source only once when the book is first cited (like ISBN number, publisher, location, authors), and then omit some of those details the second time (only mention the title and date, to convey it is the same source that was cited earlier). But I know that is tricky for longer articles. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 18:43, February 22, 2025 (EST)
 
===Retool the Names in other languages section into a more general etymology section===
{{Early notice|March 6}}
I've always felt like a subject's name is something we care about a lot in this wiki. However, the way we choose to cover that aspect of each subject could be improved tons. Information about each subject's name (or names) is scattered all over the article, with the English etymology often being at the top of the page, and the names in other languages at the bottom, and information about the various names a subject has gone by lost in History.
 
Some subjects ([[Taily]], for example) have an "Additional names" section, putting its internal and foreign names in one section. I say, why not take a page out of our fellow NIWA members, namely {{iw|pikipedia|Pikmin_family#Naming|Pikipedia}}, {{iw|inkipedia|Inkling#Etymology|Inkipedia}} and {{iw|bulbapedia|Bulbasaur_(Pokémon)#Name_origin|Bulbapedia}}, and push this a step further?


This is a ludicrous idea for many reasons:
This new section (called "Names", "Naming", "Etymology", whatever works best) would contain, in roughly this order:
*The etymology of each English name the subject has gone by, including explaining puns and cultural references
*The history of the subject's name/s (what was the first game to call [[Blooper]] by its modern name, and what was the last game to call it Bloober?)
*Miscellaneous name-related notes (like how half of [[Mario & Luigi: Brothership|''Brothership'']]'s translations give the Great Lighthouse bosses a common suffix)
*Internal name table, if applicable
*The "names in other languages" table


1; The Mariowiki isn't a purchaseable/licensed software. It's not even a software. There's no legal basis for tying the right to edit the wiki to a contract.
'''EDIT:''' If a subject doesn't have anything about its name to talk about (such as a generically-named subject like [[bubble]] or a literal name like [[Mayor Penguin]]), the section can be titled simply "Names in other languages" as we've been doing. This is to avoid non-sentences like Bulbapedia's "Iron Valiant is literally ''iron valiant''." name explanations.


2: An additional screen of legaleses isn't going to keep out dedicated trolls.
'''Proposer''': {{User|EvieMaybe}}<br>
'''Deadline''': March 13, 2025, 23:59 GMT


3: We already have [http://www.mariowiki.com/Category:MarioWiki_Policy multiple pages] detailling what we expect of user behaviours and editing competence.
====Retool====
#{{User|EvieMaybe}} Per proposal.
#{{User|Technetium}} Per proposal. I find explaining English names in opening paragraphs breaks the flow sometimes.
#{{User|Waluigi Time}} Solid idea, it's not very easy to figure this out since name changes are scattered around history sections which aren't sorted chronologically.
#{{User|Camwoodstock}} Honestly, putting the name explanation in the names in other languages section is maybe the one good thing about Bulbapedia's naming section <small>(we will never not find their arbitrary skepticism extremely strange, such as the gem of "Toucannon may be a combination of toucan and cannon.")</small>, so we'd be fine to borrow that. Helps keep things organized and improves the flow of the section.
#{{User|Fakename123}} Per proposal.
#{{User|Ahemtoday}} I'm in favor of consolidating this information. As for the resultant section's name — I'm pretty fond of how the Zelda wiki calls these sections "Nomenclature". That's a great word for it.
#{{User|PopitTart}} As a frequent Pikipedia editor, Yes all. Names are shockingly poorly documented despite their significance to wiki classification.
#{{User|Pseudo}} Makes sense to me!
#{{User|Nintendo101}} I like this idea.
#{{User|Power Flotzo}} Never really liked how English name info is just haphazardly slapped on to some articles. Per everyone.
#{{User|Super Mario RPG}} Better organization of naming info. Can we [[Template_talk:Foreign_names#Retitle|retitle]] the "foreign names" template while we're at it?
#{{User|Mushroom Head}} Per ałł.
#{{User|Sparks}} Per all.
#{{User|Mario}} Hm.
#{{User|PaperSplash}} Per all. I'm personally partial to how {{iw|fireemblem|Fire Emblem (concept)#Etymology and other languages|Fire Emblem Wiki}} labels them collectively though. "Etymology ''and'' other languages".
#{{User|Bro Hammer}} Per proposal.


4: Even if we had a legal basis for requiring a contract and that it was somehow a viable deterent, there's no viable way we could enforce it in case of violation. None of us are paid, for pete's sake.
====Do not retool (status quo)====


5: ''Even'' if we could somehow enforce it, taking people to the court would be a ludicrous waste of time, $$$ and effort.
====Comments in other languages====
I've actually been thinking of maybe swapping the order of names in other languages and internal names. The idea was that internal names predate final names, but in practice, many internal names listed come from a subject's subsequent appearances. [[User:LinkTheLefty|LinkTheLefty]] ([[User talk:LinkTheLefty|talk]]) 07:27, February 28, 2025 (EST)
:considering most internal names are either English (which would be explained right above the NIOL box) or Japanese (which would be the first name in the NIOL box), i feel like keeping it between them makes the most sense. {{User:EvieMaybe/sig}} 13:29, February 28, 2025 (EST)
::So we're keeping English ones separate from the Niol section? I can get behind that. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 17:03, February 28, 2025 (EST)
:::yeah, the idea is to have it kinda like Inkipedia. of course it could be executed differently, but i think it's the best alternative {{User:EvieMaybe/sig}} 20:33, February 28, 2025 (EST)
::::I have no experience with Inkipedia or Splatoon in general, so that comparison means nothing to me, sorry. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 09:22, March 1, 2025 (EST)
:::::...an example is literally linked in the proposal body... {{User:EvieMaybe/sig}} 13:21, March 1, 2025 (EST)
::::::I just get a weird pop-up when I try to follow it. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 14:35, March 1, 2025 (EST)
:::::::What is it you see? - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 11:45, March 3, 2025 (EST)
::::::::It's talking about browser cookies. If I see that sort of message on a site that doesn't have to do with something vital, I go back, because I don't think something like a wiki has any business processing browser cookies. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 15:13, March 4, 2025 (EST)


teel-deer: lol. --[[User:Glowsquid|Glowsquid]] ([[User talk:Glowsquid|talk]]) 10:48, 16 July 2014 (EDT)
Regarding the overall name, I think "Naming" and similar words are the best. "Nomenclature" sounds a bit too.... try-hard IMO. Like, I know we want wording to be encyclopedic, but my own subjective opinion on that word is that it comes off as outright stuffy, going from "encyclopedic" to "distractingly looking like writing from the 18th century." "Etymology" is a fine word, but it refers exclusively to the origins of meaning, not just listing them all out. [[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) 17:03, February 28, 2025 (EST)
:I know that but a lot of users just are way too goddamn lazy to even read the damn rules for crying out loud so the EULA actually acts there for convenience and it is not pointless. Hell,even Facebook and Twitter have EULAs so that users know the rules right upon sign up. The Windows NT 4.0 EULA is therefore to show how it doesn't let you hit F8 to install Windows until you read the entire whole damn thing.You get the idea right. I mean it could be a quick reference just before a user creates an account and it is just to check if a user is sincere or not. Do you get what I am trying say. I mean we could just modify the wording so that it would fit our style of writing and since we're not a company hey it will list all the rules and everything that the guideline pages talk about and sorry if you are misinterpreting things. I find the EULA system to be potential for new users when they join immediately so that they don't shoot their foot off.      {{User|Pwwnd123}}
::You can't force people to read stuff, and they're far less likely to read a big wall of legal crap than our rule pages: they'll just hit the button automatically, or they'll give up and just edit anonymously. Either way, you're not stopping the vandals, just dissuading potentially productive users, which actually makes it ''worse'' than useless. - {{User|Walkazo}}
::: It won't be a big wall of legal shit just like the Windows NT 4.0 EULA. It will be a big wall containing all rules of the Wiki. It won't contain legal crap except for mentions of Nintendo's name and all that shit. It will make the user more productive in my point of view than a spammer or a vandal.Considering that this is my proposal,I have a right to change it and did this change your mind. {{User|Pwwnd123}}
You're missing something here. '''There's nothing forcing people to follow it.''' Whether it's pages of legal crap or just explaining the rules, people are far more likely to just mash the "next page" button than read a word of it. And, let's be serious now-HOW IS EXPLAINING THE RULES GOING TO DETER SPAMMERS AND VANDALS? A two-year-old could figure out that replacing a page with the word "poo" isn't allowed. How is "forcing" them to read it going to deter someone from doing something they'd do in the first place? Writing this would just be a huge waste of everyone's time.--[[User:Vommack|Vommack]] ([[User talk:Vommack|talk]]) 18:13, 16 July 2014 (EDT)
:Yeah, people will still just skip it or give up, regardless of what it is that's being thrown in their face. Rules are better divided up into manageable chunks with specific focuses so that people can look things up when they're unsure about something or are referred there or whatever: the longer the page, the faster the eyes glass over, in my experience. My mind is unchanged. - {{User|Walkazo}}


Why are all my proposals end up failing on me even if think of a decent idea that could be implemented on this wiki?? Why do people even hate this idea,I mean Facebook and Twitter has it too? I think it would be a good idea. The way the EULA would deter vandals and spammers is that it would give them second thoughts about if they really want to join this wiki to really be part of it or just be a one year old who would steer up trouble on the wiki and waste their time here by shooting their foot. For goodness sake,does anyone get what I am trying to say? {{User|Pwwnd123}}
Will this proposal also affect media (such as the titles for ''[[The Super Mario Bros. Super Show!]]'' episodes), or just the subjects within the media? [[User:Apikachu68|Apikachu68]] ([[User talk:Apikachu68|talk]]) 19:57, March 3, 2025 (EST)
:I must ask you, yet again: What would force them to read it? Sure, other sites do it. I'm sure you faithfully read every last word in every EULA from every site you've registered on? Besides that, "other sites do it" doesn't support any argument, as it applies to nearly anything. The bottom line is, if someone signs up for the explicit purpose of vandalizing, throwing a wall of words at them won't change it.--[[User:Vommack|Vommack]] ([[User talk:Vommack|talk]]) 18:32, 16 July 2014 (EDT)
:i don't see why it wouldn't! media also has names and etymology, after all. {{User:EvieMaybe/sig}} 09:54, March 4, 2025 (EST)
::A trigger similar to Windows NT 4.0 and Windows NT 3.XX would make that the incentives to force them to read it. But what I am trying to say is that what if a normal person and not some dumbass who has nothing better to do than to spoil all our hard work joins then at least the EULA will help out in guiding the user when they create their account. I do feel a strong sense of justice within me. {{User|Pwwnd123}}
:::You're still missing something...There's nothing stopping any user from just mashing the trigger.--[[User:Vommack|Vommack]] ([[User talk:Vommack|talk]]) 18:52, 16 July 2014 (EDT)
I get what you're saying Pwwnd, but there's very little chance someone who comes to destroy our hard work would change their mind because of a bunch of rules they see when getting an account. --{{User:Koopakoolklub/sig}} 19:06, 16 July 2014 (EDT)
:If anything, it's going to make users not join. I know I probably wouldn't if all I saw was that, because it's like saying something bad will ban you because you were on a list. Some younger users might be scared of signing something like that because there parents wouldn't want them to. - {{User:Ninelevendo/sig}} 01:29, 17 July 2014 (EDT)
:: But what if in the future someone decided to change their mind then it will have to be there. I do think thrice about it. Besides I see more potential in a EULA system and it feels beneficial for the Wiki itself. {{User|Pwwnd123}}
:::We do all get what you're saying. We all just have better reasons why not to do it. Like I said in a different proposal, voting against one doesn't mean the voter hates it. Anyway, like everyone else said, there's no real way we can confirm that the new user has read everything. Like I said in my vote, they may not even read it. There's no real way past that. {{User:'Shroom64/sig}}
::::The problem with what your proposing is that the very purpose of wiki sites like this is that anyone can edit it. It's supposed to be a free site, and vandals aren't '''that''' big of a problem anyway. Seriously, we can just undo their edits with a click and that's that. And they get blocked nearly immediately. It's not like this site is in jeopardy because of some SNEAKY SCHEMING vandals found a secret, convoluted way to vandalize an open-door, universally editable wiki with some jibberish that gets reverted within a click away and a few seconds. Again as I said, the best way to counter vandals is to undo their edits and quietly report their activities to an administrator. If we're THAT sophisticated or desparate, we could even implement an anti-vandal bot (but that ain't happenin as far as I'm concerned) {{User:Baby Luigi/sig}} 21:17, 17 July 2014 (EDT)
:::::Honestly, though, we need someone or something to handle blocking or reverting during my 5-8pm hours, because literally no-one but me, Mario Jc and a couple other regulars are there and we have to wait hours until someone else comes online. I'm not trying to say "Promote me!", if anything I think that that's a bad idea, but a bot would help at these times. - {{User:Ninelevendo/sig}} 01:36, 18 July 2014 (EDT)
::::::Admins are online whenever we are online, we can't be online at every single hour of every single day. It may be annoying, but it's something that you'll have to deal with until one comes online. {{User|Yoshi876}}


So,technically 90% of the time people don't give a damn about EULAs because they are obsolete and lengthy. I mean Paypal had the biggest EULA ever.So you guys mean only 10% of the people would give 10 shits about EULAs. Hell, Windows NT 4.0,3.5X and 3.1 makes you read the entire damn EULA but Windows 2000 and XP allow you to hit F8 right away so you don't have to go through all that bullshit again and make it unimportant because we want to install the goddamn OS.So an EULA is a waste of time for us, I mean Microsoft and Apple and other free commercial software manufacturers are wasting their goddamn time with a EULA that no one cares about. I mean GNU software do have EULAs as well. {{User|Pwwnd123}}
===Introducing the crossover article===
:I'm pretty sure Apple and Microsoft have more reasoning than keeping away vandals. - {{User:Ninelevendo/sig}} 01:53, 18 July 2014 (EDT)
The passing of this proposal would accomplish seven things:
::The EULA is there because it's for legal purposes entirely. So just in case someone sues them or something, the EULA is basically a "terms of service" thing like a contract that you agree to use and can be used against cases in court. {{User:Baby Luigi/sig}} 22:25, 18 July 2014 (EDT)
#'''See the publication of the drafted ''Zelda'' article''' discussed in this proposal, titled "{{Fake link|crossovers with ''The Legend of Zelda''}}." (The draft can be viewed [[User:Nintendo101/community garden|here]].)
:::::::'''Re: Bots:''' We're ''not'' giving blocking powers to a bot, and making one to revert things also seems dubious security-wise, and either way , it'd be too much trouble to make considering that anyone can undo things manually. As others have said, vandals are not worth the worry. - {{User|Walkazo}}
#'''Funnel redirects and disambiguation pages pertaining to ''Zelda'' on the wiki to the published ''Zelda'' article''' (i.e., searches for The Legend of Zelda, Octoroks, etc. Fully covered crossover subjects like [[Link]] would keep their articles, and this would not preclude a crossover subject from receiving an article of their own in the future if warranted, such as the inclusion of Princess Zelda in a future ''Mario Tennis'' or something like that).
<br>@Pwwnd123: I see your point about GNU and those other sorftwares having EULAs, but I agree with Baby Luigi and Ninelevendo, and as stated earlier, this wiki isn't software, we're a wiki that anyone can sign up and start editing on. We have ways to deal with vandalism already, we don't need something others have to read through upon login. The Welcome template has links to those pages that make the rules clear, like the [[:Category:MarioWiki Policy|MarioWiki Policy category]]. Do we really need to add a EULA on top of that? {{User:'Shroom64/sig}}
#'''Move details pertaining to ''Zelda'' from list articles on the site to this one''' (i.e. all information pertaining to Sheik on the [[List of fighters debuting in Super Smash Bros. Melee|list of fighters debuting in ''Super Smash Bros. Melee'']] article would be cleared, and searching for "Sheik" on the site would bring you to this article. ''Zelda'' info on the [[list of references in Nintendo video games]] article would similarly be cleared. Visitors to that article would be directed towards the published ''Zelda'' one when they reach that section of the list article).
:But the only problem is that the Welcome template only is given when a user makes his or her first edit. What if they immediately made their first vandalized edit. Then a EULA becomes important. That is the only disadvantage of the Welcome template. A EULA works out much better in my opinion. We'll still be a free to edit wiki even with a EULA. I mean sites like Facebook and Twitter have EULAs and shit like that. {{User|Pwwnd123}}
#'''Establish a navbox for crossover articles''' (either a wholly dedicated one, an incorporation into "Template:Culture," or a retooling of "Template:Crossover characters").
===Create a NEC and PC-88 Page===
#'''Establish the precedent where this can be done for other IPs with which the ''Super Mario'' franchise has crossed-over.'''
You know how we have a page about Philips and the Philips CD-i. I think we can do the same with NEC and their PC-88 home computer. The NEC PC-88 did had 3 Mario games released for it so we can create an article for it. For the NEC article we can go into a brief history of the company and then go into the Nintendo and Hudson Soft's perspective only just like with the Philips article. For the PC-88 page we can do a similar thing like the CD-i page and go over the system's history in brief and and talk about the three Mario games on this home computer.
#'''Establish a 'Crossover article" section to the [[MarioWiki:Manual of Style]]''' that explains the framework for crossover articles described below. This is to be the standard structure for how other articles are to be structured.
We can try to abide by the wiki's manual of style and be trying to keep it relevant as possible.
#'''Note that this framework exists on the the [[MarioWiki:Coverage#Crossovers|crossover section of our coverage policy]]''', and provide a link directing readers to it.
Also,NEC did also did help by producing some of the chips Nintendo uses in their consoles such as the GameCube and Wii.


'''Proposer''': {{User|Pwwnd123}}<br>
The ''Super Mario'' franchise is very much the IP tentpole for Nintendo Co., Ltd. and at least one of the ones for the Japanese video game industry as a whole. Consequently, ''Super Mario'' as a franchise and brand has crossed-over with many other franchises, brands, and series over its nearly fifty years of existence - not only sister series developed by Nintendo EAD and R&D, and their successor EPD (i.e. ''Duck Hunt'', ''Punch-Out!!'', ''Exictebike'', ''Metroid'', ''F-ZERO'', ''Animal Crossing'', ''Pikmin'', ''Splatoon'', etc.) and those of their external creative partners (i.e. Ape Inc.'s ''EarthBound'', HAL Laboratory's ''Kirby'', Game Freak's ''Pokémon'', etc.), but also fellow ones from other studios like Square Enix, Sega, Bandai Namco, Koei Tecmo, Chunsoft, Ubisoft, Konami, and Hudson Soft. This is not groundbreaking news: Most folks interested in gaming history already know this, especially the curators of the Super Mario Wiki. However, I do not feel like we handle this information particularly well on the site.
'''Deadline''': July 24,2014 23:59 GMT


====Create an article for both the parent company NEC and the PC-88====
A lot of coverage of ''Super Mario'' references, homages, allusions, and cameos are nestled within various list articles, inexplicitly at the end of [[Super Mario Bros.#Notes|dedicated game articles]], or in ''Super Smash Bros.'' articles with which there seemed to have been effort to bury on the site and [[List of fighters debuting in Super Smash Bros.#Captain Falcon|are not wholly about ''Super Smash Bros.'' anyways]]. This coverage, exasperated by recent efforts to reduce coverage on the ''Super Smash Bros.'' series: (1.) obfuscates the fact that ''Super Mario'' has made references and ''is'' referenced in many other franchises outside of ''Smash Bros.'' contexts, often in very meaningful ways that are interesting and fun to read about; (2.) mitigates how ''Mario'' has been an influence behind some of these other franchises; and (3.) makes finding some bits of information just very difficult. If I, as a visitor of the site, wanted to understand scenarios where ''Splatoon'' and ''Mario'' have crossed-over, I would not have an easy way to find that all in one place, and I think that is a shame.
#{{User|Pwwnd123}} Per my proposal.


====Create an article for the PC 88 only====
[[File:LA Wart.gif|right|200px|frog man!]]
#{{User|Koopakoolklub}} Per proposal. Just this is enough, there isn't much Mario related things for NEC.
[[File:SM3DW WS-1 2nd Green Star.jpg|right|200px|green lad!]]
#{{User|'Shroom64}} Per Triple-K.
To better cover and consolidate crossover info on the site, and I have been drafting what I would like to call a "<u>crossover article</u>" using [[User:Nintendo101/community garden|''The Legend of Zelda'' franchise as an example]] (with contributions from Salmancer, DryBonesBandit, Memelord2020, RHG1951, LeftyGreenMario, and LadySophie17, and feedback from Super Mario RPG, Doc von Schmeltwick, and Koopa con Carne). This is a long article, and it is not wholly completed yet, but I think it is serviceable example of what I would like us to do going forward. Crossover articles take inspiration from the {{iw|smashwiki|Mario (universe)|universe articles}} from our affiliate Smash Wiki and, as apparent in the ''Zelda'' draft, consist of the following sections:
*'''Overview''' : A brief description of what the crossover franchise/series is for those not well versed in the subject and would like to know a little more about it without visiting another site, and how this relates to ''Mario''. It is the create a foundation so the reader is not confused by descriptions or terminology in the other areas of the article. For ''Zelda'', this section may be a bit lengthier than it would be for others because ''Mario'' had a lot of direct influence on ''Zelda'' as a series.
*'''Recurring crossover subjects''': for subjects like characters, enemies, bosses, or items that make substantial appearances in or alongside ''Mario''-related media, such as subjects that used to have their own articles on the site. Each subject would be briefly explained so readers understand who they are when mentioned in other parts of the article, have explicit conceptual or design connections with ''Mario'' highlighted, and summarize areas where they specifically crossover with ''Mario''.
*'''History in the ''Super Mario'' franchise''': a history section for where the crossover subject is referenced in the ''Super Mario'' franchise itself.
*'''History in the subject series/franchise''': a history section for the inverse, where ''Super Mario'' is referenced in the franchise subject of the article. In this case, it is ''Zelda''.
*'''Shared history''' (if applicable): a history section for mutual space where both subjects appear, such as the ''Super Smash Bros.'' series, ''Tetris'' series, ''NES Remix'' series, or other media.


====Do Nothing====
''Zelda'' is uniquely related to ''Mario'' and nearly as old, but crossover articles can be written for smaller franchises/series as well. The only requirement for a series/franchise to receive an article of its own is for it to directly crossover with ''Super Mario'' within an officially licensed capacity. Articles of this nature should not be written for series/franchise that simply make homages to ''Super Mario'' or have elements inspired by it, such as ''Celeste'', ''Gears of War'', or ''Astro Bot''.
#{{User|Ghost Jam}} Per standard procedure. You don't need community consensus to create an article for a standard topic. Generally, you'd bring articles here when either a consensus can't be reached or a more drastic measure is being suggested. These are standard topic articles that I agree we've been missing. Go make them both, with my blessings, and we'll go from there.


====Comments====
I offer three options:
#'''Support: I like the idea of crossover articles and want to see them implemented as described.'''
#'''Support: I like the idea of crossover articles, but list articles for the ''Super Smash Bros.'' series should be left alone.'''
#'''Oppose: I do not like the idea of the crossover article and do not want to see them implemented.'''
 
I know this was a long one, folks. Sorry about that, but the ideas behind this idea are multifaceted. Please let me know if you need additional clarity on anything or if you have any recommended amendments. (Also, if you would like, I welcome you to contribute to the drafted ''Zelda'' article! It is in my "<u>community</u> garden" sandbox for a reason.)
 
'''Proposer''': {{User|Nintendo101}}<br>
'''Deadline''': March 17, 2025, 23:59 GMT
 
====Support: let's implement crossover articles!====
#{{User|Nintendo101}} [[File:Link pose SMM.png]]
#{{User|Super Mario RPG}} Per proposer.
#{{User|Koopa con Carne}} Per proposal with absolutely no second thought. Aside from the obvious value such articles would bring, this practice may incidentally just be the silver bullet for the community's differences on how to cover Smash Bros. content. Nintendo101, even with your inspiration from SmashWiki, I'd say you still managed to think out of the box here.
#{{User|Waluigi Time}} Per all.
#{{User|EvieMaybe}} been waiting a long time for this one. per proposal!
#{{User|LadySophie17}} Secondary choice, I suppose. Better than no article.
#{{User|Camwoodstock}} Secondary option; we'd rather these articles exist, even if the Smash coverage is confusing, than these articles not exist at all.
#{{User|PopitTart}} It has always felt absurd to me that [[Captain Olimar]]'s presence on the wiki is entirely an entry in [[List of fighters debuting in Super Smash Bros. Brawl]], despite being directly based on Mario himself and having appearances in ''Luigi's Mansion'', ''WarioWare: D.I.Y.'', ''Super Mario Maker'', ''Yoshi's Woolly World'', ''Mario Kart 8'', and ''WarioWare Move It!''
 
====Support: let's implement crossover articles, but leave ''Smash Bros.'' lists alone====
#{{User|LadySophie17}} Per proposal. I believe the articles would be better focused on the relationship between their respective series and Mario. Detailing all their character's Smash histories (which could get quite lengthy with something like Pokémon) would be better left in the List articles they currently are in.
#{{User|Sparks}} Per Sophie.
#[[User:Doc von Schmeltwick|Doc von Schmeltwick]] ([[User talk:Doc von Schmeltwick|talk]]) - Per Soph
#{{User|Camwoodstock}} Primary option; per Sophie, we worry about the length of some Smash sections, and we feel the organization is fine enough as it is right now for Smash-related subjects.
#{{User|Tails777}} Per Sophie. I fully agree with making crossover articles to cover the relations another franchise has with Mario, but Smash in of itself is also a crossover and covering the details of these characters in a place that relates to Smash feels better.
 
====Oppose: let's not implement crossover articles====
 
====Crossover comments====
I also happened to start a [[User:PopitTart/Sandbox#Pikmin (franchise)|draft for a Pikmin series article]] the other day, inspired by Nintendo101's Zelda draft. It's in a much... '''much''' rougher state, but I hope it gives an idea what these crossover articles can provide.--[[User:PopitTart|PopitTart]] ([[User talk:PopitTart|talk]]) 19:31, March 3, 2025 (EST)
 
{{@|Koopa con Carne}} thank you for the kind words! - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 20:30, March 3, 2025 (EST)
:[[File:LinkCN.jpg|50px]] {{User:Koopa con Carne/Sig}} 11:32, March 4, 2025 (EST)
 
Question: One of the proposed points is to "''Move'' details pertaining to Zelda from list articles on the site to this one", but the i.e. states that "all information pertaining to Sheik on the list of fighters debuting in Super Smash Bros. Melee article would be ''cleared''". Characters on these fighter lists have extensive history sections; will these be moved to the crossover pages as well, or will these be nixed altogether?<br>Also, what about franchises which currently only have a connection with Mario through ''Smash Bros.'', such as ARMS? Will these get a crossover article as well or not? {{User:Arend/sig}} 12:10, March 4, 2025 (EST)
:I don't know. Perhaps we'll cross that bridge when we get there. Ultimately, very few of the franchises within ''Smash Bros.'' have only crossed-over with ''Mario'' within ''Smash Bros.'', and that was at the front of my mind for this proposal. ''ARMS'' is one of the few exceptions. I should probably make some sort of list to parse what other series and franchises are within that boat. But what would you want to see, {{@|Arend}}? - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 15:52, March 4, 2025 (EST)
 
So is the ultimate plan for these to effectively be a replacement for the Smash list pages? I imagine the lists would start looking a bit barren if things on them get moved to crossover franchise articles. {{User:Hewer/sig}} 16:07, March 4, 2025 (EST)
:I am admittedly not a fan of the fighter list articles on the wiki and I think the information on them would be better served in articles more directly focused on the ''Super Mario'' franchise, both for readers and editors. However, I respect the will of those who would rather we keep those articles around. I am not sure if you looked at my ''Zelda'' draft, but it does omit more granular information specific to the ''Super Smash Bros.'' series, like stickers, trophies, Classic Mode routes, special moves, or NIOLs for individual characters. I would rather this article emphasize how ''Zelda'' engages with ''Mario'' in other contexts. If folks would rather Super Mario Wiki continue to hold onto the more granular ''Smash Bros.'' info on the fighter list articles, they could be retained for those purposes, I imagine. - [[User:Nintendo101|Nintendo101]] ([[User talk:Nintendo101|talk]]) 16:47, March 4, 2025 (EST)
::Well, there are two voting options for people who want both. [[User:Super Mario RPG|Super Mario RPG]] ([[User talk:Super Mario RPG|talk]]) 16:52, March 4, 2025 (EST)
 
===Color-code game, series and franchise infoboxes to match their navigation template colors===
 
The color coding used in navigation templates could be used for more cases outside navigation templates. Since the wiki covers all the distinct branches of the ''Mario'' franchise (which are numerous), using those theme colors more often to sectionalize and identify them may make things easier to navigate through in some cases. While I don't think there are cases where this would have a high impact right now, we could apply them to the game, series and franchise infoboxes, where they are fitting.
 
As it currently stands, the light red color of the game infobox specifically implies "Mario" to me at least, while the purple color of the series and franchise templates I suppose is arbitrary. This change would make it possibly more intuitive from a glance at the top of the article to which ''Mario'' branch the article belongs. It would also establish a common element to the introduction of articles belonging to the same set, while also establishing a color consistency between the very top and the very bottom of the article.
 
As for the colors themselves, I imagine something like:
 
*'''infobox background:''' the navigation template's lighter background (e.g. {{color|#000|bg=#FFF5EE|#FFF5EE}} for ''Mario'');
*'''darker cell background:''' the navigation template's darker background color (e.g. {{color|#000|bg=bisque|bisque}} for ''Mario'');
*'''header:''' the navigation template's header color (e.g. {{color|#fff|bg=#CC0000|#CC0000}} for miscellaneous ''Mario'', {{color|#fff|bg=#FF2400|#FF2400}} for ''Super Mario'');
*'''border:''' {{color|#000|bg=#aac|#aac}}, {{color|#000|bg=#aca|#aca}}, {{color|#000|bg=#acc|#acc}}, {{color|#000|bg=#caa|#caa}}, {{color|#000|bg=#cac|#cac}} or {{color|#000|bg=#cca|#cca}}, depending on the most closely matching color.
 
'''Proposer''': {{User|Bro Hammer}}<br>
'''Deadline''': March 17, 2025, 23:59 GMT
 
====Support: implement color coding for game, series and franchise infoboxes====
#{{User|Bro Hammer}}: Per my proposal
#{{User|Super Mario RPG}}: Per proposer.


==Removals==
====Oppose: do not implement color coding for game, series and franchise infoboxes====
''None at the moment.''
#{{User|Nintendo101}} I honestly prefer keeping infoboxes color coordinated to what type of the subject the article is about. It is intuitive and helpful. I feel like allowing too many colors for this infobox would only dilute that structure across the board. I would support some sort of quick way to jump between entries in the same series at the bottom of the infobox, similar to our level and world infoboxes, but I'd rather all game articles share the same colored infobox.
#{{User|EvieMaybe}} per Nintendo101
#{{User|Technetium}} Per Nintendo101.
#{{User|Hewer}} Per, and I also already find the navbox colours for most series to be quite random and arbitrary.
#{{User|Rykitu}} Per Nintendo101 and Hewer.


==Changes==
====Comments====
''None at the moment.''


==Miscellaneous==
==Miscellaneous==
''None at the moment.''
''None at the moment.''

Latest revision as of 16:52, March 4, 2025

Image used as a banner for the Proposals page
Current time:
Tuesday, March 4th, 21:52 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. Proposals can be created by one user or co-authored by two users.
  2. Anyone is free to comment on proposals (provided that the page's protection level allows them to edit).
  3. 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.
  4. Users may vote for more than one option, but they may not vote for every option available.
  5. 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.
  6. 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.
  7. 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.
  8. Proposals cannot contradict an already ongoing proposal or overturn the decision of a previous proposal that concluded less than four weeks (28 days) ago.
  9. 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.
  10. 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.
  11. If a proposal reaches its deadline and there is a tie for first place, then the proposal is extended for another week.
  12. 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.
  13. 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.
  14. 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.
  15. After a proposal passes, it is added to the appropriate list of "unimplemented proposals" below and is removed once it has been sufficiently implemented.
  16. 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.
  17. 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.
  18. 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.
  19. Proposals cannot be made about promotions and demotions. Staff changes are discussed internally and handled by the bureaucrats.
  20. No joke proposals. Proposals are serious wiki matters and should be handled professionally. Joke proposals will be deleted on sight.
  21. Proposals must have a status quo option (e.g. Oppose, Do nothing) unless the status quo itself violates policy.

Basic proposal formatting

Copy and paste the formatting below to get started; your username and the proposal deadline will automatically be substituted when you save the page. Update the bracketed variables with actual information, and 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}}}} Per 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."

Poll proposal formatting

As an alternative to the basic proposal format, users may choose to create a poll proposal when one larger issue can be broken down into multiple sub-issues that can be resolved independently of each other. In a poll proposal, each option is its own mini-proposal with a deadline and Support/Oppose subheadings. The rules above apply to each option as if it were a its own two-option proposal: users may vote Support or Oppose on any number of options they wish, and individual options may close early or be extended separately from the rest. If an option fails to achieve quorum or reach a consensus after three extensions, then the status quo wins for that option by default. A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done.

To create a poll proposal, copy and paste the formatting below to get started; your username and the option deadlines will automatically be substituted when you save the page. Update the bracketed variables with actual information, and 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]". 

===[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}}}}

====[option title (e.g. Option 1)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

====[option title (e.g. Option 2)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

====[option title (e.g. Option 3)]: [brief summary of option]====
'''Deadline''': {{subst:#time:F j, Y|+2 weeks}}, 23:59 GMT

;Support
#{{User|{{subst:REVISIONUSER}}}} Per proposal.

;Oppose

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

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 heading, 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 {{ongoing TPP}}. 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 and Super Mario Run.
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)
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)
Organize "List of implied" articles, EvieMaybe (ended January 12, 2025)
Split Mario & Luigi badges and remaining accessories, Camwoodstock (ended February 1, 2025)
Merge Chef Torte and Apprentice (Torte), Camwoodstock (ended February 3, 2025)
Merge the Ancient Beanbean Civilizations to List of implied species, Camwoodstock (ended February 13, 2025)
Make about templates on New Super Mario Bros. U courses and New Super Luigi U courses link to each other instead of a disambiguation page, but keep the disambiguation page, Salmancer (ended February 21, 2025)
Merge intro/outro sections, rename Gameplay section to "Overview" for Mario Party minigame articles, ToxBoxity64 (ended March 1, 2025)

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)
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)
Merge Wiggler Family to Dimble Wood, Camwoodstock (ended January 11, 2025)
Split the Ink Bomb, Camwoodstock (ended January 12, 2025)
Create a catch-all Poltergust article, Blinker (ended January 21, 2025)
Merge Dangan Mario to Invincible Mario, PrincessPeachFan (ended January 30, 2025)
Give the Cluck-A-Pop Prizes articles, Camwoodstock (ended January 31, 2025)
Reverse the proposal to trim White Shy Guy, Waluigi Time (ended February 8, 2025)
Split Animal Crossing (game), Kaptain Skurvy (ended February 12, 2025)
Split the modes in the Battles page, Mario (ended February 15, 2025)
Tighten Category:Power-ups and its subcategories, SolemnStormcloud (ended February 27, 2025)

Writing guidelines

None at the moment.

New features

Establish a format for poll proposals on the archive lists

Something that's slipped through the cracks when we invented poll proposals was what we do when we add them to these pages. We can't simply have one link to the poll proposal — the entire purpose of the format is that different parts of it can pass and fail independently of one another. What color do we put a proposal where one thing fails and another thing succeeds in?

I have several pitches for you.

OPTION ZERO
Do nothing. I'm putting this at the front because I want to leave room for any good-sounding solutions beyond the four I'm about to suggest. It's here on the proposal at all because I'm pretty sure I'm legally obligated to put it here, but I'll be honest — I'm not entirely sure what this winning would... mean. Our hand will eventually be forced when our first poll proposal fully resolves, so a format will be established one way or the other.

OPTION ONE
The different issues of a poll proposal share a number corresponding to when the first issue closes. They're listed separately, and distinguished from each other via letters. As an example, the three parts of the Brown Yoshi proposal would slot in at #83A, #83B, and #83C. (That would shove some other proposals down; we could also just append them to the end of the list like normal and brush off the inconsistency if y'all prefer.)

The Brown Yoshi proposal is also a handy demonstration of an edge case we have to contend with — if this proposal passed right now, we would list #83A as red and #83B as gray, but what would happen with #83C, which is still ongoing? This is the aspect on which Options One and Two differ. In Option One, issues are not added to the archive page until they close. The page would only contain #83A and #83B if the proposal passed right now, with #83C being added later

I would like to note that the Brown Yoshi proposal is a remarkably well-behaved example. If the issues were ordered differently, we may at one point have #83A and #83C on the list with no #83B until later.

OPTION TWO
Option Two is identical to Option One except in how it handles open issues on partially closed poll proposals. In this option, they are added to the list alongside the other issues, and marked with a new color — let's say black.

This prevents the awkward gaps we would be susceptible to in Option One, but it is introducing a whole color for a temporary edge case.

OPTION THREE
Option Three is simpler. We create a new color in the archive for poll proposals — I guess let's say black again. Poll proposals get added to the archive when all issues on them are closed.

This saves space (the other options will have to give fourteen entries to this proposal, but it means the entry on the list doesn't reflect anything about any individual issue's status, such as whether it's been implemented or not.

EDIT: Camwoodstock's pitch below of using three colors (and, implicitly, adding the poll proposal to the archive when it has any closed issues) doesn't entirely eliminate that negative, but it does seem much more useful than just having the one color.

OPTION FOUR
Option Four is simpler still. Each issue is treated as if it were an entirely separate proposal. Each gets numbered and appended to the list when it closes regardless of what anything else in the poll proposal is up to.

The negative of this way of doing it is that the issues of a poll proposal may end up strewn about the list in a way that doesn't really reflect that they're a related thing.

Proposer: Ahemtoday (talk)
Deadline: March 18, 2025, 23:59 GMT

Option Zero

Option One

  1. Ahemtoday (talk) It's either this or Option Two for me — it's important to me that the issues end up next to each other on the archive and that the status of each one is visible on the page.

Option Two

  1. Ahemtoday (talk) See my note about Option One.
  2. Camwoodstock (talk) Secondary option, but we do think darker shades of the colors (a-la our pitch for Option Three) would be nice. Helps distinguish at a glance what was a poll proposal.

Option Three

  1. Camwoodstock (talk) We would like to pitch a more sophisticated variant of this; 3 new colors. One for a poll that has concluded, one for a poll that is partially concluded, partially ongoing, and one for a poll that has been partially overturned by a future proposal. Maybe dark green, dark gray, and a dark yellow? The darker colors, of course, to contrast with the non-poll proposals.

Option Four

Comments

@Camwoodstock — I definitely think your pitch for Option Three is better than the version I was suggesting. I'm not really sure about the pitch for Option Two, though — the letters already distinguish them, and I feel like they'd seem more like separate states rather than a "modifier" on some of the existing ones. Not to mention, wouldn't we need a darker version of every single color just in case? That's a lot of changes to make, and we'd end up running into problems with dark blue, teal, and dark teal; or "dark white", gray, and dark gray. Ahemtoday (talk) 03:20, March 4, 2025 (EST)

I don't quite understand option one and two, as the above rules for poll proposals state "A poll proposal closes after all of its options have been settled, and no action is taken until then. If all options fail, then nothing will be done." --PopitTart (talk) 07:09, March 4, 2025 (EST)

Could you explain the contradiction in greater detail? I don't see what you mean. Ahemtoday (talk) 12:01, March 4, 2025 (EST)

Removals

None at the moment.

Changes

Include italics for category page titles for media that normally uses it

Shouldn't category pages for media that uses italics (such as games, shows, movies, etc.) use italics for their category pages? I did start adding it to some pages already, but I thought it was worth proposing about it, possibly to make it policy. I feel like italics should be used though, as it is used everywhere else. For example, the page titled Category:Donkey Kong 64 should be Category:Donkey Kong 64.

Proposer: Kaptain Skurvy (talk)
Deadline: February 20, 2025, 23:59 GMT Extended to February 27, 2025, 23:59 GMT Extended to March 6, 2025, 23:59 GMT

Support

  1. Kaptain Skurvy (talk) Per proposal.
  2. Camwoodstock (talk) Wait, this isn't already policy??? We think this lack of parity speaks a lot to how neglected categories can be in some regards. While yes, the category description isn't really meant to be the main point, we don't think slightly slanted text is distracting from the actual list of articles in the category, and just because categories are more utility than text doesn't excuse the text that is there looking below the standard of a usual article for being "lesser".
  3. Super Mario RPG (talk) Nothing wrong with having more consistency around the wiki.
  4. GuntherBayBeee (talk) Per all.
  5. Salmancer (talk) It is easier to figure out what the standards are from context alone when the standards are applied in every instance.
  6. Hewer (talk) The proposer has confirmed on their talk page that the goal of the proposal is just to put Template:Italic title on category pages, so concerns about formatting the category links on articles are moot (and I'm not sure applying it there would even be possible anyway). With that cleared up, per all, I don't see the harm in some more consistency.
  7. EvieMaybe (talk) per Hewer
  8. Shy Guy on Wheels (talk) sure, for consistencies sake
  9. LadySophie17 (talk) Per Hewer, then.

Oppose

  1. Nintendo101 (talk) Categories are supposed to provide simple, direct, and utilitarian functions, not something to be read or presented to readers. I don't think italicizing them is necessary and would detract from their simplicity.
  2. Sparks (talk) Per Nintendo101. It doesn't feel necessary.
  3. OmegaRuby (talk) What is this supposed to change, exactly? Yes, it's in line with how pages about games are to have the subject italicized, but the change feels unneeded and especially arduous to implement for pretty much no reason. Per Nintendo101.
  4. SolemnStormcloud (talk) Per all.
  5. Rykitu (talk) Per Nintendo101
  6. Mushroom Head (talk) Per all
  7. Technetium (talk) Per all.
  8. Pseudo (talk) Per Nintendo101.

Comments

@Nintendo101: In that case, why do we italicise game titles in category descriptions? (Genuine question, I'm undecided on this proposal.) Hewer (talk · contributions · edit count) 08:58, February 7, 2025 (EST)

Because that is a proper sentence. It is not the tool itself. - Nintendo101 (talk) 20:15, February 7, 2025 (EST)
We mean... Wiki policy is to italicize game titles on their articles' names using {{Italic title}}, too, and those aren't proper sentences. They're article names. Camwoodstock-sigicon.png~Camwoodstock (talk) 19:00, February 8, 2025 (EST)
That's not the same situation in my eyes because the articles are what the site is for. That is what we are writing and presenting to the public. Of course we would italicize those. The categories are a tool, chiefly for site editors, not readers. We do not really gain anything from italicizing their titles. If anything, I worry this would lead to a lot of work to implement, either burdening site editors, porplemontage, or both. - Nintendo101 (talk) 16:05, February 9, 2025 (EST)
So category names are just tools not meant for readers, but category descriptions aren't? Hewer (talk · contributions · edit count) 18:08, February 9, 2025 (EST)
The descriptions are just sentences, and I feel inclined to render those they way we would a sentence anywhere else on the site, be it on articles or in the description for image files. - Nintendo101 (talk) 19:49, February 9, 2025 (EST)
We disagree with the notion categories are more for editors and not readers; while yes, all of the categories on the front page are maintenance categories from the to-do list, the sheer quantity of proposals for categories wouldn't make sense if they were moreso for editors, rather than your average reader; moves such as the reforms for the Look-alikes categories or the Thieves category wouldn't make sense if these weren't meant to be public-facing. And of course, there are the various categories that exist for users, but do not serve a utility purpose, such as the various "users that know a given language" categories.
As for difficulty implementing, considering the recent success stories with images without descriptions and categories without descriptions having gone from 4000+ and ≈100, to 0 and 0 respectively, we have it in good faith that this wouldn't be that hard to implement. Monotonous? Yes. But difficult? It's nothing a bit of caffeine and music can't solve. Camwoodstock-sigicon.png~Camwoodstock (talk) 18:22, February 9, 2025 (EST)
Not only for editors, but chiefly for them. I don't exclude the idea of more curious readers utilizing them, but I suspect they are exceptions. I maintain that their ease of implementation is more important to the site than the formatting inconsistency. Like, are we to be expected to format category ourselves as "[[Category:Super Mario World screenshots|Category:''Super Mario World'' screenshots]]" instead of just "[[Category:Super Mario World screenshots]]" going forward? Would we do this for the articles that are in dozens of categories? Why? I would not want to do that, and I don't find the inconsistency a good enough reason to roll something like that out, and only brings downsides. It makes the tool where one types "[[Category:" almost entirely moot because we would still need to write out the whole name just to format it this way. Others are welcomed to think differently, but I personally think the way we format these names now in categories is perfectly fine. - Nintendo101 (talk) 19:49, February 9, 2025 (EST)

even if this proposal doesn't pass, i think we should use Template:Italic title in the category pages. — Super Leaf stamp from Super Mario 3D World + Bowser's Fury.eviemaybe (talk / contributions) 10:16, February 12, 2025 (EST)

I thought that was the whole proposal. Hewer (talk · contributions · edit count) 03:32, February 13, 2025 (EST)
@Kaptain Skurvy: Could you please clarify whether the proposal's goal is simply to add italic title to categories, or to also do something else as well? Hewer (talk · contributions · edit count) 20:14, February 17, 2025 (EST)
The proposer has clarified on their talk page that adding the italic title template to categories is all the proposal would do if it passed. Hewer (talk · contributions · edit count) 15:21, February 23, 2025 (EST)

Make a standard for citing different pages/sections of the same source across an article, codify it at MarioWiki:Citations

The formatting of citations has been a recurring, if sometimes contentious, topic of discussion around here. What I describe in the proposal's heading is something that happens more often than you'd expect, so it wouldn't hurt to reach a consensus over this practice.

If you're required to cite a source multiple times across an article, the Citations policy already explains a way to link to one instance of that citation multiple times, without the need to copy and paste the entire thing each time. However, this is not practical when you need to cite distinct parts of one source to support different claims across an article. For example, you may need to cite different pages from an issue of Nintendo Power on one article. The same issue may arise even when citing different quotes from a singular page of that publication.

I consulted a few American style guides over the topic, and found their recommendations quite practical. These were my observations:

I looked up some time ago how official American style guides do it and found this (studyhood.com, section "ORDER OF ELEMENTS FOR A BOOK REFERENCE" (2nd)) for MLA and this (libguides.up.edu) for Chicago Manual of Style. To synthetize what both these guides recommend: the first time a source is cited, list the rigmarole that you normally would (author last name, author first name, publication date, title, publisher etc.); if the document then requires that you cite a different page from the same source, use a shortened form that contains the bare necessities.
The two style guides may prioritize different such "bare necessities" for shortform citations. MLA dictates that you should use the author's last name and the relevant page if you source only one work by that author, and additionally list a shortened form of the work's title if you cite multiple works by that author on the same document. Chicago, on the other hand, dictates that you always use the author's last name, title of work (again, a short form!), and page name even if you only cite one work by that author.

In my opinion, the ideal approach on this wiki would be to blend these two guidelines as such: fully elaborate on the source the first time it is cited, as is typically done. For subsequent references to that source, list a condensed version with only the bare minimum (title, page/section) to set them apart from other sources in the article, including the specific page or section cited. If the source shares a title with another work, consider adding a distinguishing detail in its condensed version, such as the author's last name or date of publication, at your discretion. The best justification for this practice is that it helps cut down on redundant information: the reader doesn't need to digest the particulars of a source, such as its authors, ISBN, website, language etc, more than once on a given page. You can view early applications of this standard at Stretch Shroom and Big Penguin. The template {{cite}} can be used in this case as with any other citation.

I noticed that some users prefer to instead fully list the details of that source each time it is referenced. This may be beneficial to better identify a source when it isn't referenced in close succession, but in disparate areas of an article. For this reason, the supporting option is divided between these two approaches. The winning option becomes the standard and is included in the wiki's policy for citations.

Edit (18:00, February 22, 2025 (EST)): Added another option to integrate Wikipedia's "reference page" system, per Nintendo101 (talk)'s suggestion in the comments section. In short, you call a source multiple times in the article using the "name" parameter (optionally listing all the pages you wish to cite throughout the article within the citation), and append the page number or section to a desired reference link to that source in superscript. To exemplify with a fictional source:

  • one instance[1]:18
  • another instance[1]:20
  1. ^ a b Smith, John (1985). Super Mario Bros. Official Guide. McPublisher Publishing ISBN 0000-0000-0000. Pages 18, 20.

Proposer: Koopa con Carne (talk)
Deadline: March 8, 2025, 23:59 GMT

Option 1: Fully list the details of a source upon its first reference, condense its subsequent references to mostly its title and relevant page/section

  1. Koopa con Carne (talk) Per proposal.

Option 2: Fully list the details of a source in repeated references

  1. Ahemtoday (talk) Option 1 seems inconsistent — I'm not a fan of the concept of citing the same source in two different ways within the same article. It'd be jarring when they're next to each other and it'd be difficult to find the missing information when they're far apart. Option 2 has neither of these issues.

Option 3: integrate Wikipedia's "reference page" system

  1. Koopa con Carne (talk) Per Nintendo101.
  2. Nintendo101 (talk) Per my suggestion below.
  3. Camwoodstock (talk) Per Nintendo101; this feels like the best compromise between curbing redundancy, while being more specific on a citation-by-citation basis.
  4. Ahemtoday (talk) This also seems like a reasonable way of doing this.
  5. EvieMaybe (talk) makes sense!
  6. Super Mario RPG (talk) This is a great idea, as it will help refine our citation system.
  7. Mario (talk) Mario in Club Nintendo Classic. Let's not forget to cite this proposal once it's listed in the policy page.
  8. GuntherBayBeee (talk) Per all.
  9. PaperSplash (talk) No reason to stray from Wikipedia's system IMO if it works.

Don't make a standard

Comments (citing multiple parts of a single source)

On Wikipedia, as demonstrated here, they have a system for articles where you write out a citation once, and can convey the individual page numbers in a superscript next to the spots it is invoked in the article. I have long thought that is a great system and could help reduce redundancies on Super Mario Wiki. Do you think this could be reflected in the proposal? - Nintendo101 (talk) 17:33, February 22, 2025 (EST)

I encountered this system before, but completely forgot about it for some reason. Seems like an excellent system for pages and even other non-numeric parts of a source that could outshine the other candidates in the proposal. Still, what do you do, for instance, if you want to cite different quotes from the same page of a book? It's a bit of a fringe scenario, which is why I'm not stressing it in the proposal, but it's not far-fetched either. You can't rely on an in-line superscript, that would be unwieldy. -- KOOPA CON CARNE 18:00, February 22, 2025 (EST)
Good question. I think given the general lack of recurrence, It's okay treat them as different citations like normal. My personal preference is to cite more specific details pertaining to a source only once when the book is first cited (like ISBN number, publisher, location, authors), and then omit some of those details the second time (only mention the title and date, to convey it is the same source that was cited earlier). But I know that is tricky for longer articles. - Nintendo101 (talk) 18:43, February 22, 2025 (EST)

Retool the Names in other languages section into a more general etymology section

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

I've always felt like a subject's name is something we care about a lot in this wiki. However, the way we choose to cover that aspect of each subject could be improved tons. Information about each subject's name (or names) is scattered all over the article, with the English etymology often being at the top of the page, and the names in other languages at the bottom, and information about the various names a subject has gone by lost in History.

Some subjects (Taily, for example) have an "Additional names" section, putting its internal and foreign names in one section. I say, why not take a page out of our fellow NIWA members, namely Pikipedia, Inkipedia and Bulbapedia, and push this a step further?

This new section (called "Names", "Naming", "Etymology", whatever works best) would contain, in roughly this order:

  • The etymology of each English name the subject has gone by, including explaining puns and cultural references
  • The history of the subject's name/s (what was the first game to call Blooper by its modern name, and what was the last game to call it Bloober?)
  • Miscellaneous name-related notes (like how half of Brothership's translations give the Great Lighthouse bosses a common suffix)
  • Internal name table, if applicable
  • The "names in other languages" table

EDIT: If a subject doesn't have anything about its name to talk about (such as a generically-named subject like bubble or a literal name like Mayor Penguin), the section can be titled simply "Names in other languages" as we've been doing. This is to avoid non-sentences like Bulbapedia's "Iron Valiant is literally iron valiant." name explanations.

Proposer: EvieMaybe (talk)
Deadline: March 13, 2025, 23:59 GMT

Retool

  1. EvieMaybe (talk) Per proposal.
  2. Technetium (talk) Per proposal. I find explaining English names in opening paragraphs breaks the flow sometimes.
  3. Waluigi Time (talk) Solid idea, it's not very easy to figure this out since name changes are scattered around history sections which aren't sorted chronologically.
  4. Camwoodstock (talk) Honestly, putting the name explanation in the names in other languages section is maybe the one good thing about Bulbapedia's naming section (we will never not find their arbitrary skepticism extremely strange, such as the gem of "Toucannon may be a combination of toucan and cannon."), so we'd be fine to borrow that. Helps keep things organized and improves the flow of the section.
  5. Fakename123 (talk) Per proposal.
  6. Ahemtoday (talk) I'm in favor of consolidating this information. As for the resultant section's name — I'm pretty fond of how the Zelda wiki calls these sections "Nomenclature". That's a great word for it.
  7. PopitTart (talk) As a frequent Pikipedia editor, Yes all. Names are shockingly poorly documented despite their significance to wiki classification.
  8. Pseudo (talk) Makes sense to me!
  9. Nintendo101 (talk) I like this idea.
  10. Power Flotzo (talk) Never really liked how English name info is just haphazardly slapped on to some articles. Per everyone.
  11. Super Mario RPG (talk) Better organization of naming info. Can we retitle the "foreign names" template while we're at it?
  12. Mushroom Head (talk) Per ałł.
  13. Sparks (talk) Per all.
  14. Mario (talk) Hm.
  15. PaperSplash (talk) Per all. I'm personally partial to how Fire Emblem Wiki labels them collectively though. "Etymology and other languages".
  16. Bro Hammer (talk) Per proposal.

Do not retool (status quo)

Comments in other languages

I've actually been thinking of maybe swapping the order of names in other languages and internal names. The idea was that internal names predate final names, but in practice, many internal names listed come from a subject's subsequent appearances. LinkTheLefty (talk) 07:27, February 28, 2025 (EST)

considering most internal names are either English (which would be explained right above the NIOL box) or Japanese (which would be the first name in the NIOL box), i feel like keeping it between them makes the most sense. — Super Leaf stamp from Super Mario 3D World + Bowser's Fury.eviemaybe (talk / contributions) 13:29, February 28, 2025 (EST)
So we're keeping English ones separate from the Niol section? I can get behind that. Doc von Schmeltwick (talk) 17:03, February 28, 2025 (EST)
yeah, the idea is to have it kinda like Inkipedia. of course it could be executed differently, but i think it's the best alternative — Super Leaf stamp from Super Mario 3D World + Bowser's Fury.eviemaybe (talk / contributions) 20:33, February 28, 2025 (EST)
I have no experience with Inkipedia or Splatoon in general, so that comparison means nothing to me, sorry. Doc von Schmeltwick (talk) 09:22, March 1, 2025 (EST)
...an example is literally linked in the proposal body... — Super Leaf stamp from Super Mario 3D World + Bowser's Fury.eviemaybe (talk / contributions) 13:21, March 1, 2025 (EST)
I just get a weird pop-up when I try to follow it. Doc von Schmeltwick (talk) 14:35, March 1, 2025 (EST)
What is it you see? - Nintendo101 (talk) 11:45, March 3, 2025 (EST)
It's talking about browser cookies. If I see that sort of message on a site that doesn't have to do with something vital, I go back, because I don't think something like a wiki has any business processing browser cookies. Doc von Schmeltwick (talk) 15:13, March 4, 2025 (EST)

Regarding the overall name, I think "Naming" and similar words are the best. "Nomenclature" sounds a bit too.... try-hard IMO. Like, I know we want wording to be encyclopedic, but my own subjective opinion on that word is that it comes off as outright stuffy, going from "encyclopedic" to "distractingly looking like writing from the 18th century." "Etymology" is a fine word, but it refers exclusively to the origins of meaning, not just listing them all out. Doc von Schmeltwick (talk) 17:03, February 28, 2025 (EST)

Will this proposal also affect media (such as the titles for The Super Mario Bros. Super Show! episodes), or just the subjects within the media? Apikachu68 (talk) 19:57, March 3, 2025 (EST)

i don't see why it wouldn't! media also has names and etymology, after all. — Super Leaf stamp from Super Mario 3D World + Bowser's Fury.eviemaybe (talk / contributions) 09:54, March 4, 2025 (EST)

Introducing the crossover article

The passing of this proposal would accomplish seven things:

  1. See the publication of the drafted Zelda article discussed in this proposal, titled "crossovers with The Legend of Zelda." (The draft can be viewed here.)
  2. Funnel redirects and disambiguation pages pertaining to Zelda on the wiki to the published Zelda article (i.e., searches for The Legend of Zelda, Octoroks, etc. Fully covered crossover subjects like Link would keep their articles, and this would not preclude a crossover subject from receiving an article of their own in the future if warranted, such as the inclusion of Princess Zelda in a future Mario Tennis or something like that).
  3. Move details pertaining to Zelda from list articles on the site to this one (i.e. all information pertaining to Sheik on the list of fighters debuting in Super Smash Bros. Melee article would be cleared, and searching for "Sheik" on the site would bring you to this article. Zelda info on the list of references in Nintendo video games article would similarly be cleared. Visitors to that article would be directed towards the published Zelda one when they reach that section of the list article).
  4. Establish a navbox for crossover articles (either a wholly dedicated one, an incorporation into "Template:Culture," or a retooling of "Template:Crossover characters").
  5. Establish the precedent where this can be done for other IPs with which the Super Mario franchise has crossed-over.
  6. Establish a 'Crossover article" section to the MarioWiki:Manual of Style that explains the framework for crossover articles described below. This is to be the standard structure for how other articles are to be structured.
  7. Note that this framework exists on the the crossover section of our coverage policy, and provide a link directing readers to it.

The Super Mario franchise is very much the IP tentpole for Nintendo Co., Ltd. and at least one of the ones for the Japanese video game industry as a whole. Consequently, Super Mario as a franchise and brand has crossed-over with many other franchises, brands, and series over its nearly fifty years of existence - not only sister series developed by Nintendo EAD and R&D, and their successor EPD (i.e. Duck Hunt, Punch-Out!!, Exictebike, Metroid, F-ZERO, Animal Crossing, Pikmin, Splatoon, etc.) and those of their external creative partners (i.e. Ape Inc.'s EarthBound, HAL Laboratory's Kirby, Game Freak's Pokémon, etc.), but also fellow ones from other studios like Square Enix, Sega, Bandai Namco, Koei Tecmo, Chunsoft, Ubisoft, Konami, and Hudson Soft. This is not groundbreaking news: Most folks interested in gaming history already know this, especially the curators of the Super Mario Wiki. However, I do not feel like we handle this information particularly well on the site.

A lot of coverage of Super Mario references, homages, allusions, and cameos are nestled within various list articles, inexplicitly at the end of dedicated game articles, or in Super Smash Bros. articles with which there seemed to have been effort to bury on the site and are not wholly about Super Smash Bros. anyways. This coverage, exasperated by recent efforts to reduce coverage on the Super Smash Bros. series: (1.) obfuscates the fact that Super Mario has made references and is referenced in many other franchises outside of Smash Bros. contexts, often in very meaningful ways that are interesting and fun to read about; (2.) mitigates how Mario has been an influence behind some of these other franchises; and (3.) makes finding some bits of information just very difficult. If I, as a visitor of the site, wanted to understand scenarios where Splatoon and Mario have crossed-over, I would not have an easy way to find that all in one place, and I think that is a shame.

frog man!
green lad!

To better cover and consolidate crossover info on the site, and I have been drafting what I would like to call a "crossover article" using The Legend of Zelda franchise as an example (with contributions from Salmancer, DryBonesBandit, Memelord2020, RHG1951, LeftyGreenMario, and LadySophie17, and feedback from Super Mario RPG, Doc von Schmeltwick, and Koopa con Carne). This is a long article, and it is not wholly completed yet, but I think it is serviceable example of what I would like us to do going forward. Crossover articles take inspiration from the universe articles from our affiliate Smash Wiki and, as apparent in the Zelda draft, consist of the following sections:

  • Overview : A brief description of what the crossover franchise/series is for those not well versed in the subject and would like to know a little more about it without visiting another site, and how this relates to Mario. It is the create a foundation so the reader is not confused by descriptions or terminology in the other areas of the article. For Zelda, this section may be a bit lengthier than it would be for others because Mario had a lot of direct influence on Zelda as a series.
  • Recurring crossover subjects: for subjects like characters, enemies, bosses, or items that make substantial appearances in or alongside Mario-related media, such as subjects that used to have their own articles on the site. Each subject would be briefly explained so readers understand who they are when mentioned in other parts of the article, have explicit conceptual or design connections with Mario highlighted, and summarize areas where they specifically crossover with Mario.
  • History in the Super Mario franchise: a history section for where the crossover subject is referenced in the Super Mario franchise itself.
  • History in the subject series/franchise: a history section for the inverse, where Super Mario is referenced in the franchise subject of the article. In this case, it is Zelda.
  • Shared history (if applicable): a history section for mutual space where both subjects appear, such as the Super Smash Bros. series, Tetris series, NES Remix series, or other media.

Zelda is uniquely related to Mario and nearly as old, but crossover articles can be written for smaller franchises/series as well. The only requirement for a series/franchise to receive an article of its own is for it to directly crossover with Super Mario within an officially licensed capacity. Articles of this nature should not be written for series/franchise that simply make homages to Super Mario or have elements inspired by it, such as Celeste, Gears of War, or Astro Bot.

I offer three options:

  1. Support: I like the idea of crossover articles and want to see them implemented as described.
  2. Support: I like the idea of crossover articles, but list articles for the Super Smash Bros. series should be left alone.
  3. Oppose: I do not like the idea of the crossover article and do not want to see them implemented.

I know this was a long one, folks. Sorry about that, but the ideas behind this idea are multifaceted. Please let me know if you need additional clarity on anything or if you have any recommended amendments. (Also, if you would like, I welcome you to contribute to the drafted Zelda article! It is in my "community garden" sandbox for a reason.)

Proposer: Nintendo101 (talk)
Deadline: March 17, 2025, 23:59 GMT

Support: let's implement crossover articles!

  1. Nintendo101 (talk) Link costume pose in Super Mario Maker
  2. Super Mario RPG (talk) Per proposer.
  3. Koopa con Carne (talk) Per proposal with absolutely no second thought. Aside from the obvious value such articles would bring, this practice may incidentally just be the silver bullet for the community's differences on how to cover Smash Bros. content. Nintendo101, even with your inspiration from SmashWiki, I'd say you still managed to think out of the box here.
  4. Waluigi Time (talk) Per all.
  5. EvieMaybe (talk) been waiting a long time for this one. per proposal!
  6. LadySophie17 (talk) Secondary choice, I suppose. Better than no article.
  7. Camwoodstock (talk) Secondary option; we'd rather these articles exist, even if the Smash coverage is confusing, than these articles not exist at all.
  8. PopitTart (talk) It has always felt absurd to me that Captain Olimar's presence on the wiki is entirely an entry in List of fighters debuting in Super Smash Bros. Brawl, despite being directly based on Mario himself and having appearances in Luigi's Mansion, WarioWare: D.I.Y., Super Mario Maker, Yoshi's Woolly World, Mario Kart 8, and WarioWare Move It!

Support: let's implement crossover articles, but leave Smash Bros. lists alone

  1. LadySophie17 (talk) Per proposal. I believe the articles would be better focused on the relationship between their respective series and Mario. Detailing all their character's Smash histories (which could get quite lengthy with something like Pokémon) would be better left in the List articles they currently are in.
  2. Sparks (talk) Per Sophie.
  3. Doc von Schmeltwick (talk) - Per Soph
  4. Camwoodstock (talk) Primary option; per Sophie, we worry about the length of some Smash sections, and we feel the organization is fine enough as it is right now for Smash-related subjects.
  5. Tails777 (talk) Per Sophie. I fully agree with making crossover articles to cover the relations another franchise has with Mario, but Smash in of itself is also a crossover and covering the details of these characters in a place that relates to Smash feels better.

Oppose: let's not implement crossover articles

Crossover comments

I also happened to start a draft for a Pikmin series article the other day, inspired by Nintendo101's Zelda draft. It's in a much... much rougher state, but I hope it gives an idea what these crossover articles can provide.--PopitTart (talk) 19:31, March 3, 2025 (EST)

@Koopa con Carne thank you for the kind words! - Nintendo101 (talk) 20:30, March 3, 2025 (EST)

Link -- KOOPA CON CARNE 11:32, March 4, 2025 (EST)

Question: One of the proposed points is to "Move details pertaining to Zelda from list articles on the site to this one", but the i.e. states that "all information pertaining to Sheik on the list of fighters debuting in Super Smash Bros. Melee article would be cleared". Characters on these fighter lists have extensive history sections; will these be moved to the crossover pages as well, or will these be nixed altogether?
Also, what about franchises which currently only have a connection with Mario through Smash Bros., such as ARMS? Will these get a crossover article as well or not? ArendLogoTransparent.pngrend (talk) (edits) 12:10, March 4, 2025 (EST)

I don't know. Perhaps we'll cross that bridge when we get there. Ultimately, very few of the franchises within Smash Bros. have only crossed-over with Mario within Smash Bros., and that was at the front of my mind for this proposal. ARMS is one of the few exceptions. I should probably make some sort of list to parse what other series and franchises are within that boat. But what would you want to see, @Arend? - Nintendo101 (talk) 15:52, March 4, 2025 (EST)

So is the ultimate plan for these to effectively be a replacement for the Smash list pages? I imagine the lists would start looking a bit barren if things on them get moved to crossover franchise articles. Hewer (talk · contributions · edit count) 16:07, March 4, 2025 (EST)

I am admittedly not a fan of the fighter list articles on the wiki and I think the information on them would be better served in articles more directly focused on the Super Mario franchise, both for readers and editors. However, I respect the will of those who would rather we keep those articles around. I am not sure if you looked at my Zelda draft, but it does omit more granular information specific to the Super Smash Bros. series, like stickers, trophies, Classic Mode routes, special moves, or NIOLs for individual characters. I would rather this article emphasize how Zelda engages with Mario in other contexts. If folks would rather Super Mario Wiki continue to hold onto the more granular Smash Bros. info on the fighter list articles, they could be retained for those purposes, I imagine. - Nintendo101 (talk) 16:47, March 4, 2025 (EST)
Well, there are two voting options for people who want both. Super Mario RPG (talk) 16:52, March 4, 2025 (EST)

Color-code game, series and franchise infoboxes to match their navigation template colors

The color coding used in navigation templates could be used for more cases outside navigation templates. Since the wiki covers all the distinct branches of the Mario franchise (which are numerous), using those theme colors more often to sectionalize and identify them may make things easier to navigate through in some cases. While I don't think there are cases where this would have a high impact right now, we could apply them to the game, series and franchise infoboxes, where they are fitting.

As it currently stands, the light red color of the game infobox specifically implies "Mario" to me at least, while the purple color of the series and franchise templates I suppose is arbitrary. This change would make it possibly more intuitive from a glance at the top of the article to which Mario branch the article belongs. It would also establish a common element to the introduction of articles belonging to the same set, while also establishing a color consistency between the very top and the very bottom of the article.

As for the colors themselves, I imagine something like:

  • infobox background: the navigation template's lighter background (e.g. #FFF5EE for Mario);
  • darker cell background: the navigation template's darker background color (e.g. bisque for Mario);
  • header: the navigation template's header color (e.g. #CC0000 for miscellaneous Mario, #FF2400 for Super Mario);
  • border: #aac, #aca, #acc, #caa, #cac or #cca, depending on the most closely matching color.

Proposer: Bro Hammer (talk)
Deadline: March 17, 2025, 23:59 GMT

Support: implement color coding for game, series and franchise infoboxes

  1. Bro Hammer (talk): Per my proposal
  2. Super Mario RPG (talk): Per proposer.

Oppose: do not implement color coding for game, series and franchise infoboxes

  1. Nintendo101 (talk) I honestly prefer keeping infoboxes color coordinated to what type of the subject the article is about. It is intuitive and helpful. I feel like allowing too many colors for this infobox would only dilute that structure across the board. I would support some sort of quick way to jump between entries in the same series at the bottom of the infobox, similar to our level and world infoboxes, but I'd rather all game articles share the same colored infobox.
  2. EvieMaybe (talk) per Nintendo101
  3. Technetium (talk) Per Nintendo101.
  4. Hewer (talk) Per, and I also already find the navbox colours for most series to be quite random and arbitrary.
  5. Rykitu (talk) Per Nintendo101 and Hewer.

Comments

Miscellaneous

None at the moment.

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