68:
339:, but there are a few warning templates written in other languages. It is important that templates use language that is easily understood. Bear in mind that English Knowledge attracts editors from all over the world; not everyone on English Knowledge will speak English as a first language. When considering the wording of a template the following points should be observed:
90:
699:
To prevent the problem with newlines, templates must be on a single code line; however, this is highly illegible to humans in edit view. To restore legibility, HTML comments can be inserted to emulate the appearance of newlines. Although this looks ungainly with two-term lines, the comments are much
530:
When a template's parameters might be given symbols that break templates (notably the '|' pipe symbol and '=' equals sign), a named syntax should allow these. In such cases, a named and unnamed can coexist as needed. For example, a wikilink template can assign both a name and a number to a parameter
387:
in Level 3, Level 4 and Level 4im templates as well as in single issue warnings. Level 2 templates often include reference to the blocking policy but the wording is much less strong; for example, Level 2 templates often include text similar to "Continuing to edit disruptively could result in loss of
428:
No derivative template (a non-standard variant of a template under a new name) should be included in the list of standardized templates or mentioned in the documentation. Although users are free to create and use non-standard templates, these should not be recognized in the standardized sets listed
173:
There are different severity levels for templates. All multi-level templates include several levels of increasing severity. The tone of these varies, from kindly, to very stern. These templates don't necessarily have to be followed in chronological order; a user may use any level of their choice;
687:
Templates with newlines will break any list they are placed in: the first paragraph will be in the list, the others out, and any subsequent templates in the list will begin a new list. By using HTML paragraph syntax directly, Knowledge's paragraph parsing is circumvented and multiple-paragraph
286:
The multi-level templates range from a polite pointer to the sandbox to a stern warning that the editor desist immediately or face consequences. There are also single issue notices that serve to remind other editors about minor mistakes. These generally cover common editing errors, such as not
593:, where 'username' is the username and 'skin' is the name of the skin in use (usually monobook). To help users take full advantage of this feature, block templates should be enclosed in a CSS container with the "user-block" class.
326:
Regardless of the severity level of the template, any user warning should be a model of civility (even for the most destructive vandal). Remember that when you use a warning template, you may be seen to do so in
Knowledge's name.
679:
All user warning and block templates should be natively compatible with lists. For optimal intervention efficiency, talk pages with numerous warnings are sometimes organized into formatted lists sectioned by date (see the
419:
All references to blocking should include the use of the word "may" rather than "will" (be blocked from editing). This allows administrators to exercise discretion when dealing with complex cases of abuse.
250:. If the nature of the disruptive editing appears to be a content dispute, and an editor continues to engage in such edits, after a level 3 warning; consideration can be given to reporting the matter at a
475:
these tags. This allows the use of the template on a page (such as a talk or list page) without adding that page to a category by using the template with no value specified for the category parameter:
295:
There are also single issue warnings. Single issue warnings generally serve to advise editors of policy breaches that; if repeated, are likely to result in a block. An example of such an act would be
628:
Should the user wish to, they can customize the appearance of all block templates by adding CSS to their user stylesheet. For example, the following code adds a dark red background with white text.
565:
should include a "safesubst:" parameter at the appropriate location. This allows for easy substitution of all nested templates inside a template. For example, consider the following template code:
246:. Instead, you should consider the nature of the disruptive editing. If the edits relate to obvious disruption that is not properly defined as vandalism, it may be appropriate to report them to
52:
47:
225:– Only Warning – Assumes bad faith; very strong cease and desist, first and only warning. Generally used in the case of excessive or continuous disruption from a user or specific IP.
174:
based on the severity desired. For example, the test series is test1, test2, test3, test4. The number of levels for any given template depends, on the editing actions in question.
370:
The message should identify specific behavior. If possible, avoid "or" statements and other language that would not be used had the message been written out by a human.
496:
Nearly every parameter should have a default value, such that misuse does not break the template. You can set the default value of a parameter by using piped syntax (
451:(if the template is a redirect page to another template, it should be categorized using the sort key "Redirect"). User block templates should be categorized to
75:
32:
57:
251:
229:
467:
Any template that places pages it's used on into a category should surround the category tags with the category parameter. If the template uses
164:. This is to assist counter-vandalism tools and bots in detecting and identifying user warning templates, and to be transparent to recipients.
74:
Before designing a new template, please check that it, or one like it, does not already exist. If you are unsure, discuss the matter on the
42:
455:, with the sort key "Temporary" or "Indefinite" as appropriate. The category tag should be on the template page within noinclude syntax.
124:
313:
287:
leaving an edit summary. These notices are not classed as warnings and the actions they advise against almost never result in a block.
177:
27:
17:
722:
674:
361:. Beginning the message with "Welcome to Knowledge" or "Hello" and ending with "Thank you" is considered appropriate.
448:
242:. Although it may be appropriate to warn disruptive editors, it is not appropriate to report them as vandals at
452:
399:
block warning. Typically Level 3 templates include: "Continuing to edit disruptively may result in you being
388:
editing privileges." Level 1 and single issue notices should not include reference to the blocking policy.
590:
580:
262:
198:
406:
Level 4, Level 4im, and single issue warnings typically include text similar to: "If you continue to...
384:
290:
545:. However, some symbols will break the template if used like that. These require the named syntax:
281:
437:
684:). Due to the way Knowledge parses wiki syntax into HTML, list items are closed at any newline.
130:
Template names should be of similar syntax i.e. no spaces, capitals, etc., and preferably use a
154:
98:
All standardized user talk namespace templates should meet the guidelines set out on this page.
432:
277:– Warning – Assumes bad faith; cease and desist. Generally includes "Please stop" or "Stop".
556:
391:
Level 3 templates often include a more direct reference to blocking, although, they should
8:
486:
321:
562:
111:
317:
296:
103:
681:
500:). For example, the template below takes a parameter; it expects the user to supply a
462:
235:
302:
442:
380:
Generally speaking, block advisories should appear at the end of the template text.
374:
336:
239:
183:
213:– Warning – Assumes bad faith; cease and desist. Generally includes "Please stop".
146:
All templates should include a comment containing the template name in the format
586:
491:
409:
400:
330:
307:
186:. For editing actions that can include severe or gross examples of vandalism, a
716:
525:
364:
358:
351:
247:
243:
531:
by 'nesting' them (placing parameters in other parameters' default values).
219:– Final Warning – Assumes bad faith; strong cease and desist, last warning.
182:
There are 4 levels of template for editing actions that can be considered
522:, the template will use the default value, and expand to "This is cool".
688:
templates can then be added to organized warning lists without problem.
168:
344:
143:
All templates made obsolete are to have the relevant redirects added.
131:
423:
357:
Level 1 and Level 2 templates and single issue notices should
429:
in these pages and should not be named using the uw- prefix.
265:. Generally includes "Welcome to Knowledge" or some variant.
201:. Generally includes "Welcome to Knowledge" or some variant.
501:
134:. All standardized template names should be prefixed uw-.
561:
Any template containing templates, magic variables, or
335:
With few exceptions user warnings should be written in
504:, but if they don't, it uses a default noun ("This").
700:
less bulky when used with more realistic paragraphs.
518:
will expand to "This help page is cool". If the with
514:, the template will expand to "Knowledge is cool".
343:Keep the message of the template 'on-track', avoid
350:Try to keep sentences as concise as possible, see
190:template is also included in the template series.
714:
585:Knowledge allows registered users to maintain a
447:User warning templates should be categorized to
125:Naming convention, basic format and maintenance
541:is straightforward enough, and will expand to
271:– Caution – No faith assumption; just a note.
207:– Caution – No faith assumption; just a note.
244:Administrator intervention against vandalism
230:Multi-level templates for disruptive editing
314:Knowledge:Please do not bite the newcomers
569:This is {{{{{|safesubst:}}}CURRENTYEAR}}.
471:tags, be careful to place the parameter
383:It is appropriate to make reference to
14:
715:
162:<!-- Template:uw-vandalism1 --: -->
137:Templates will not include ==Headers==
248:Administrators' noticeboard/Incidents
148:<!-- Template:templatename --: -->
412:from editing without further notice"
84:
62:
483:{{{category|]}}}</noinclude: -->
367:should be avoided in all templates.
178:Multi-level templates for vandalism
23:
18:Knowledge:WikiProject User warnings
24:
734:
234:It is important to remember that
573:Substituting the template using
88:
66:
449:Category:User warning templates
140:Templates will not include ~~~~
53:View all single-level templates
547:{{template|link=article|name}}
160:template contains the comment
48:View all multi-level templates
13:
1:
453:Category:User block templates
577:will output "This is 2024".
354:for advice on writing style.
7:
516:{{template|This help page}}
352:Knowledge's manual of style
10:
739:
433:Template coding guidelines
311:
101:
723:WikiProject User warnings
675:Compatibility with lists
630:
595:
403:." Or a variant thereof.
96:This page in a nutshell:
58:View all block templates
710:Paragraph 3.</p: -->
707:Paragraph 2.</p: -->
704:Paragraph 1.</p: -->
696:Paragraph 3.</p: -->
694:Paragraph 2.</p: -->
692:Paragraph 1.</p: -->
549:, which will expand to
510:Supplied with the noun
459:] ] </noinclude: -->
591:user:username/skin.css
512:{{template|Knowledge}}
477:{{template|category=}}
507:{{{1|This}}} is cool.
498:{{{1|default value}}}
303:Civility and language
291:Single issue warnings
76:centralized talk page
539:{{template|article}}
401:blocked from editing
282:Single issue notices
252:relevant noticeboard
587:personal stylesheet
557:Nested substitution
322:Knowledge:Etiquette
150:. For example, the
581:Block template CSS
575:{{subst:template}}
482:<noinclude: -->
469:<noinclude: -->
458:<noinclude: -->
318:Knowledge:Civility
263:Assumes good faith
236:disruptive editing
199:Assumes good faith
43:Table of templates
359:assume good faith
122:
121:
83:
82:
38:Design guidelines
730:
670:
667:
664:
661:
658:
655:
652:
649:
646:
643:
640:
637:
634:
624:
621:
618:
615:template message
614:
611:
608:
605:
602:
599:
576:
570:
552:
548:
544:
540:
521:
517:
513:
499:
478:
470:
375:Block advisories
163:
159:
153:
149:
114:
92:
91:
85:
70:
69:
63:
60:
55:
50:
45:
40:
35:
33:Usage and layout
30:
738:
737:
733:
732:
731:
729:
728:
727:
713:
712:
711:
708:<!-- --: -->
705:<!-- --: -->
697:
677:
672:
671:
668:
665:
662:
659:
656:
653:
650:
647:
644:
641:
638:
635:
632:
626:
625:
622:
619:
616:
612:
609:
606:
603:
600:
597:
583:
574:
568:
563:ParserFunctions
559:
550:
546:
542:
538:
535:
528:
519:
515:
511:
508:
497:
494:
489:
484:
476:
468:
465:
460:
445:
440:
435:
426:
377:
333:
324:
310:
305:
293:
284:
232:
180:
171:
169:Severity levels
161:
157:
151:
147:
127:
118:
117:
110:
106:
89:
67:
61:
56:
51:
46:
41:
36:
31:
26:
22:
21:
20:
12:
11:
5:
736:
726:
725:
702:
690:
676:
673:
631:
596:
582:
579:
558:
555:
533:
527:
524:
506:
493:
492:Default values
490:
488:
485:
481:
464:
463:User talk page
461:
457:
444:
441:
439:
438:Categorization
436:
434:
431:
425:
422:
421:
420:
417:
416:
415:
404:
381:
376:
373:
372:
371:
368:
365:Colloquialisms
362:
355:
348:
332:
329:
309:
306:
304:
301:
292:
289:
283:
280:
279:
278:
272:
266:
231:
228:
227:
226:
220:
214:
208:
202:
179:
176:
170:
167:
166:
165:
144:
141:
138:
135:
126:
123:
120:
119:
116:
115:
107:
102:
99:
93:
81:
80:
71:
25:
15:
9:
6:
4:
3:
2:
735:
724:
721:
720:
718:
701:
689:
685:
683:
629:
594:
592:
588:
578:
571:
566:
564:
554:
532:
523:
505:
503:
480:
474:
456:
454:
450:
443:Template page
430:
418:
413:
411:
405:
402:
398:
394:
390:
389:
386:
382:
379:
378:
369:
366:
363:
360:
356:
353:
349:
346:
342:
341:
340:
338:
328:
323:
319:
315:
300:
298:
288:
276:
273:
270:
267:
264:
261:– A notice –
260:
257:
256:
255:
253:
249:
245:
241:
237:
224:
221:
218:
215:
212:
209:
206:
203:
200:
197:– A notice –
196:
193:
192:
191:
189:
185:
175:
156:
155:uw-vandalism1
145:
142:
139:
136:
133:
129:
128:
113:
109:
108:
105:
100:
97:
94:
87:
86:
79:
77:
72:
65:
64:
59:
54:
49:
44:
39:
34:
29:
19:
698:
686:
678:
627:
610:"user-block"
584:
572:
567:
560:
536:
529:
526:Named syntax
520:{{template}}
509:
495:
472:
466:
446:
427:
407:
396:
392:
334:
325:
297:edit warring
294:
285:
274:
268:
258:
233:
222:
216:
210:
204:
194:
187:
181:
172:
95:
73:
37:
589:located at
424:Derivatives
408:you may be
709:<p: -->
706:<p: -->
703:<p: -->
695:<p: -->
693:<p: -->
691:<p: -->
682:guidelines
651:!important
642:background
636:user-block
487:Parameters
395:include a
345:digression
312:See also:
240:vandalism
223:Level 4im
188:level 4im
184:vandalism
28:Main page
717:Category
385:blocking
331:Language
308:Civility
132:mnemonic
104:Shortcut
410:blocked
337:English
275:Level 3
269:Level 2
259:Level 1
238:is not
217:Level 4
211:Level 3
205:Level 2
195:Level 1
112:WP:UWDG
537:Using
473:inside
397:bolded
320:, and
657:color
623:: -->
617:</
613:: -->
604:class
16:<
663:#FFF
648:#C00
598:<
502:noun
620:div
601:div
393:not
719::
553:.
534:]
479:.
316:,
299:.
254:.
158:}}
152:{{
669:}
666:;
660::
654:;
645::
639:{
633:.
607:=
551:]
543:]
414:.
347:.
78:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.