MarioWiki:Proposals

List of Talk Page Proposals

 * Create a New Super Mario Bros. (series) article. (Discuss) Deadline: December 12, 2015, 23:59 GMT
 * Split from Sticker (Discuss) Deadline: December 14, 2015, 23:59 GMT
 * Split the Trophy section from Super Smash Bros. into a new article named . (Discuss) Deadline: December 15, 2015, 23:59 GMT
 * Split Mario Party information from Item Shop into . (Discuss) Deadline: December 15, 2015, 23:59 GMT
 * Split Fire Flower (the Special Attack) section of Mario & Luigi series into a new article named . (Discuss) Deadline: December 19, 2015, 23:59 GMT

Writing Guidelines
None at the moment.

New features
None at the moment.

Removals
None at the moment.

Changes
None at the moment.

Do not relegate charts to templates
This proposal affects, , , and any other similar templates that have been overlooked. These three are charts that were once part of their respective articles (Super Smash Bros. for Wii U, Mario Kart 7, and Mario Kart 8), but were unceremoniously split into those templates. Nobody complained, and here we are. I think it's about time somebody complained. Simply put, the advantages do not outweigh the disadvantages. I brought the topic up on one of the template's talk pages, and Walkazo, BL, and LGM chimed in with their own comments. Moving the charts doesn't make editing all that much simpler, since that's what editing via section is for, and it just makes editing the charts more complicated. Since the article still has to load the template as well, I believe that it wouldn't help all that much for loading times either. Meanwhile, sticking the charts on a template by themselves is inconvenient and makes no sense considering that they're only going to be used on one or two articles, max. These charts can easily be reincorporated back into their articles.

This proposal is not affecting rules and other protected page, such as the proposal header, since they are kept separate in order to ensure that they can only be edited by the right people.

Proposer: Deadline: December 17, 2015, 23:59 GMT

Support

 * 1) I support my proposal.
 * 2) Per proposal. Having them as templates makes it slightly more difficult/time-consuming to edit them. Templates are mainly for use on multiple pages, it makes no sense to create an entire template just for one page...
 * 3) Per myself and all involved in the talk. Get rid of 'em.
 * 4) - Per TT, I see no benefits in the current situation.
 * 5) I actually complained in person with Baby Luigi and was about to bring it up, but the latter never occurred to me. Anyway, per my comment in the talk page; templates are intended to save repetition on particular coding when it is used several times, such as navtemplates, infoboxes, notice templates, and button input. This may save text or so when you're editing an entire page, but the savings are measly when it is much more inconvenient for editors and has virtually no advantages for our readers. So, yeah, just move them back to their parent page.
 * 6) Per all.
 * 7) Just because I have no idea what "relegate" means doesn't mean a chart isn't the same as a template. Per all.
 * 8) Per all.
 * 9) Per all.

Comments
Wording title is kind of weird, the proposal's strength in the future may be better if it said "Stop outsourcing entire chart content to templates"; "stop" is more precise since the outsourcing is ongoing; "relegate" is vague compared to "outsource". 15:53, 10 December 2015 (EST)
 * That seems pedantic.

Poking around a bit more, I actually found a bit more justification for the SSB4 template: it was meant to go on both Super Smash Bros. for Wii U and Super Smash Bros. for Nintendo 3DS, so rather than having all the identical info duplicated, it'd just be in one central place, saving space and making upkeep easier, which, assuming the two games remain identical in their rosters, does make sense. The guy who made the template initially put it on both pages, but then there was an edit war on the 3DS page and ended in the removal of the template, but really, looking at the two charts, I fail to see a difference, and really, that edit summary is contradictory to what the chart was envisioned to do (and I checked, and it looks like the pre-template version of the 3DS chart was indeed the same as the Wii U / current one). I agree that a one-template-to-one-page substitution is needless complication (we actually told people to stop doing it on userpsace years ago), but it could make sense for pages that share large chunks of content. (But even then, prior discussion would be better than just striking out on one's own.) - 16:01, 10 December 2015 (EST)
 * For this case I do see the use in having the template. Maybe the proposal could be modified to say templates only used on one page are useless whereas if they're used on more than one it's fine to have them? --
 * My sister brought it up previously: "it's more convenient to edit the template once than go through it twice" but it may not have been clear to you at the time. Anyway, I've said this already: templates are supposed to make repetitive content easier to implement, but I think we can go through case-by-case rather than make a flimsy qualifier in this proposal. 16:10, 10 December 2015 (EST)


 * Just to note: the difference in the Smash Bros. tables is that certain characters that are unlockable in the Nintendo 3DS version (Bowser Jr., Ganondorf, and Ness) are available by default in the Wii U version, and both tables reflect that by listing those characters in the appropriate sections. If we were to use one table then we would have to show that difference.


 * -Toa 95 (talk)
 * Well, there goes that. There is no reason to create the template for those either. I knew there was some catch between the 3DS and Wii U games when it comes to characters. 16:18, 10 December 2015 (EST)
 * I didn't see the talk page again after I made my comment - got too busy and forgot to check back. And ah, okay, I didn't catch the different between-header placements: I just thought there were arbitrary order differences at times and the headers blended into everything. Too bad - it'd be easier to manage one set of info, but yeah, setting up a switch function to have those characters appear in different places depending on the page would probably be too much trouble for most peoples' tastes. - 16:35, 10 December 2015 (EST)