Help:Templates: Difference between revisions

From BoyWiki
← Older edit
VisualWikitext
 
(48 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Stub}}




A list of BoyWiki templates can be found on [[Portal:Template index]].


Templates are pages shown in [[Portal:Template index]]. This means any page whose name begins with "Template:", such as "[[Template:Documentation]]", can be used as a template. The content of a template can be added to a page by typing <nowiki>{{templatename}}</nowiki> while editing the page. When the page is later viewed, <nowiki>{{templatename}}</nowiki> is replaced by the content of the page "Template:templatename". If the page "Template:templatename" is later altered, all the pages with <nowiki>{{templatename}}</nowiki> in them will change automatically.
Any page whose name begins with "Template:", such as "[[Template:Documentation]]", can be used as a template. The content of a template can be added to a page by typing <nowiki>{{templatename}}</nowiki> while editing the page. When the page is later viewed, <nowiki>{{templatename}}</nowiki> is replaced by the content of the page "Template:templatename". If the page "Template:templatename" is later altered, all the pages with <nowiki>{{templatename}}</nowiki> in them will change automatically.


Amongst other things, templates are used to add recurring messages to pages in a consistent way, to add boilerplate such as template {{Tl|stub}} which indicates that the article is a fledgling.   
Amongst other things, templates are used to add recurring messages to pages in a consistent way, to add boilerplate such as template {{Tl|stub}} which indicates that the article is a fledgling.   
Line 14: Line 14:


==General==
==General==
Most templates are pages in [[Portal:Template index]]
Most templates are listed on [[Portal:Template index]]


Templates can contain any desired [[Help:Wikitext|Wikitext]], including calls to other templates. They have some limited programming capacities: customizable values (called [[#Parameters|parameters]]), calculation and branchings (using parser functions), and access to wiki-specific variables ([[Help:Magic words|magic words]]), such as dates, times, and page names. They may also contain tags which define which parts of the wikitext are to be included when the template is transcluded or substituted. This means that the appearance of the template page itself need not be the same as that of the transcluded content (for example, it can contain documentation, categories, etc. for the template).
Templates can contain any desired [[Help:Wikitext|Wikitext]], including calls to other templates. They have some limited programming capacities: customizable values (called [[#Parameters|parameters]]), calculation and branchings (using parser functions), and access to wiki-specific variables ([[Help:Magic words|magic words]]), such as dates, times, and page names. They may also contain tags which define which parts of the wikitext are to be included when the template is transcluded or substituted. This means that the appearance of the template page itself need not be the same as that of the transcluded content (for example, it can contain documentation, categories, etc. for the template).
Line 55: Line 55:
Notice that the same double-brace syntax is used for many MediaWiki variables and parser functions (see [[Help:Magic words]]). For example, the code <code><nowiki>{{NAMESPACE}}</nowiki></code> may look like a template call, but it is actually a variable whose value is the namespace prefix of the current page.
Notice that the same double-brace syntax is used for many MediaWiki variables and parser functions (see [[Help:Magic words]]). For example, the code <code><nowiki>{{NAMESPACE}}</nowiki></code> may look like a template call, but it is actually a variable whose value is the namespace prefix of the current page.


==Usage hints and workarounds==
 
The following points may be worth noting when using templates:
* An unnamed parameter cannot contain an ordinary equals sign, as this would be interpreted as setting off a named parameter. (This does not apply if the equals sign comes within another template call or other item which the parser handles separately.) To pass an equals sign in an unnamed parameter (for example in a [[URL]] with key/value pairs), replace the equals sign with the special template {{tlx|{{=}}}}, which returns an equals sign that will not be specially interpreted. Another method is to replace the unnamed parameter (and any subsequent unnamed parameters) with named parameters&nbsp;— the first unnamed parameter is equivalent to a named parameter with the name "1", and so on. So to call template {{tl|done}} with the parameter "a=b", type either <code><nowiki>{{done|a{{=}}b}}</nowiki></code> or <code><nowiki>{{done|1=a=b}}</nowiki></code>.
* Similarly, it is not possible to use an ordinary pipe character | in template parameters, as it will be interpreted as a separator. (Again, this does not apply if it comes within another separately parsed item, such as a piped wikilink.) This time the problem can be solved by using the special template {{tlx|!}} in place of the pipe, or (if the pipe is not intended to be parsed specially at a higher level) using the [[List of XML and HTML character entity references|HTML entity]] <tt>&amp;#124;</tt>.
* Remember that whitespace characters (spaces, tabs, carriage returns and line feeds) are not automatically stripped from the start and end of unnamed parameters (as they are from named parameters). Including such characters (or any other non-visible characters in any parameters) may in some cases affect the template's behaviour in unexpected ways. (Template designers can use {{tl|StripWhitespace}} to remove unwanted whitespace in unnamed parameters.)
* In documentation and discussions it is often convenient to be able to produce the template call syntax, with a link to the template in question, but without actually calling the template. This can be done easily using the "{{tl|tl}}" template (the ''template link'' template). For example, using the text "<tt><nowiki>{{tl|tc}}</nowiki></tt>" produces "{{tl|tc}}". There is an extended version, {{tl|tlx}}, which also supports parameters.
* When a template is changed (when the template or one of its subtemplates is edited), the change will be reflected on all pages on which the template is transcluded. However the change may not become visible on all pages immediately&nbsp;— a previously cached version of a page, based on the previous version of the template, may continue to be displayed for some time. Use the [[Help:Purge|purge]] function to force a page to be displayed using the latest versions of templates. (This includes the template page itself, if it contains usage examples.)
* When viewing old versions of pages, remember that templates will be transcluded as they are now, not necessarily as they were when the old page version was active.
* To list all pages onto which a template is transcluded, use [[WP:What links here|What links here]] on the template page. (This will not include pages where the template has been substituted.)
* To get a list of templates transcluded on a page, click "Edit", and find the list below the edit window. This list also includes the sub-templates used by the templates that are directly transcluded. To get such a list for a page section, an old version of the page, or your newly edited version prior to saving, click "Show preview" on the appropriate edit page. (For an old version, the subtemplate tree will be constructed according to the templates' current state.)
* There are limits to the number and complexity of the templates that an article may have. See the "[[#Expand limits|Expand limits]]" section for help in resolving this.


==Creating and editing templates==
==Creating and editing templates==
Templates are created and edited in much the same way as any other page: choose an appropriate name, navigate to that page, then click the Edit tab or create a new page as needed. As mentioned above, templates are normally placed in the [[WP:Template namespace|Template namespace]], though templates intended for your own personal use or for experimentation can be created in your own [[WP:user space|user space]]. Anything that can be included on a normal page or article can be included on a template, including other templates (called ''subtemplates''). Templates often make use of programming features&nbsp;— parameters, parser functions and other [[Help:Magic words|magic words]]&nbsp;— which allow the transcluded content to vary depending on context. There are also special tags to control which information is transcluded and which is not.
Templates are created and edited in much the same way as any other page: choose an appropriate name, navigate to that page, then click the Edit tab or create a new page as needed. Templates intended for your own personal use or for experimentation can be created in your own [[WP:user space|user space]]. Anything that can be included on a normal page or article can be included on a template, including other templates (called ''subtemplates''). Templates often make use of programming features&nbsp;— parameters, parser functions and other [[Help:Magic words|magic words]]&nbsp;— which allow the transcluded content to vary depending on context. There are also special tags to control which information is transcluded and which is not.


Before creating a template, do a quick search for existing templates (e.g. by exploring [[Portal:Template index]]) to see if there's already a template that does what you want, or a similar template whose code can be copied and modified (or left in place and expanded). Look for generic templates on which the new template can be based (for example, [[WP:navbox|navbox]] templates can be easily created by calling the generic [[Template:Navbox]]).
Before creating a template, do a quick search for existing templates (e.g. by exploring [[Portal:Template index]]) to see if there's already a template that does what you want, or a similar template whose code can be copied and modified (or left in place and expanded). Look for generic templates on which the new template can be based (for example, [[WP:navbox|navbox]] templates can be easily created by calling the generic [[Template:Navbox]]).
Line 76: Line 66:
'''Be extremely careful when editing existing templates&nbsp;— changes made can affect a large number of pages, often in ways you might not expect.'''  
'''Be extremely careful when editing existing templates&nbsp;— changes made can affect a large number of pages, often in ways you might not expect.'''  


To propose the deletion of unused or inappropriate templates, or other changes in the way particular templates are used, go to [[WP:Templates for discussion|Templates for discussion]] (TfD).
===Handling parameters===
The values of the parameters which can be fed to a template are represented in the template code by items enclosed between ''triple'' braces:
* the code <code><nowiki>{{{xxx}}}</nowiki></code> will be replaced by the value of the parameter named ''xxx''
* the codes <code><nowiki>{{{1}}}</nowiki></code>, <code><nowiki>{{{2}}}</nowiki></code> etc. will be replaced by the first, second etc. unnamed parameter (or the value of a parameter named ''1'', ''2'', etc.); these are sometimes known as ''positional'' parameters
If a parameter is not assigned a value, then the above replacements will not take place&nbsp;— the form "{{{xxx}}}" will remain as the effective value of the parameter. To change this behaviour, define default values using the pipe syntax. For example, <code><nowiki>{{{1|default}}}</nowiki></code> will be replaced by the first unnamed parameter if there is one, or otherwise by the text "default". Similarly, <code><nowiki>{{{xxx|}}}</nowiki></code> will be replaced by the parameter named ''xxx'' if it exists, or otherwise will be left blank. Though if a template is called with the parameter specified as empty (e.g. <code>&#123;&#123;Example|&#125;&#125;</code>), the default for the parameter will be ignored; if that is undesired one can use <code><nowiki>{{#if:{{{1|}}}|{{{1}}}|default}}</nowiki></code> instead to get the text "default" even if the parameter is specified as empty.


Parameters do not get expanded when they are inside nowiki tags or XML-style extension tags. Thus, the following will not work within a template&nbsp;— <nowiki><myextension xparam={{{tparam}}}> ... </myextension></nowiki>&nbsp;— because the parameter is not expanded.


Because of the multiple uses of double-brace and triple-brace syntax, expressions can sometimes be ambiguous. It may be helpful or necessary to include spaces to resolve such ambiguity, for example by writing <code><nowiki>{{ {{{xxx}}} }}</nowiki></code> or <code><nowiki>{{{ {{xxx}} }}}</nowiki></code>, rather than typing five consecutive braces. However, watch out for unwanted whitespace appearing in template expansions.


===System variables and conditional logic===
===System variables and conditional logic===
Line 168: Line 148:
|}
|}


==Finding and Using Templates==
==Text Paragraphs==
There are already several thousands of templates within the WikiBooks templates namespace.  That is another way of saying that the templates list is already long.  At first sight, this may seem to avoid the need for template-making, but things are not so simple.
The code for a template need not start with any special character or symbol.  The main consideration is that the code performs the required action, just as if it were typed directly onto the page.  At the 'end of the code block, be sure to add the '''<nowiki><noinclude></noinclude></nowiki>''' tags as mentioned above.


If the ''name'' of the template is known, then it can be found easily, but if the name is ''not'' known, it can take a long time to find a template similar to the one that you are looking for.  Templates have their functions described on their own pages but many do not include notes, so the task of knowing which is which, and what they do even when they are found, becomes doubly difficult.
All of the existing Wikitext and HTML code that can be used in a page can be used for a text template.  The user of a page does not have access to the parts associated with styles, namely the heading of the web page and their style sheets.  As a result, users are limited to modifying the parts of the page that ''are'' available, the text within the body of the page.  Those familiar with web page design will know that the only remaining available method is to modify the page's text with '''in-line styles'''.  Working methods use the '''<nowiki><div></div></nowiki>''' tags and the '''<nowiki><span></span></nowiki>''' tags, thanks to a feature of Wikitext that allows the use of HTML coding within it.  CSS, (Cascading Style Sheet), properties and values are used within these tags to modify the text styles that would otherwise apply.


Templates made in ''Wikipedia''  and ''Wikibooks'' are not interchangeable, since they exist on separate servers.   Although the code to make them is identical, this description applies to finding things in Wikibooks.   
    


*To view lists of templates listed ''alphabetically'' within WikiBooks, follow the link to the [http://en.wikibooks.org/w/index.php?title=Special:AllPages&namespace=10 '''All Templates Namespace'''].
====The Simplest Case====
*To find templates listed in various template ''categories'', for example, ''drop-control templates'', follow the link to the page [[:Category:Templates]].
Before doing any formatting, consider the method for making a template from a simple block of text.  Type a block of text, with all of its formats and page layout in place, then save the block as a template.  It is as simple as that.
*If you ''know'' a template's name, then find the template page by using the search box on any Wiki page.  For example, to find ''Dropimage'' just type;
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>Template:Dropimage</nowiki>}}
then ''enter''.


When a template page is found, the code to make the template can be seen by viewing its editing window.  Many pages have their documentation on the same page as the template code, isolated from it with <nowiki><noinclude></noinclude></nowiki> tags.


If after searching, you still need to make a template, as many no doubt do, then read on.


 
==Making Boxes==
===Put it on the Page===
----
----
Templates are called for use in pages by typing a line of Wikitext, and so the user needs to know the correct spelling of the template's name, options, and parameters.  Even when these are known it is all too easy to disrupt a page with a template error, especially during trials, so consider using the [[WB:SB|'''sandbox''']] for testing.  Some templates have all of the documentation and details on the same page and this makes them easy to use.   See templates [[Template:Plainlist|Plainlist]], and  [[Template:Codebits|Codebits]] as examples.
The following sections ''make'' box or table templates from Wikitext.  They can also be made with HTML tables in the same way.    When it comes to ''making'' such a template, wikitext is fine but when a table is needed to go ''into'' a template as its parameter, or part of its parameter, an HTML table should be used instead.   


To ''call up'' any template for use in a page, '''the code is typed within double curly brackets'''. <nowiki>{{}}</nowiki>.   
This [http://en.wikibooks.org/wiki/Editing_Wikitext WikiBooks text] touches on HTML table structures, and explains how to use styles.   
Included within the curly brackets is the template '''name''', then, if required, a sequence of '''options''', followed by a sequence of '''parameters'''.   '''All entries are separated by ''pipe'' symbols'''. ('''<nowiki>|</nowiki>''').  For example, the general form to use for a template with two ''options'' and one ''parameter'' is as follows:
{{-}}
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{Name|Option1=Value|Option2=value|Parameter1}}</nowiki>}}
{{-}}
and a typical example of its use is:
{{-}}
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{Plainlist|width=250px|background=LightSalmon|The text for the box goes here.}}</nowiki>}}           
{{-}}
The above code has only ''one'' parameter; it is numbered '''1''' by default.  Parameters are given numbers or names to identify them in their design code, and examples will be seen in the sections that follow.  The template-call in the example uses a so-called ''unnamed'' parameter, because it is not preceded by a term like '''1=''' (numbered parameter),  or '''content=''' (typical named parameter).        When templates have ''several'' parameters then the parameter numbers or names help to make clear to the template which is which.  Alternatively, the template can manage with unnamed and unnumbered parameter entries provided that they are in any case listed in their correct number sequence.  When in doubt, use names or numbers.  At times, especially when the first character of a parameter is a symbol, the use of named or numbered parameters avoids the corruption that would otherwise result with the unnamed entry.


'''The sequence of <u>''options''</u> is ''unimportant''''', since '''all options must be named''' in any case.  Using ''named'' values just means adding the name of the option and an equals sign before the option's ''value''.  This of course requires a knowledge of the template's details.
   
====The Box Structure====
Boxes are essentially ''tables'', in fact table cells.  The CSS property list to format  tables is extensive.  Simple boxes make use of the table ''container'', and one or two ''cells'' within it.


'''''Template'' names are sensitive to case except for the first letter''', so a useful convention is to use lower case for template name, parameters, and options all of the time; that way you will never be in doubt.
Apart from the table container, the other structures of a table include its ''rows'', and ''cells''.  In the case below there are two rows, each with only one cell in them.  Each part of a table has properties that affect it, and an example of typical table coding can be seen in the listing below.


'''''Parameter'' names are quite sensitive to case in every way''', so a capital letter makes all the difference.  As a general rule, do not mix ''unnamed'' and ''named'' parameters in a template call, since the method used by the program to interpret their meaning becomes confused.  Either use ''all unnamed'' with special attention to their sequence, or ''all named'' in any order that you like.
====Parameters and Options====
It is intended to provide three ''options'' along with the two ''parameters''.  The options are to be ''background'',''width'', and ''align''.  The parameter ''names'' are to be ''1'' and ''2'', with the labels ''heading'' and ''content''.


===Find Details from Code===
===Nesting templates===
----
Templates may contain other templates&nbsp;— this is usually called "nesting". As the template is processed, the wikitext produced by any nested templates is transcluded into the nesting template, so that the final product is essentially processed from the most deeply nested template out. While fairly straightforward in application, it involves some noteworthy quirks and tricks.
Let us assume that a template made by others has been found but that its details are unclear.   Even without much knowledge of mark-up, it is usually possible to discern the options and parameters of a template by inspection of its coding.  To see how this can be done follow the reasoning below.


The coding and anything else on a template page can be displayed in the sandbox by typing a special code there.  The template does not do anything when this is done; it just reveals the text of the template page.  That is, it reveals the coding and any documentation.  As an example the template code for say, the template '''Tocbox''', can be viewed in the Sandbox by typing:
===Examples===
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{msgnw:tocbox}}</nowiki>}}
Here are two examples of box templates that are easy to use and are useful to those just starting out.
To save the reader the trouble of doing so here, the template code for '''Tocbox''' is given below.
{{-}}


'''Code for the Template Tocbox'''<br>
<table cellpadding=20px style="font-family:courier;border:1px dashed blue;background:#f9f9f9;;">
<td align=left><poem style="font-family:'Courier New', Courier, monospace; font-size:1.1em;"><nowiki>{| class=toccolours style="margin:1em 0 0 0;width:{{{width|300px}}};" align={{{align|left}}}
| align=center style="font-weight:bold;"|{{{Heading|{{{1}}}}}}
|-
| align=left style="font-weight:normal;"|{{{Content|{{{2}}}}}}
|}
<noinclude>
</nowiki></poem></td>
</table>


{{-}}
<pre>
The template page itself has a good description for its use, but assume for a moment that the descriptive material was absent.   The code at the top of a template page is ''always'' the template source code; consider the example given above.   Although it looks complicated, the object here is ''not'' to understand it, but to find the options and parameters from the code itself.
{{Box1 start}}
Sample text
{{Boxes end}}
</pre>
;gives...
{{Box1 start}}
Sample text
{{Boxes end}}
<pre>
{{Box1 start}}
Box1 text
{{Box2 start}}
Box2 text
{{Boxes end}}
</pre>
;gives...
{{Box1 start}}
First box text
{{Box2 start}}
Second box text
{{Boxes end}}


Note that the end of the code is marked with a <nowiki><noinclude></nowiki> tag, to make sure that any text that follows it is not used as a part of the template.   In this example, there are ''two'' parameters; they can be recognized as the items with the form:
===Making a Basic Wiki Table===
<pre>
{|class="wikitable"
! one box
|} </pre>
;gives...


{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{{heading|{{{1}}}}}}  and  {{{content|{{{2}}}}}}</nowiki>}}
{|class="wikitable"
! one box
|}


These entries identify '''parameters''' ''one'' and ''two'' respectively.   It is clear, even without much understanding, that the first parameter is the ''heading'' text and the second parameter is the ''content'' text, and these terms in addition to the numbers could be used as their names .   In the event that a user forgets to enter the parameter for say, ''content'', a '''{{{2}}}''' will be displayed on the page as a reminder of what is missing.
<pre>
{|class="wikitable"
!
!Top row
|-
!First row
| (add some txt)
|}
</pre>
;gives...
{|class="wikitable"
!
!Top row
|-
!First row
| (add some txt)
|}


All of the '''options''' within this template are recognized from the typical form;
<pre>
{| class="wikitable"
!top row
!This is text
!This is more txt
!This is more txt
|-
!line1
|(add some txt)
|(add some txt)
|(add some txt)
|-
!line2
|(add some txt)
|(add some txt)
|(add some txt)
|-
!line3
|(add some txt)
|(add some txt)
|(add some txt)
|}
</pre>
;gives...


{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{{align|left}}}</nowiki>}}
{| class="wikitable"
!top row
!This is text
!This is more txt
!This is more txt
|-
!line1
|(add some txt)
|(add some txt)
|(add some txt)
|-
!line2
|(add some txt)
|(add some txt)
|(add some txt)
|-
!line3
|(add some txt)
|(add some txt)
|(add some txt)
|}
<pre>
{| class="wikitable" style="float: right;: 1em auto 1em auto;"
|+ '''(this is my table name)'''
! scope="col" | top row
! scope="col" | This is text
! scope="col" | This is text
|-
| row 1 || (add some txt) || (add some txt)
|-
| row 2 || (add some txt) || (add some txt)
|}
</pre>
;gives...


This extract states that there is an option called ''align'' that has the default value of ''left''.  The idea of this default is that the value '''left''' would be used for ''align'' if the user does not use that option in the template call. The option could have almost ''any'' name; in fact it has been given the same name as the '''HTML attribute''' associated with it, (the part before the equals sign in the main code block).  There are several properties within this code but only two of them have been coded as options; ''align'' and ''width'', and both options have similar bracket formats to that of the above example.
{| class="wikitable" style="float: right;: 1em auto 1em auto;"
 
|+ '''(this is my table name)'''
With the options and parameters now understood, test the template on a page as follows:
! scope="col" | top row
 
! scope="col" | This is text
This is the code:
! scope="col" | This is text
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{tocbox|align=center|width=300px|Heading text|Content paragraphs}}</nowiki>}}
|-
The result is:
| row 1  || (add some txt) || (add some txt)
{{tocbox|align=center|width=300px|Heading text|Content paragraphs}}
 
It should by now be clear that despite having no specification for the template in the first instance, it has been possible to obtain information from the coding for its use.
 
 
 
===Modifying a Template===
----
Assume for a moment that a template has been found that is ''nearly'' right, but not quite.  Say for example that the background color was the only part that was wrong.  The source code for such a template could be changed, by adding a term to modify its background color.  Then, the ''modified'' version could be saved as a new template, with a different name.  Note that if the modified template were saved with the ''same'' name as before, the existing users who depended on the original colors would experience unwelcome changes in their work.
 
There is another way that allows the new user to choose colors while the existing users can continue to enjoy the default colors that their work displays.  The template can keep the old name if the background property is made into an option, and the original background color made its default.  Then, since the old users would not bother to specify the background color, perhaps not even knowing that they now ''could'', they would get the usual color as the default value and would be happy with it.  The new users who need a ''different'' color, could simply specify it as an option value when they call the template for use.  In this way both parties would be content.
 
The modifying of a template approaches the difficulty of ''making'' a new one at times, and this process is covered in other sections below.  For the background-change case, a suitable '''modified Tocbox''' code module would look like this.
The code is:
<table cellpadding=20px style="font-family:courier;border:1px dashed blue;background:#f9f9f9;;">
<td align=left><center>Code for a Modified Template Tocbox</center><br><poem style="font-family:'Courier New', Courier, monospace; font-size:1.1em;"><nowiki>{| class=toccolours style="margin:1em 0 0 0;width:{{{width|300px}}};background:{{{background|#f9f9f9;}}};" align={{{align|left}}}
| align=center style="font-weight:bold;"|{{{Heading|{{{1}}}}}}
|-
|-
| align=left style="font-weight:normal;"|{{{Content|{{{2}}}}}}
| row 2 || (add some txt) || (add some txt)
|}
|}
<noinclude>
<Br>
</nowiki></poem></td>
If you float the wikitable right, you can make your text rap around the box without leaving large blank spaces on your page. This is often very useful.
</table>
<Br>
{{-}}
<center> (This is how a line would look.)</center>  
In the above code the ''background'' property has been made into an option.  In addition, the original background color, '''#f9f9f9;''' , (light gray), has been used for the default.  To labor the point, if the user does not bother to specify the background color, he will still get the ''gray'' color as before.  Note again that the added option need not have been called ''background'' but could, for example, have been called ''bgc'' or some other name.  In that event the template's option code would look like '''<nowiki>background:{{{bgc|#f9f9f9;}}}</nowiki>''', and another color would then be called using say, '''<nowiki>bcg=papayawhip</nowiki>''' on the page. 
 
The real template '''Tocbox''' has not been modified here, though this example provides a reliable demonstration of the method to use for doing so.  After the modification above the template could be called by the new users as follows:
 
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{tocbox|align=center|width=250px|background=papayawhip|Heading|Long text paragraphs}}</nowiki>}}
 
A knowledge of CSS property values allows considerable variation in a template's appearance.  Luckily, the subject is well documented.  See the external ''W3'' site's [http://www.w3schools.com/css/css_reference.asp '''CSS Reference List'''] for a comprehensive listing of values and properties.  Although the examples on the referenced page are designed for style sheets, the syntax found there is also that used for modifying styles within templates and other in-line styles.  In addition, a useful color reference can also be had at [http://en.wikipedia.org/wiki/Web_colors '''Web Colors'''].  A drop-box with many of the CSS properties for tables has been provided in the box-making section below. If time is short it could be noted that most of the template work done so far in this project, (WikiBooks that is), could have made do with little more that the CSS properties of text and tables.    Study of these two areas is thus rewarding.
 
CSS reference sources are useful, though styles can also be changed with ''HTML attributes'', (the styles like ''align'' with the ''equals'' signs).  Such attributes can be seen in HTML reference texts as opposed to CSS texts, and in the aforementioned drop-box below.  It may be of interest to know that some HTML attributes are the only ways to accomplish certain tasks;  examples include ''colspan'' (to span table columns), ''rowspan'' (to span table rows), and ''align'', (to align tables to center, something that the CSS ''float'' property cannot do).
 
 
 
==Making Templates==
There are many template types, but those used for inserting and modifying text are the most numerous.  Boxes feature next; whether they are ''information boxes'', so-called ''user boxes'', or simple ''text boxes'', they all have common constructs.  Some templates have dynamic functions, like drop-controls, though once their basic outlines are clear, they can be shaped for many purposes.  At least one example of each will be considered.
 
Template making consists of writing functional code, Wikitext or HTML, or sometimes a mixture of both.  The method is to test the code in the Sandbox, until the function works well.  Then the options and the parameters can be assigned to the code.  These are tested again, and if all is well, the block of code can be saved as a template.
 
In saving the template it as well to check whether or not there is an existing template of that name already.  The simplest way to save a template is as follows.  First, make sure that you are logged-on in a page of '''WikiBooks''', to avoid making a template in the wrong project.  Go to the ''search'' box at the left of the WikiBooks page, and enter the wording to find the as-yet unmade template.  Assume here that the intended name is to be '''Caption'''.  The line to type in the search window is just:
 
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>Template:Caption</nowiki>}}
 
If the template is found, then the name is already taken, and another is needed.  Assuming that the name is not found, then the search results window will state that it was not found and ask whether or not you want to ''make'' the page.  Click the link to make the page.
 
The link opens a template editing page with the name of the template already listed as its address.  Copy the code from your work in the sandbox, then paste it into the empty template page.  In the line immediately following the last line in the code block, add the tags '''<nowiki><noinclude></noinclude></nowiki>'''.  All text not intended to be a part of the template code, must be placed ''between'' these tags, as is the case for the template's description.
 
Finally, save the page by pressing the ''Save page'' button at the bottom of the page.  The template is now made, and can be called into use with its given name.  Go to the sandbox and test the features of the template. 
 
 
 
===Text Paragraphs===
The code for a template need not start with any special character or symbol.  The main consideration is that the code performs the required action, just as if it were typed directly onto the page.  At the 'end of the code block, be sure to add the '''<nowiki><noinclude></noinclude></nowiki>''' tags as mentioned above.
 
All of the existing Wikitext and HTML code that can be used in a page can be used for a text template.  The user of a page does not have access to the parts associated with styles, namely the heading of the web page and their style sheets.  As a result, users are limited to modifying the parts of the page that ''are'' available, the text within the body of the page.  Those familiar with web page design will know that the only remaining available method is to modify the page's text with '''in-line styles'''.  Working methods use the '''<nowiki><div></div></nowiki>''' tags and the '''<nowiki><span></span></nowiki>''' tags, thanks to a feature of Wikitext that allows the use of HTML coding within it.  CSS, (Cascading Style Sheet), properties and values are used within these tags to modify the text styles that would otherwise apply.
 
It is as well to point out here the difference in use for '''<nowiki>span</nowiki>''' and '''<nowiki>div</nowiki>''' in text templates.  '''<nowiki>Span</nowiki>''' should be used to format text only, noting that any formats applied to the text will not extend beyond the last text character; '''<nowiki>div</nowiki>''', on the other hand, will apply its formats to a rectangular block of text that extends across the page.  the significance of this is that '''<nowiki>div</nowiki>''' is neater for changing background colors on the page.  A comparative example can be seen in the ''Classes and Styles in Tags'' section of [[Editing_Wikitext/Class_and_Style_Notes|'''Class and Style Notes''']]. 
 
 
====The Simplest Case====
Before doing any formatting, consider the method for making a template from a simple block of text.  Type a block of text, with all of its formats and page layout in place, then save the block as a template.  It is as simple as that.  Such blocks of text find use for test text, such as [[Template:Lorem_ipsum|'''Lorem Ipsum''']], a well-known text block of fictitious content used by printers and others in laying out their work.  To use such a template just type:
{{block|ff='Courier New', Courier, monospace|fs=1.1em|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{lorem ipsum}}</nowiki>}}
at any convenient place on a page to produce the text block.   This block of text is not pre formatted with hard breaks, so it will ''wrap'' within the space where it is typed, and with the ''default'' text styles of the page.   
 
 
====Adding Styles====
To ''modify'' text styles, for example, for the text '''This is the text''', we first place the text within <nowiki><span></span></nowiki> tags, like this:
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki><span>This is the text</span></nowiki>}}
Then we construct a style statement ''within'' the first tag.   This example makes the font ''Garamond'', 20 points, colored red.  It looks like this:
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki><span style="font-family:Garamond;font-size:20pt;color:red">This is the text</span></nowiki>}} 
and the result will be:
 
<center><span style="font-family:Garamond;font-size:20pt;color:red">This is the text</span></center>  
{{-}}
Notice that there is still a closing arrow for the first tag; it is located at the end of the style statement.
 
Notice also that there are three style rules in the statement, separated by semi-colons; these are ''font-family:Garamond'' to set the ''face'' of the font, ''font-size:20pt'' to set the ''size'' of the font, and ''color:red'' to set the ''color'' of the text.
 
The style statement starts with the term ''style='', and the right hand side of the statement is entirely within double quotes.
 
The individual style rules consist of a ''property''; the left part, and a ''value''; the right part.  The two parts are ''separated'' by a full colon.  The format of a style statement is strict.  If the format has an error within it then the whole statement could fail.  Note that Wikitext ''could'' have been used on the text itself; for example, to produce italics, (double quotes), or text that is bold, (triple quotes).  Wikitext acts in ''addition'' to the CSS styles, provided that there are no obvious conflicts.  Several spans and style statements can be applied to produce quite complex results.
 
These tag sets can be ''nested''; that is, one set of tags within another set.  Beware of nested '''span''' tags, since there can be unexpected results.  Say that an overall style is applied to several paragraphs using span tags.  Within these paragraphs ''another'' span set is used to format one of the paragraphs differently.  When this is viewed, at the point where the ''inside'' span closes, the styles will have reverted to the body text styles described by the style sheet, and not the intended outside style definition.  This is perhaps because the first closing tag was wrongly interpreted as the end tag.  The problem is '''avoided by using div tags for both''', or at most by '''using span tags for only one of the formats'''.   
 
Many properties exist to modify text.  They consist of all of the text styles found in style sheets, namely those for fonts, padding, alignment, margins, borders, text colors, and backgrounds. [http://www.w3schools.com/css/css_reference.asp '''CSS property lists''']  and other material on [[CSS_Programming/Fonts_and_Text|'''Fonts and Text''']] provide the source material for all such work.  Although CSS properties and examples are listed primarily for style sheets, the properties and values ''themselves'' can be used on the page and in templates.  The Study Work drop-box contains a useful code module for studying text properties.  It contains most of the useful text entries and can be copied for study into the [http://en.wikibooks.org/w/index.php?title=Wikibooks:Sandbox&action=edit '''sandbox'''].   
{{-}}
{{dropimage|align=center|cbgc=lightyellow|hbgc=lightyellow|Study Work|<b>This module contains most of the useful text properties.  Copy it into the sandbox to experiment with text property values.</b><br><pre><div style="font-family:lucida handwriting;font-weight:bold;font-style:italic;font-size:12pt;color:blue;background:papayawhip;word-spacing:0pt;letter-spacing:0pt;line-height:1.8em;border:1px solid red;margin:10pt 100pt 10pt 50pt;padding:10pt 20pt 15pt 20pt;text-align:justify;"><center>Text Property Notes</center>
 
Both PADDING and MARGIN style-rule values use the sequence TOP, RIGHT, BOTTOM, then LEFT, i.e. clockwise starting at the top.
 
BORDER uses the sequence BORDER-WIDTH, BORDER-STYLE, then BORDER-COLOR for all of the four borders at once.  Other properties can address the four separately.
 
PADDING is the space around the text.  MARGIN is the space around the text block.  BORDER is the line that surrounds the text and its padding.
 
The code block contains the common text properties.
 
Experiment with the settings. </div></pre>}}
{{-}}
{{dropimage|hbgc=lightyellow|align=center|Color Values for Study Work|[[image:pastelsRGB.jpg|911px]]<br><br>Color values for CSS properties taking a form such as : Background:RGB(255,202,149)}}
{{-}}
 
 
====Parameters====
Now, continue to make use of the ''red-text'' example.  Although the code could be saved as a template just as it is, it would not be very useful since it consists only of fixed text.  To introduce the notion of ''variable text chosen by the user'', we need to make the text position in the code into a ''parameter''. 
 
Assuming that the basic code works correctly, the ''parameter'' brackets can be added.  In the above text example there is only ''one'' parameter, the content to be formatted.  Starting with the code above, just replace the text part so that the code line now looks like this:
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki><span style="font-family:Garamond;font-size:20pt;color:red">{{{content|{{{1}}}}}}</span></nowiki>}}
Notice that the original text has now been replaced with:
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{{content|{{{1}}}}}}</nowiki>}}
The ''digit'' identifies the parameter as number one.  It is also the ''name'' of the parameter.  The word ''content'' is just a convenient label, though either the number or the label can be used for ''named parameters''.  If the user forgets to write any text in a parameter position, then the number of the parameter will appear on the page to remind of it.  If the template had ''more'' than one parameter, a similar process could be applied, with a sequence of digits 2,3,4 etc., and adding a suitable label in place of ''content'' for each.
 
Saving it in the usual way completes such a template. Assuming that the template were to be saved with the name ''BigText'' then the entry to call it for use would be just:
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{BigText|1=This is the text to format}}</nowiki>}}
Note that when a template has ''several'' parameters, the ones used can either be entered as ''named parameters'', using the number or label with an equals sign, or as ''unnamed parameters'', by omitting the added names and just entering the text directly.  The parameters should be ''all unnamed'' or ''all named'' but not a mixture of the two.  If they are ''unnamed'', the correct sequence must be maintained, and if they are ''named'', then ''any'' sequence can be used. Number names and label names ''can'' be mixed without difficulty in a template call.
 
Although virtually ''any'' tags can be modified by adding a style statement to the leading tag, it is not to say that the work can always be made into a template.  There is at least one exception that exists when it comes to making such a template.  The '''&lt;pre&gt;&lt;/pre&gt;''' tags by their very definition cause a template's parameter code to be disregarded, and a different approach is needed. Instead of attempting to make a modified pre-formatted text template consider the use of [[Template:Prettypre|Prettypre]] for a ready-made fancy version of these tags. 
 
That is to say, it is possible to modify the '''&lt;pre&gt;&lt;/pre&gt;''' tags with inline styles, to make more interesting pre-formatted text, and it is possible to add the tags to text used as a template's parameter, but making a template from text ''bounded'' by pre-formatting tags will prove more difficult.
 
 
====Options====
For completeness, we can also add ''options'' to our basic ''red-text'' template example.  Say we want to change the color of the text from time to time in our work.  We could make another complete template for the new color or we could just add an option to the text coloring code.  The new code looks like this:
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki><span style="font-family:Garamond;font-size:20pt;color:{{{tint|red}}}">{{{content|{{{1}}}}}}</span></nowiki>}}
 
Note that the entire property value (applies also to an attribute value), must be enclosed in triple curly brackets.  Additionally, the value should be replaced with an ''option name / default value'' combination. In this case, if the user does not specify the color of text, it will be ''red'' in any case.  If it is specified, (see the example below}, it can be changed to any color using the option ''tint='' within the template call.  Assuming that this template's name were ''BigText'' the template call for purple text would be, say:
{{block|ff='Courier New', Courier, monospace|fs=1.1em|<nowiki>{{BigText|tint=purple|1=My purple text goes here}}</nowiki>}}       
 
Other options could be made in the same way, and similar techniques could be used regardless of the tags used for the template.
 
A knowledge of the different tags and access to lists of CSS properties allows considerable scope in template design.
 
 


===Making Boxes===
----
----
The following sections ''make'' box or table templates from Wikitext.  They can also be made with HTML tables in the same way.    When it comes to ''making'' such a template, wikitext is fine but when a table is needed to go ''into'' a template as its parameter, or part of its parameter, an HTML table should be used instead.  The WikiBooks text [[../Tables|'''Making Tables''']] touches on HTML table structures, and explains how to use styles.  It is assumed that the reader is familiar with these concepts in the text that follows.


   
<Br>
====The Box Structure====
Boxes are essentially ''tables'', in fact table cells.  The CSS property list to format  tables is extensive.  Simple boxes make use of the table ''container'', and one or two ''cells'' within it.
 
Apart from the table container, the other structures of a table include its ''rows'', and ''cells''.  In the case below there are two rows, each with only one cell in them.  Each part of a table has properties that affect it, and an example of typical table coding can be seen in the listing below.
 
====Parameters and Options====
It is intended to provide three ''options'' along with the two ''parameters''.  The options are to be ''background'',''width'', and ''align''.  The parameter ''names'' are to be ''1'' and ''2'', with the labels ''heading'' and ''content''.
 
===Nesting templates===
Templates may contain other templates&nbsp;— this is usually called "nesting". As the template is processed, the wikitext produced by any nested templates is transcluded into the nesting template, so that the final product is essentially processed from the most deeply nested template out. While fairly straightforward in application, it involves some noteworthy quirks and tricks.


==External Links==
*[http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike License]


*[http://en.wikipedia.org/wiki/ Some parts of this page have been adapted from wikipedia]










[[Category:Template documentation]]
[[Category:Help templates]]
[[Category:BoyWiki]]

Latest revision as of 12:20, 13 April 2015


A list of BoyWiki templates can be found on Portal:Template index.

Any page whose name begins with "Template:", such as "Template:Documentation", can be used as a template. The content of a template can be added to a page by typing {{templatename}} while editing the page. When the page is later viewed, {{templatename}} is replaced by the content of the page "Template:templatename". If the page "Template:templatename" is later altered, all the pages with {{templatename}} in them will change automatically.

Amongst other things, templates are used to add recurring messages to pages in a consistent way, to add boilerplate such as template {{stub}} which indicates that the article is a fledgling.

When a template is automatically expanded and appears on a page, it is said to be "transcluded".

Templates are documented (or should be) at their pages. See Help:Template Documentation


General

Most templates are listed on Portal:Template index

Templates can contain any desired Wikitext, including calls to other templates. They have some limited programming capacities: customizable values (called parameters), calculation and branchings (using parser functions), and access to wiki-specific variables (magic words), such as dates, times, and page names. They may also contain tags which define which parts of the wikitext are to be included when the template is transcluded or substituted. This means that the appearance of the template page itself need not be the same as that of the transcluded content (for example, it can contain documentation, categories, etc. for the template).

How to do it: To transclude a template to an article or page, type {{template name}} in the wikitext at the place where the template is to appear. The prefix "Template:" need not be included, and an initial capital is not necessary.

Note: Attempting to transclude a template that does not exist produces a red link, just like linking to any other nonexistent page. Following the link allows one to create that particular template.

Also see: Help:Templates for beginners

  • TEMPLATES are just blocks of saved text that have been given names. Some are ordinary text paragraphs and some contain wikitext to make headings, indents, tables, and the like. In a simple case, by typing a template's name in the work, an entire block of text is added to the page with all of its formats and other parts, just as if it had been typed by the user. This behavior can be repeated at any point that the user wants, and almost any work that is found on a wiki page could be placed within a template to do this. The main effort as you might suppose, lies in its initial design.
  • NAMES of templates are assigned when they are first saved. The name must be unique, and it is used when a template is called for use. Sometimes other text is also used along with the name; it can include any options and parameters.
  • OPTIONS allow the user to vary the template's usual behavior.. The usual behavior suits most situations but the designer builds-in ways of changing things just in case. Option values are usually limited to a short list so these are described in a template's documentation. For example, option values for an option called align might include only left, right, or center, and no others. Templates do not always need options, since their default behavior is often enough.
  • DEFAULTS are the values used by a template when the user did not say. Default values are specified in design, and they could apply to formats or to user text inputs. For example, in the alignment example above, if the align option was not used, the template could use left, provided that left had been specified in design as its default. In the same way if the user forgets to type a text input, the template could use a pre-planned default input instead of the missing parameter; sometimes just a code to say something was forgotten.
  • PARAMETERS are usually bits of text that a user enters for a template to process. For example, if a template makes text red, it still needs to know the text to color; this text is called a parameter, and the text is included by the user when the template is called for use. Sometimes parameters contain text like code to insert an image, or even a gallery or a table; it just depends what the template is designed for. A template can even be the parameter of another template; for example, a template to insert a test paragraph might occupy the parameter space of a template to make a text box. The new paragraph would then appear in a new text box.
  • MORE GENERALLY, templates let us do much of the preparation in advance of making a page, and let us insert a block of typing, be it code to make tables, boxes, and other structures, or just a paragraph of text that is used a lot.

Usage syntax

Parameters

The basic transclusion syntax given above can be extended by the addition of parameters, which are used to control the template's output. The syntax for this is

  • {{template name|parameter|parameter|...}}

where each "parameter" may either contain just a value (these are called unnamed parameters) or be of the form name=value (named parameters). The first, second, etc. unnamed parameters are equivalent to parameters named "1", "2", etc.

Whitespace characters (spaces, tabs, returns) are stripped from the beginnings and ends of named parameter names and values, but not from the middle: thus {{ ... | myparam = this is a test }} has the same effect as {{ ... |myparam=this is a test}}. This does not apply to unnamed parameters, where the whitespace characters are preserved.

What parameters (if any) can or should be passed to a template, and how they are to be named, depends on the coding of that template. Named parameters can be defined in any order. Superfluous or misnamed parameters will be ignored; undefined parameters will be assigned default values. If a parameter is defined more than once, the last value takes effect.

The value of a parameter can be the empty string (pipe or equals sign followed immediately by the next pipe or the closing braces). This is different from leaving the parameter undefined (although templates are often coded so as to behave the same in both cases).


Other details

Template names are exactly like other page names case-sensitive except for the first letter, with spaces indistinguishable from underscores. If the symbol # (normally used to link to a section of a page) appears in a transclusion, then it and any characters that follow it are ignored.

Notice that the same double-brace syntax is used for many MediaWiki variables and parser functions (see Help:Magic words). For example, the code {{NAMESPACE}} may look like a template call, but it is actually a variable whose value is the namespace prefix of the current page.


Creating and editing templates

Templates are created and edited in much the same way as any other page: choose an appropriate name, navigate to that page, then click the Edit tab or create a new page as needed. Templates intended for your own personal use or for experimentation can be created in your own user space. Anything that can be included on a normal page or article can be included on a template, including other templates (called subtemplates). Templates often make use of programming features — parameters, parser functions and other magic words — which allow the transcluded content to vary depending on context. There are also special tags to control which information is transcluded and which is not.

Before creating a template, do a quick search for existing templates (e.g. by exploring Portal:Template index) to see if there's already a template that does what you want, or a similar template whose code can be copied and modified (or left in place and expanded). Look for generic templates on which the new template can be based (for example, navbox templates can be easily created by calling the generic Template:Navbox).

There is no hard rule about what name to choose for a template — make it short but reasonably descriptive. If similar templates exist, try to follow a consistent naming pattern. Templates can be renamed without breaking existing transclusions, provided a redirect to the new template name is left behind.

Be extremely careful when editing existing templates — changes made can affect a large number of pages, often in ways you might not expect.



System variables and conditional logic

Template code often makes use of the variables and parser functions described at Help:Magic words, in order to make the template's behaviour depend on the environment (such as the current time or namespace) or on the parameter values which are passed to it. They can also be used for arithmetical calculations. Notice that full string manipulation is not available (although templates have been created which provide such functionality, though very inefficiently and imperfectly), nor are certain standard programming features such as loops and variable assignment.

Some of the most often used variables and functions are listed hereafter. For more, see Help:Magic words.

Examples of core parser functions
Description Text entered Result
Uppercasing text {{uc: Heavens to BETSY! }} HEAVENS TO BETSY!
Lowercasing text {{lc: Heavens to BETSY! }} heavens to betsy!
Getting a namespace name {{NS: 1 }} Talk
Getting a Wikipedia URL {{fullurl: pagename }} https://www.boywiki.org/en/Pagename

The ParserFunctions extension gives more programming-oriented parser functions.

Examples of extension parser functions
Description Text Entered Result
Testing between options {{#ifeq: yes | yes | Hooray...! | Darn...! }}
{{#ifeq: yes | no | Hooray...! | Darn...! }} 		Hooray...!
Darn...!
Testing if a parameter is set {{#if: {{{param|}}} | Hooray...! | Darn...! }} Darn...!
Making a calculation (mathematics)
[area of circle of radius 4, to 3 decimal places] 		{{#expr: ( pi * 4 ^ 2 ) round 3 }} 50.265
Testing the result of a calculation
[is 1230 even or odd?] 		{{#ifexpr: 1.23E+3 mod 2 | Odd | Even }} Even
Examples of System Variables
Description Text Entered Result (for this help page)
Page names {{PAGENAME}}
{{FULLPAGENAME}} 		Templates
Help:Templates
Name of the current namespace {{NAMESPACE}} Help
Number of registered users {{NUMBEROFUSERS}} 225
Number of pages in a given category {{PAGESINCATEGORY:"Weird Al" Yankovic albums}} 0
Current software version {{CURRENTVERSION}} 1.42.1
Timestamp of last revision {{REVISIONTIMESTAMP}} 20150413122054

Text Paragraphs

The code for a template need not start with any special character or symbol. The main consideration is that the code performs the required action, just as if it were typed directly onto the page. At the 'end of the code block, be sure to add the <noinclude></noinclude> tags as mentioned above.

All of the existing Wikitext and HTML code that can be used in a page can be used for a text template. The user of a page does not have access to the parts associated with styles, namely the heading of the web page and their style sheets. As a result, users are limited to modifying the parts of the page that are available, the text within the body of the page. Those familiar with web page design will know that the only remaining available method is to modify the page's text with in-line styles. Working methods use the <div></div> tags and the <span></span> tags, thanks to a feature of Wikitext that allows the use of HTML coding within it. CSS, (Cascading Style Sheet), properties and values are used within these tags to modify the text styles that would otherwise apply.


The Simplest Case

Before doing any formatting, consider the method for making a template from a simple block of text. Type a block of text, with all of its formats and page layout in place, then save the block as a template. It is as simple as that.


Making Boxes

The following sections make box or table templates from Wikitext. They can also be made with HTML tables in the same way. When it comes to making such a template, wikitext is fine but when a table is needed to go into a template as its parameter, or part of its parameter, an HTML table should be used instead.

This WikiBooks text touches on HTML table structures, and explains how to use styles.


The Box Structure

Boxes are essentially tables, in fact table cells. The CSS property list to format tables is extensive. Simple boxes make use of the table container, and one or two cells within it.

Apart from the table container, the other structures of a table include its rows, and cells. In the case below there are two rows, each with only one cell in them. Each part of a table has properties that affect it, and an example of typical table coding can be seen in the listing below.

Parameters and Options

It is intended to provide three options along with the two parameters. The options are to be background,width, and align. The parameter names are to be 1 and 2, with the labels heading and content.

Nesting templates

Templates may contain other templates — this is usually called "nesting". As the template is processed, the wikitext produced by any nested templates is transcluded into the nesting template, so that the final product is essentially processed from the most deeply nested template out. While fairly straightforward in application, it involves some noteworthy quirks and tricks.

Examples

Here are two examples of box templates that are easy to use and are useful to those just starting out. 


{{Box1 start}}
Sample text
{{Boxes end}}
gives...

Sample text 

{{Box1 start}}
Box1 text
{{Box2 start}}
Box2 text
{{Boxes end}}
gives...

First box text

Second box text

Making a Basic Wiki Table

{|class="wikitable"
! one box
|}
gives...
one box 
{|class="wikitable"
! 
!Top row
|-
!First row
| (add some txt)
|}
gives...
Top row
First row (add some txt) 
{| class="wikitable"
!top row
!This is text
!This is more txt
!This is more txt
|-
!line1
|(add some txt)
|(add some txt)
|(add some txt)
|-
!line2
|(add some txt)
|(add some txt)
|(add some txt)
|-
!line3
|(add some txt)
|(add some txt)
|(add some txt)
|}
gives...
top row This is text This is more txt This is more txt
line1 (add some txt) (add some txt) (add some txt)
line2 (add some txt) (add some txt) (add some txt)
line3 (add some txt) (add some txt) (add some txt) 
{| class="wikitable" style="float: right;: 1em auto 1em auto;"
|+ '''(this is my table name)'''
! scope="col" | top row
! scope="col" | This is text
! scope="col" | This is text
|-
| row 1  || (add some txt) || (add some txt)
|-
| row 2 || (add some txt) || (add some txt)
|}
gives...
(this is my table name)
top row This is text This is text
row 1 (add some txt) (add some txt)
row 2 (add some txt) (add some txt)


If you float the wikitable right, you can make your text rap around the box without leaving large blank spaces on your page. This is often very useful.

(This is how a line would look.)


External Links

Retrieved from "https://www.boywiki.org/en/index.php?title=Help:Templates&oldid=22286"