MarioWiki talk:Proposals/Header: Difference between revisions
| Line 34: | Line 34: | ||
It's not a very big change, but it the way the font is rendered in Courier or Courier New instead of Ariel. Seeing this font type rendered like that above reminds you of that same particular font type when trying to edit a wiki page. It's a hint that gives a subtle nudge in the right direction when trying to make a new proposal, especially for newcomers. It would be notably weird to see <nowiki>===blah BLAH 1234===</nowiki> in Ariel, and not <code><nowiki>===blah BLAH 1234===</nowiki></code> in Courier or New Courier when trying to edit a page. {{User:RAP/sig}} 01:04, 12 April 2016 (EDT) | It's not a very big change, but it the way the font is rendered in Courier or Courier New instead of Ariel. Seeing this font type rendered like that above reminds you of that same particular font type when trying to edit a wiki page. It's a hint that gives a subtle nudge in the right direction when trying to make a new proposal, especially for newcomers. It would be notably weird to see <nowiki>===blah BLAH 1234===</nowiki> in Ariel, and not <code><nowiki>===blah BLAH 1234===</nowiki></code> in Courier or New Courier when trying to edit a page. {{User:RAP/sig}} 01:04, 12 April 2016 (EDT) | ||
:No, it should be left as-is. The text which can be copied is already contained within its own space separated by header lines. And the instructions above already invite inexperienced readers to copy from the section below. Most importantly, the current instructions provide links to the Writing Guidelines page and the Talk Page Proposals section. | :No, it should be left as-is. The text which can be copied is already contained within its own space separated by header lines. And the instructions above already invite inexperienced readers to copy from the section below. Most importantly, not all of the section is intended to display an example code: the current instructions provide links to the Writing Guidelines page and the Talk Page Proposals section. It is inconsistent with the rest of the page and looks quite odd to include links while trying to display the same text, just in a way that users would see in their edit box. | ||
:{{User:YoshiKong/sig}} 05:20, 14 July 2016 (EDT) | :{{User:YoshiKong/sig}} 05:20, 14 July 2016 (EDT) | ||
Revision as of 04:27, July 14, 2016
Order
Can somebody explain me why is the How to subsection before the table of contents while the Talk page proposals one is after it? I don't want a technical answer, but I'd like to hear the reason, I'm just wondering :)
Banon (talk · edits) 11:53, 31 May 2013 (EDT)
- So that all the TPP stuff is grouped together on MarioWiki:Proposals. - Walkazo 20:05, 31 May 2013 (EDT)
Punctuation
Shouldn't there be a closing square bracket somewhere in the "Deadline" row? GBAToad (talk) 00:36, 28 June 2013 (EDT)
On Rule #16: replace Administrators with Bureaucrats (because Administrators cannot promote or demote)--
07:04, 4 July 2013 (EDT)
- But the Admins as a whole decide who gets promoted: the only 'Crat-specific part of the process is pushing the button (and writing the log), but procedure trumps technical details. - Walkazo 11:32, 4 July 2013 (EDT)
Dates
Can the example dates be updated? It makes this page look really out of date when they're over four years ago (1 Aug 2016 is a Monday again, for simplicity). - Reboot (talk) 23:58, 14 December 2015 (EST)
- "Outdated" implies the page isn't useful anymore, but the standards have not changed since the example was made, so it's still perfectly accurate and functional - not outdated, and I see no compelling reason whatsoever to arbitrarily change the examples. If anything, having a rules section that's been written solidly enough to not need overhauling for over 4 years is a thing to be proud of. - Walkazo 00:35, 15 December 2015 (EST)
Minor improvement suggestion on proposal skeleton
May I suggest wrapping this whole block with <code></code>?
===[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|[enter your username here]}}<br>
'''Deadline''': [insert a deadline here, 7 days after the proposal was created (14 for Writing Guidelines andTalk Page Proposals), at 23:59 GMT, in the format: "August 8, 2011, 23:59 GMT"]
====Support====
#{{User|[enter your username here]}} [make a statement indicating that you support your proposal]
====Oppose====
====Comments====
It's not a very big change, but it the way the font is rendered in Courier or Courier New instead of Ariel. Seeing this font type rendered like that above reminds you of that same particular font type when trying to edit a wiki page. It's a hint that gives a subtle nudge in the right direction when trying to make a new proposal, especially for newcomers. It would be notably weird to see ===blah BLAH 1234=== in Ariel, and not ===blah BLAH 1234=== in Courier or New Courier when trying to edit a page. 
RAP... 01:04, 12 April 2016 (EDT)
- No, it should be left as-is. The text which can be copied is already contained within its own space separated by header lines. And the instructions above already invite inexperienced readers to copy from the section below. Most importantly, not all of the section is intended to display an example code: the current instructions provide links to the Writing Guidelines page and the Talk Page Proposals section. It is inconsistent with the rest of the page and looks quite odd to include links while trying to display the same text, just in a way that users would see in their edit box.
