Template:Failed policy/doc: Difference between revisions
Created page with "To include a shortcut, pass a parameter: <code><nowiki>{{Failed|WP:SHORT}}</nowiki></code>. When adding this template, it is recommended to provide links to any new proposals that superseded it, if known. == When to use == A proposal is considered unsuccessful if, within a reasonable timeframe, there is no consensus for its acceptance. It is not necessary for consensus to be totally opposed; if consensus is ambiguous or indifferent towards the..." |
m Harvici moved page User:Harvici/Template: Failed policy/doc to Template:Failed policy/doc: Test |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| ⚫ | |||
When adding this template, it is recommended to [[Template:Superseded|provide links to any new proposals that superseded it]], if known. |
|||
== When to use == |
== When to use == |
||
A proposal is considered unsuccessful if, within a reasonable timeframe, there is no consensus for its acceptance. It is not necessary for consensus to be totally opposed; if consensus is ambiguous or indifferent towards the matter and unlikely to change, the plan has also failed. |
A proposal is considered unsuccessful if, within a reasonable timeframe, there is no consensus for its acceptance. It is not necessary for consensus to be totally opposed; if consensus is ambiguous or indifferent towards the matter and unlikely to change, the plan has also failed. |
||
| ⚫ | |||
| Line 13: | Line 10: | ||
<!-- Abstract usage of the template --> |
<!-- Abstract usage of the template --> |
||
<code>{{Failed|''shortcut''}}</code> |
<code>{{Failed policy|''shortcut''}}</code> |
||
The first unnamed parameter (or named as {{Para|1}}) is optional. If supplied, it displays as a link to the appropriate [[WP:SHORTCUT|shortcut]] page for the proposal. (Note that this is not automatic; MediaWiki cannot determine the shortcut from the page itself. You need to discover or create the shortcut yourself.) Please do not create shortcuts for failed proposals; intelligible shortcuts are a finite resource. In fact, shortcuts may be usurped from long-failed proposals to redirect to something active. |
The first unnamed parameter (or named as {{Para|1}}) is optional. If supplied, it displays as a link to the appropriate [[WP:SHORTCUT|shortcut]] page for the proposal. (Note that this is not automatic; MediaWiki cannot determine the shortcut from the page itself. You need to discover or create the shortcut yourself.) Please do not create shortcuts for failed proposals; intelligible shortcuts are a finite resource. In fact, shortcuts may be usurped from long-failed proposals to redirect to something active. |
||
Latest revision as of 16:33, 9 May 2024
When to use[edit source]
A proposal is considered unsuccessful if, within a reasonable timeframe, there is no consensus for its acceptance. It is not necessary for consensus to be totally opposed; if consensus is ambiguous or indifferent towards the matter and unlikely to change, the plan has also failed.
To include a shortcut, pass a parameter: {{Failed policy|TW:SHORT}}.
How to use[edit source]
{{Failed policy|shortcut}}
The first unnamed parameter (or named as |1=) is optional. If supplied, it displays as a link to the appropriate shortcut page for the proposal. (Note that this is not automatic; MediaWiki cannot determine the shortcut from the page itself. You need to discover or create the shortcut yourself.) Please do not create shortcuts for failed proposals; intelligible shortcuts are a finite resource. In fact, shortcuts may be usurped from long-failed proposals to redirect to something active.
The |date= parameter can be used to add the date at which the page was tagged as failed, or at which a formal WP:PROPOSAL process did not accept the proposal. It accepts any valid date format.
A |result= AKA |reason= parameter can also be used to add free-form text explaining the failure This should be kept short (e.g., a concise sentence or two), since this is a banner template. The content of this parameter will be auto-formatted as a separate paragraph below the default text (and thus should not itself contain paragraph markup).