118
edits
User talk:Zeal: Difference between revisions
→Signature Policy
m (→Signature Policy: new section) |
|||
| Line 35: | Line 35: | ||
Any other questions, let me know, I'll be happy to help out. --[[user:Jioruji_Derako|<font color="#237d00"> '''J'''ïörüjï '''Ð'''ērākō.'''>'''</font>]]<small>[[user talk:Jioruji Derako|<font color="#237d00">''.cнаt'''''^'''</font>]]</small> 08:21, 30 March 2008 (UTC) | Any other questions, let me know, I'll be happy to help out. --[[user:Jioruji_Derako|<font color="#237d00"> '''J'''ïörüjï '''Ð'''ērākō.'''>'''</font>]]<small>[[user talk:Jioruji Derako|<font color="#237d00">''.cнаt'''''^'''</font>]]</small> 08:21, 30 March 2008 (UTC) | ||
:Well i was expecting such a response. Though i was expecting to have to justify myself too. | |||
:On WoWWiki, sig templates are allowed, and i noticed when i came here, the sigs were mostly templated and contained many (unneccessary) images, so just tried to keep it low profile and neat. The reason i changed mine back and discouraged subst is, as you've realized, they can contain a good deal of markup and styling which you don't want editors to have to read through. Any changes to a sig once it's been included in a good deal of pages would always require a new sig to be made and modified via the SigX pointer. This is to prevent overloading the job queue, otherwise editors could bring a wiki to it's knees. | |||
:I noticed that i can't edit my sig (as well as it's pointer to circumvent subst) now, as you've said. Why is this? there's no right changes in the history and i've not seen an extension used that would automatically protect templates on inclusion :S | |||
:Anyways, if you're enforcing that new policy, then i'll comply with it, and switch to a new sig and reduce the amount of markup and styling. I can handle that myself simply with a new sig page anyway, not a problem. --{{SUBST:User:Zeal/Signature}} 08:49, 30 March 2008 (UTC) | |||