Bulbapedia:Usertag policy: Difference between revisions
m (how dare you) |
Politoed666 (talk | contribs) (Fixing. :D) |
||
| Line 1: | Line 1: | ||
{{Policy|policy|proposed}} | {{Policy|policy|proposed}} | ||
Bulbapedia has recently adopted a | Bulbapedia has recently adopted a new '''[[:Category:Usertags|Usertag]] policy''', which pertains in particular to their creation. | ||
While it is important for any fansite to allow their users a place to express themselves and let others know more about them, | While it is important for any fansite to allow their users a place to express themselves and let others know more about them, the Bulbapedia staff feel that there must be a standard for creation usertag creation. In the past, we have cracked down on laziness templates as well as integrated groups of usertags into a single, multipurpose one, such as {{template|User Pet}} and {{template|User Want}}. To reduce the amount of maintenance that Bulbapedia administrators need to do in the <code>Template:</code> namespace, we are now requiring that any and all new usertags are to either be created in the <code>User:</code> namespace, under User:(your username)/(template name) or in the case of a tag that is only to be used on one page, that the {{template|User Template}} template be used. | ||
We have compiled a list of criteria usertags must meet before they will be moved to the <code>Template:</code> namespace. | |||
Please note that creating usertags directly into the <code>Template:</code> namespace will result in the tag being moved to the <code>User:</code> namespace. | ==Criteria for a Usertag to be moved into the Template namespace== | ||
* The usertag must have at least five users using it. | |||
* The usertag must be deemed useful enough to be in the <code>Template:</code> namespace by at least two {{bp|administrators}}. | |||
* Note: If an administrator creates a usertag, it ''does not'' need to meet the above criteria, and is instead instantaneously approved. | |||
Once a usertag has met the following criteria and is brought to the attention of an administrator(s), it may be moved to the <code>Template:</code> namespace. | |||
Please note that creating usertags directly into the <code>Template:</code> namespace will result in the tag being moved to the <code>User:</code> namespace, and after multiple offenses, a short ban may occur. | |||
Revision as of 23:17, 12 July 2009
 |
This article is a proposed policy for Bulbapedia.
Please discuss the proposed policy and suggest possible changes on the article's talk page. |
Bulbapedia has recently adopted a new Usertag policy, which pertains in particular to their creation.
While it is important for any fansite to allow their users a place to express themselves and let others know more about them, the Bulbapedia staff feel that there must be a standard for creation usertag creation. In the past, we have cracked down on laziness templates as well as integrated groups of usertags into a single, multipurpose one, such as {{User Pet}} and {{User Want}}. To reduce the amount of maintenance that Bulbapedia administrators need to do in the Template: namespace, we are now requiring that any and all new usertags are to either be created in the User: namespace, under User:(your username)/(template name) or in the case of a tag that is only to be used on one page, that the {{User Template}} template be used.
We have compiled a list of criteria usertags must meet before they will be moved to the Template: namespace.
Criteria for a Usertag to be moved into the Template namespace
- The usertag must have at least five users using it.
- The usertag must be deemed useful enough to be in the
Template:namespace by at least two administrators. - Note: If an administrator creates a usertag, it does not need to meet the above criteria, and is instead instantaneously approved.
Once a usertag has met the following criteria and is brought to the attention of an administrator(s), it may be moved to the Template: namespace.
Please note that creating usertags directly into the Template: namespace will result in the tag being moved to the User: namespace, and after multiple offenses, a short ban may occur.
