LifeWiki:Template editors

The template editor user right can be granted to experienced coders who have proven themselves to be trustworthy with editing templates to edit all of them, including fully protected templates. It grants the user  to edit fully protected templates, and   to allow them to edit cascade-protected templates.

Policy
You can request the template editor flag at LW:RFP, and by requesting it, you agree to the following:
 * 1) That you will not use the right to protect pages except in cases of emergency, or with permission from an administrator.
 * 2) That you will not use this right to edit fully protected pages outside of the template and module namespaces without permission from an administrator.
 * 3) That you will not use this right to make controversial changes to high-risk templates such as Protected page text/full without first seeking consensus or at least contacting an administrator.
 * 4) That you will not use this right to perform any vandalism.
 * 5) That you should have a strong password and two-factor authentication.

Guidelines for granting
In order to request this right, you should (not must) have
 * 1) At least five hundred edits, where
 * 2) At least 10% of them were made to the module or template namespaces
 * 3) Demonstrated experience with templates, modules, or technical areas in general
 * 4) No blocks in the past six months outside of joke blocks, edit warring blocks, or username blocks.

Guidelines for un-granting
If you meet any or all of these criteria, your template editor right will be revoked. You have a:
 * 1) Demonstrated lack of understanding of templates, causing severe errors to display on pages, such as changing the altskin template, which is transcluded on the Main Page, and accidentally breaking the entire CSS code
 * 2) Any blatant vandalism
 * 3) Using the permission to perform controversial changes to templates without determining consensus, or using it in content disputes and edit wars, or you have been
 * 4) Inactive for twelve months, or you have a
 * 5) Failure to comply with proper account security practices, because this permission is very powerful.