Sarkarverse:Signatures: Difference between revisions
(Expand) |
(++) |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Shortcut|SV:SIGN}} | {{Shortcut|SV:SIGN}} | ||
{{GLL}} | {{GLL}} | ||
{{subcat guideline|behavioral guideline|Signatures|SV:SIG|SV:SIGNATURE|SV:SIGN|SV:FOURTILDES}} | |||
{{subcat guideline|behavioral guideline|Signatures| | |||
{{nutshell|Please sign your posts on talk pages, using <code><nowiki>~~~~</nowiki></code>. Keep the coding of your signature short, do not make the signature too large, do not embed files in it, and ensure that the end result is easily readable by virtually everybody.}} | {{nutshell|Please sign your posts on talk pages, using <code><nowiki>~~~~</nowiki></code>. Keep the coding of your signature short, do not make the signature too large, do not embed files in it, and ensure that the end result is easily readable by virtually everybody.}} | ||
{{Guideline list}} | {{Guideline list}} |
Latest revision as of 07:14, 21 November 2013
Sarkarverse guidelines |
---|
Behavioral |
Content |
Stand-alone article |
Discussion |
Editing |
Organization |
Style |
Directories |
This page documents an English Sarkarverse behavioral guideline. It is a generally accepted standard that editors should attempt to follow, though it is best treated with common sense, and occasional exceptions may apply. Any substantive edit to this page should reflect consensus. When in doubt, discuss first on the talk page. |
This page in a nutshell: Please sign your posts on talk pages, using ~~~~ . Keep the coding of your signature short, do not make the signature too large, do not embed files in it, and ensure that the end result is easily readable by virtually everybody. |
Sarkarverse guidelines |
---|
Behavioral |
Content |
Stand-alone article |
Discussion |
Editing |
Organization |
Style |
Directories |
Signing your posts on talk pages, both for the article and non-article namespaces, is good practice, and facilitates discussion by helping identify the author of a particular comment. Other users can then navigate to a talk page and address their comments to the specific, relevant user(s). Discussion is an important part of collaborative editing, because it helps all users to understand the progress and evolution of a work.
Comments posted on user talk pages, article talk pages and other discussion pages should be properly signed. Signature use that is intentionally and persistently disruptive may lead to blocking under the disruptive editing policy.
When editing a page, main namespace articles should not be signed, because the article is a shared work, based on the contributions of many people, and one editor should not be singled out above others.