__EXPECTED_UNCONNECTED_PAGE__

Usage

{{Usertalkback}} is a template intended to be placed at the very top of your user talk page, so as to inform your interlocutors of your user discussion preferences (whether you prefer to maintain discussions on a single user talk page or fragment them across two, etc.).

Its main difference with the various similar templates is that it is customizable for its content, while following the official talk page guidelines for its aspect.

Notes

  • By default, it follows the scheme of answering on the same page a discussion was started so as to avoid talk fragmentation, and notifying the other party with the {{Talkback}} template, but options allow to express other preferences.
  • Contrary to a lot of similar templates that use various color schemes, this one follows the official guideline on talk page boxes and will self-adapt to your interlocutor's skins.
  • Optionally, you can also duplicate this template at the very top of your user page.
  • Preferably, do not subst: this template in order to automatically benefit from its improvements.

Options

For each option, the default value is displayed in bold and automatically assumed if the field is left blank.

you
Explain what you should do if I left you a message:
  • talkback : please answer on your talk page, then place {{Talkback}} on my talk.
  • notify : please answer on your talk page, then notify my talk page.
  • notifications : please answer on your talk page, linking to me ({{Ping}}), so I will be notified.
  • watched : please answer on your talk page, as I am watching it.
  • watchtb : please answer on your talk page, as I am watching it. If I have been active and have not yet responded, please place {{Talkback}} on my page as I may have missed your response.
  • other : please answer on my talk page, else inform me.
me
Explain what I will do if you leave me a message:
  • talkback : I will answer on my talk page, then place {{Talkback}} on your talk.
  • notify : I will answer on my talk page, then notify your talk page.
  • notifications : I will answer on my talk page, linking to your username, so you will be notified.
  • watched : I will answer on my talk page, so please add it to your watchlist.
  • watchtb : I will answer on my talk page, so please add it to your watchlist. If I notice that you have been active but have not responded, I may place {{Talkback}} on your page in case you have missed my response.
  • other : I will answer on your talk page, unless you request otherwise.

The value of "you" and "me" do not necessarily have to be the same, but should of course be consistent: either you chose both "other" (for suggesting discussions fragmented across both talk pages), or you chose a combination of the three first values (for suggesting discussions that stay on the page they started, and how the other party will know that you answered).

hint
Defines if the mandatory parameters for the talkback template should be shown:
  • yes : the usage examples are included, such as {{Talkback|your username}}.
  • no : only the short references to {{Talkback}} are provided.
small
Define the size and position of the box:
  • no : the regular sized centered box is used.
  • yes : the template will shrink to a small, right-aligned floating box.
runon
Defines how the three sentences are displayed:
  • no : as two bullet items and a clickable button.
  • yes : as runon text.
icon
Selects an optional icon for the left side:
  • none : keeps maximum space to prevent lines wrapping. (On a standard 1024 display with average browser fontsize, adding an icon can make the three sentences wrap to six lines on your interlocutors' screen).
  • blank : File:No image.svg (empty icon-sized placeholder)
  • plus : File:B plus.svg (plus, add new message)
  • lang : File:Gaim send-im.svg (language, talk)
  • info : File:Info talk.png (for your information)
  • attn : (attention please)
  • stop : (stop, warning)
  • frag : (fragmented discussion)
  • anyfile.img : any valid image filename.
iconalt
Defines the icon's alternative text (displayed in text-only, or as tooltip):
  • User talk : default short and relevant text.
  • Any text : should satisfy text-only browsers and the blind.
iconcell
Defines the attribute or CSS style of the icon's table cell:
  • [none] : put the icon in the middle of its column
  • valign=top : put the icon at the top of its column
  • valign=bottom : put the icon at the bottom of its column
iconsize1
Defines the size of the icon when in regular mode:
iconsize2
Defines the size of the icon when in small mode:
hidenew
Defines if the "Leave me a new message" line will be hidden:
  • no : normal mode at the top of a user/talk page.
  • yes : advanced use inside User:YourName/editintro (see #Editintro below).

Most values are case-insensitive ("watched" or "WAtChEd" work the same), except when it matters (such as a custom icon filename).

Examples

  • The regular version (with default values) can be seen at the top of this page.
  • The {{Usertalkback|small=yes}} version (with default values) can be seen at the right side of this section. It is inserted at the top of the section, just below the heading and before this bullet list. The text that follows will wrap next to it. In this version, the items of the regular version are merged into a single sentence, without the bullets. Just below is the code {{Usertalkback|you=other|me=other |small=yes|runon=yes |icon=frag|iconcell=valign=bottom}} for a fragmented discussion preference. (You can skip the two next paragraphs, they are a dummy Latin text for showing how text flow around the small template.)
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Curabitur pretium tincidunt lacus. Nulla gravida orci a odio. Nullam varius, turpis et commodo pharetra, est eros bibendum elit, nec luctus magna felis sollicitudin mauris. Integer in mauris eu nibh euismod gravida. Duis ac tellus et risus vulputate vehicula. Donec lobortis risus a elit. Etiam tempor. Ut ullamcorper, ligula eu tempor congue, eros est euismod turpis, id tincidunt sapien risus a quam. Maecenas fermentum consequat mi. Donec fermentum. Pellentesque malesuada nulla a mi. Duis sapien sem, aliquet nec, commodo eget, consequat quis, neque. Aliquam faucibus, elit ut dictum aliquet, felis nisl adipiscing sapien, sed malesuada diam lacus eget erat. Cras mollis scelerisque nunc. Nullam arcu. Aliquam consequat. Curabitur augue lorem, dapibus quis, laoreet et, pretium ac, nisi. Aenean magna nisl, mollis quis, molestie eu, feugiat in, orci. In hac habitasse platea dictumst.

Editintro

This is a special case for advanced users: note this only works when |runon=yes.

  • The "&editintro=" option of wiki URLs allows to customize the text that will appear above the inputbox in edit mode. If you create a user subpage at User:YourName/editintro (all-lowercase "editintro"), the template will autodetect it and use it as the editintro for its "Leave me a new message" link. However, a user can set the editintro page manually using the "editintro" parameter. Regardless of which technique is used, the template will check if the page exists before including it as the editintro.
  • If you wish, you can also reuse a copy of the template in your /editintro subpage. The only change is to add the option "hidenew=yes". This is not required, but cosmetic: for someone who is already in edit mode to write you a message, it'd look silly to show him again a "Leave me a new message" link, so the option will hide it for your editintro.
  • More importantly, if you use elsewhere on Wikipedia a direct link to "create a new message on my talk page", the person using it would bypass your talk page and not see your user discussion preferences. The copy of the template in your editintro remedy this.
  • This would be even more useful in the future if it becomes possible to make such a link in the custom user signature. (Currently, external URLs are forbidden, and wiki markup does not seem to allow using the special options without an external URL.)
  • Example of such a link, code and result:
<SPAN CLASS="plainlinks">[https://en.wikipedia.org/w/index.php?title=User_talk:Komusou&action=edit&section=new&editintro=User:Komusou/editintro Leave a new message to Komusou.]</SPAN>
Leave a new message to Komusou.

Technical

Before changing the template's code or text, please bear in mind some points that should be preserved:

  • The box follows the standards from the Wikipedia:Talk page templates guideline (such as the mandated background color, width, small= implementation, icon size, etc.), which automatically derive from a class that will self-adapt to each user's skin. The visual aspects and colors should thus not be changed, because it would hardcode colors that may look good on your own skin but could be poor on the screen of people using other skins.
  • The template is designed so that you can also place it on your user page (if wanted) in addition to your talk page, and it stays functional, that is:
    • The new message URL is constructed with TALKPAGENAME so as to work in both cases.
    • The texts say "on my talk page" rather than "here" so as to be valid in both cases.
  • The template is designed to have three short sentences that stay on a single line each, on as many screen configuration as possible:
    • The icon has been removed by default on purpose to limit line wraps.
    • The sentences have been kept concise rather than verbose.

See also

  • {{Talkback}} – the original, large "you have new messages" notice to put on other users' talk pages
    • {{subst:Mytalk}} – invokes the talkback template and automatically fills in your username
    • {{Talkbacktiny}} – a somewhat smaller version of {{Talkback}}
  • {{Interwiki talkback}} – a "you have new messages" notice to put on other users' talk pages for interwiki purposes
  • {{Whisperback}} – a less obtrusive template than {{Talkback}}, with more features and without the box
  • {{You've got mail}} – like {{Talkback}} but to notify of an offsite e-mail
  • {{Please see}} – similar to {{Whisperback}}, but notifying others of a topic they may wish to participate in
  • {{Discussion notice}} – an alternative to {{Please see}}, similar to {{ANI-notice}}
  • {{Usertalkback}} and {{Userwhisperback}} – notices for the top of one's own user talk page, so as to inform your interlocutors of your user discussion preferences
  • {{FYI}} – icon box to give a visual hint to readers of talk page items
  • {{Notified}} – disclosure indicating that a notification has been posted on another page
  • {{Reply to}} – ping a user without posting on their talk page (uses the mentions notification)
  • {{Response}} – to direct the attention of another user to a discussion on a specific talk page
  • {{No talkback}} – opt-out of talkback messages from Twinkle
Template:Usertalkback invokes Module:Navbox using Lua.

Usage

This template can be used to make a standard navigation box. It is intended for use within another template that standardises the title and contents of the box (see Template:ShipNavbox). This template SHOULD NOT be used directly within articles, as it creates a maintenance burden to do so whenever the contents of the box have to be updated.

The purpose of this template is to standardise the attributes of all navigation boxes, for example, their colours and other CSS attributes. The template is fairly simple, and could be extended to add other features in the future. Using this template allows changes to be implemented much quicker and easier than editing each template separately.

Syntax

{{navbox
|state      = uncollapsed, collapsed, plain, autocollapse (default)
|name       = mandatory - name of the template
|style      = optional - style for the whole table
|title      = mandatory - navbox header
|gtitleN    = optional - title of N-th group of items
|styleN     = optional - style for groupN; i.e. text-align
|groupN     = mandatory - list of groups of items
|fstyle     = optional - style for footer ; i.e. text-align
|footer     = optional - navbox footer
}}
  • Groups: Currently there is no technical limit to the maximum number of groups.
    • Groups of items can be added as parameters: group1, group2, group3, ... up to groupN.
  • Group title: Each group has its own title parameter: gtitle1, gtitle2, gtitle3, ... up to gtitleN. Note that the default width for the first column is 15%.
  • Group style: Style may also be customised to each group in: style1, style2, style3, ... up to styleN.
    • Note that neither the title nor the items have any wiki-links built into the template. As a result, users of the template are free to use wiki-links as they wish.
  • Line breaks: Line-breaks (<br />) are unnecessary, as text wrapping is done automatically by the template. This also includes links and text in gtitleN and groupN.
  • Bullets: Create unordered lists with lines beginning with *.
  • Pipe links: Because of the nature of template syntax, it may be necessary to use Template:! ({{!}}).

States

  • Autocollapse: By default, the state of a navbox is "autocollapsed". This means that if the number of navboxes in a page exceeds the maximum allocation of the collapsible navboxes, then the remaining navboxes are collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
    • Currently, the autocollapse allocation is 2 (see MediaWiki:Common.js). This means that if there are 3 navboxes in a page, the third and subsequent navboxes will be collapsed automatically.
  • Uncollapsed: Forces the navbox to be displayed.
    • All of the navboxes in this documentation are in the uncollapsed state.
  • Collapsed: The reverse of uncollapsed. Forces the navbox to be hidden instead.
    • Navboxes with a height of more than 300 pixels will also be collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
  • Plain: Removes the "show/hide" link.

Sub-groups

  • For larger navboxes, it may be necessary to include sub-groups within a particular group of items. It is also possible to collapsible navboxes within the parent navbox, see Collapsible sub-groups.
  • To create sub-groups within {{navbox}}, certain parameters are to be included:
    • The parent navbox group (i.e. group2 in the example below) requires the type parameter (gtype2 = Subgroup).
    • The nested navbox (sub-group) requires the inclusion of the sub-group parameter (subgroup = yes). This enables the template to differentiate between the sub-group and the parent navbox.
{{navbox
|name    =
|title   =
|gtitle1 =
|group1  =
|gtitle2 =  
|gtype2  = Subgroup (mandatory)
|group2  = 
  {{navbox
  |subgroup = yes (mandatory)
  |gtitle1  = 
  |group1   =
  |gtitle2  = 
  |group2   = 
  }}
}}

Collapsible sub-groups

  • For extremely long navboxes, it is recommended to use collapsible navboxes within the parent navbox. Further sub-groups can then be added to these collapsible navboxes.
  • To create collapsible sub-groups within {{navbox}}, these parameters need to be included:
    • The parent navbox is almost always uncollapsed (state=uncollapsed).
    • The parent navbox group (i.e. group1 in the example below) requires the type parameter (gtype1 = Subgroup).
    • The nested collapsible navbox requires the inclusion of the collapsible parameter (collapsible = yes). This enables the template to differentiate between the collapsible navbox and the parent navbox.
    • The nested collapsible navbox is forcefully collapsed (state=collapsed).
{{navbox
|state  = uncollapsed
|name   = 
|gtype1 = Subgroup
|group1 = 
  {{navbox
  |collapsible = yes
  |state   = collapsed
  |title   = 
  |gtitle1 = 
  |group1  = 
  |gtitle2 = 
  |group2  = 
  }}
}}

Use of images

  • The use of images in navboxes is permitted, but please resize the images to keep them small. Inventory-sized images (25-30 pixels) are recommended.
  • Please use {{t|plink}} to create links with images. Use {{t|plink}} for any case where text is not desired after the link. It functions the same as {{t|plink}}, but it does not produce a wikilink in text. Use {{t|chatl}} to link chatheads. These templates create links for both the image and text (except for {{t|plink}}) using far less wikicode than the standard syntax.

Link and file share the same name

{{plink|Item}}

File name differs from the link

{{plink|Item|File}}

Link and file share the same name, but different text is desired to display

{{plink|Item|alt=Text}}

File name differs from the link and different text is desired to display

{{plink|Item|File|alt=Text}}

Categorising

Navboxes are very useful for transcluding categories onto a large number of pages that share both a trait and the navigation box. For example: Template:ShipNavbox transcludes Category:Ships onto every page that uses it.

There are 2 methods of categorising pages with navboxes:

The first way is with {{t|Ctg}}. This is the preferred method, and can be used in most cases. The rules and operations for the Category handler template are very simple; however, they are enough to produce the desired results on most pages.

Categorisation should only be used on a template for large-scale addition. It is unhelpful, for example, to use a rule that only applies to 1 page.

Examples

To see the following navboxes in action, see Template:Navbox.

Single line navbox with centered list

{{navbox
|name    = 
|title   = 
|style1  = text-align:center
|group1  =
}}
{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|footer  = Centered footer
}}
{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|fstyle  = text-align:right
|footer  = Right-aligned footer
}}

Multiple line navbox

{{navbox
|name    = 
|title   = 
|gtitle1 = Group title 1
|group1  = 
|gtitle2 = Group title 2
|group2  = 
|gtitle3 = Group title 3
|group3  = 
}}

Collapsed navbox

{{navbox
|state   = collapsed
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox with Tnavbar

{{navbox
|state   = plain
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox without Tnavbar

{{navbox
|state   = plain
|title   = 
|style1  = text-align:center
|group1  = 
}}

Complicated navbox

{{navbox
|state   = uncollapsed
|name    = 
|title   = 
|gtitle1 = Level 1 Title 1
|group1  = 
|gtitle2 = Level 1 Title 2
|group2  = 
|gtitle3 = Level 1 Title 3
|group3  = 
|gtitle4 = Level 1 Title 4
|group4  = 
|gtitle5 = Level 1 Title 5
|gtype5  = Subgroup
|group5  = 
  {{navbox
  |subgroup = Yes
  |gtitle1  = Level 2 Title 1
  |group1   =
  |gtitle2  = Level 2 Title 2
  |group2   =
  |gtitle3  = Level 2 Title 3
  |gtype3   = Subgroup
  |group3   = 
    {{navbox
    |subgroup = Yes
    |gtitle1  = Level 3 Title 1
    |group1   =
    |gtitle2  = Level 3 Title 2
    |group2   =
    }}
  |gtitle4  = Level 2 Title 4
  |group4   = 
  }}
|gtitle6 = Level 1 Title 6
|group6  = 
|gtitle7 = Level 1 Title 7
|group7  = 
|fstyle  = 
|footer  = 
}}

Preventing unwanted documentation

The Navbox template's documentation is automatically transcluded under the navbox on any Template namespace page. It is not transcluded when used as a sub-group or collapsible sub-group template (subgroup= yes or collapsible=yes).

Should the documentation appear when it is unwanted, it can be hidden by setting the doc parameter doc=no on the template. In most cases, the doc parameter is NOT used and the parameter is removed completely.


Template:Usertalkback invokes Module:Navbox using Lua.

Usage

This template can be used to make a standard navigation box. It is intended for use within another template that standardises the title and contents of the box (see Template:ShipNavbox). This template SHOULD NOT be used directly within articles, as it creates a maintenance burden to do so whenever the contents of the box have to be updated.

The purpose of this template is to standardise the attributes of all navigation boxes, for example, their colours and other CSS attributes. The template is fairly simple, and could be extended to add other features in the future. Using this template allows changes to be implemented much quicker and easier than editing each template separately.

Syntax

{{navbox
|state      = uncollapsed, collapsed, plain, autocollapse (default)
|name       = mandatory - name of the template
|style      = optional - style for the whole table
|title      = mandatory - navbox header
|gtitleN    = optional - title of N-th group of items
|styleN     = optional - style for groupN; i.e. text-align
|groupN     = mandatory - list of groups of items
|fstyle     = optional - style for footer ; i.e. text-align
|footer     = optional - navbox footer
}}
  • Groups: Currently there is no technical limit to the maximum number of groups.
    • Groups of items can be added as parameters: group1, group2, group3, ... up to groupN.
  • Group title: Each group has its own title parameter: gtitle1, gtitle2, gtitle3, ... up to gtitleN. Note that the default width for the first column is 15%.
  • Group style: Style may also be customised to each group in: style1, style2, style3, ... up to styleN.
    • Note that neither the title nor the items have any wiki-links built into the template. As a result, users of the template are free to use wiki-links as they wish.
  • Line breaks: Line-breaks (<br />) are unnecessary, as text wrapping is done automatically by the template. This also includes links and text in gtitleN and groupN.
  • Bullets: Create unordered lists with lines beginning with *.
  • Pipe links: Because of the nature of template syntax, it may be necessary to use Template:! ({{!}}).

States

  • Autocollapse: By default, the state of a navbox is "autocollapsed". This means that if the number of navboxes in a page exceeds the maximum allocation of the collapsible navboxes, then the remaining navboxes are collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
    • Currently, the autocollapse allocation is 2 (see MediaWiki:Common.js). This means that if there are 3 navboxes in a page, the third and subsequent navboxes will be collapsed automatically.
  • Uncollapsed: Forces the navbox to be displayed.
    • All of the navboxes in this documentation are in the uncollapsed state.
  • Collapsed: The reverse of uncollapsed. Forces the navbox to be hidden instead.
    • Navboxes with a height of more than 300 pixels will also be collapsed automatically. For more information (or to change the setting), see MediaWiki:Common.js.
  • Plain: Removes the "show/hide" link.

Sub-groups

  • For larger navboxes, it may be necessary to include sub-groups within a particular group of items. It is also possible to collapsible navboxes within the parent navbox, see Collapsible sub-groups.
  • To create sub-groups within {{navbox}}, certain parameters are to be included:
    • The parent navbox group (i.e. group2 in the example below) requires the type parameter (gtype2 = Subgroup).
    • The nested navbox (sub-group) requires the inclusion of the sub-group parameter (subgroup = yes). This enables the template to differentiate between the sub-group and the parent navbox.
{{navbox
|name    =
|title   =
|gtitle1 =
|group1  =
|gtitle2 =  
|gtype2  = Subgroup (mandatory)
|group2  = 
  {{navbox
  |subgroup = yes (mandatory)
  |gtitle1  = 
  |group1   =
  |gtitle2  = 
  |group2   = 
  }}
}}

Collapsible sub-groups

  • For extremely long navboxes, it is recommended to use collapsible navboxes within the parent navbox. Further sub-groups can then be added to these collapsible navboxes.
  • To create collapsible sub-groups within {{navbox}}, these parameters need to be included:
    • The parent navbox is almost always uncollapsed (state=uncollapsed).
    • The parent navbox group (i.e. group1 in the example below) requires the type parameter (gtype1 = Subgroup).
    • The nested collapsible navbox requires the inclusion of the collapsible parameter (collapsible = yes). This enables the template to differentiate between the collapsible navbox and the parent navbox.
    • The nested collapsible navbox is forcefully collapsed (state=collapsed).
{{navbox
|state  = uncollapsed
|name   = 
|gtype1 = Subgroup
|group1 = 
  {{navbox
  |collapsible = yes
  |state   = collapsed
  |title   = 
  |gtitle1 = 
  |group1  = 
  |gtitle2 = 
  |group2  = 
  }}
}}

Use of images

  • The use of images in navboxes is permitted, but please resize the images to keep them small. Inventory-sized images (25-30 pixels) are recommended.
  • Please use {{t|plink}} to create links with images. Use {{t|plink}} for any case where text is not desired after the link. It functions the same as {{t|plink}}, but it does not produce a wikilink in text. Use {{t|chatl}} to link chatheads. These templates create links for both the image and text (except for {{t|plink}}) using far less wikicode than the standard syntax.

Link and file share the same name

{{plink|Item}}

File name differs from the link

{{plink|Item|File}}

Link and file share the same name, but different text is desired to display

{{plink|Item|alt=Text}}

File name differs from the link and different text is desired to display

{{plink|Item|File|alt=Text}}

Categorising

Navboxes are very useful for transcluding categories onto a large number of pages that share both a trait and the navigation box. For example: Template:ShipNavbox transcludes Category:Ships onto every page that uses it.

There are 2 methods of categorising pages with navboxes:

The first way is with {{t|Ctg}}. This is the preferred method, and can be used in most cases. The rules and operations for the Category handler template are very simple; however, they are enough to produce the desired results on most pages.

Categorisation should only be used on a template for large-scale addition. It is unhelpful, for example, to use a rule that only applies to 1 page.

Examples

To see the following navboxes in action, see Template:Navbox.

Single line navbox with centered list

{{navbox
|name    = 
|title   = 
|style1  = text-align:center
|group1  =
}}
{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|footer  = Centered footer
}}
{{navbox
|name    = 
|title   = 
|gtitle1 = 
|group1  = 
|fstyle  = text-align:right
|footer  = Right-aligned footer
}}

Multiple line navbox

{{navbox
|name    = 
|title   = 
|gtitle1 = Group title 1
|group1  = 
|gtitle2 = Group title 2
|group2  = 
|gtitle3 = Group title 3
|group3  = 
}}

Collapsed navbox

{{navbox
|state   = collapsed
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox with Tnavbar

{{navbox
|state   = plain
|name    = 
|title   = 
|style1  = text-align:center
|group1  = 
}}

Plain navbox without Tnavbar

{{navbox
|state   = plain
|title   = 
|style1  = text-align:center
|group1  = 
}}

Complicated navbox

{{navbox
|state   = uncollapsed
|name    = 
|title   = 
|gtitle1 = Level 1 Title 1
|group1  = 
|gtitle2 = Level 1 Title 2
|group2  = 
|gtitle3 = Level 1 Title 3
|group3  = 
|gtitle4 = Level 1 Title 4
|group4  = 
|gtitle5 = Level 1 Title 5
|gtype5  = Subgroup
|group5  = 
  {{navbox
  |subgroup = Yes
  |gtitle1  = Level 2 Title 1
  |group1   =
  |gtitle2  = Level 2 Title 2
  |group2   =
  |gtitle3  = Level 2 Title 3
  |gtype3   = Subgroup
  |group3   = 
    {{navbox
    |subgroup = Yes
    |gtitle1  = Level 3 Title 1
    |group1   =
    |gtitle2  = Level 3 Title 2
    |group2   =
    }}
  |gtitle4  = Level 2 Title 4
  |group4   = 
  }}
|gtitle6 = Level 1 Title 6
|group6  = 
|gtitle7 = Level 1 Title 7
|group7  = 
|fstyle  = 
|footer  = 
}}

Preventing unwanted documentation

The Navbox template's documentation is automatically transcluded under the navbox on any Template namespace page. It is not transcluded when used as a sub-group or collapsible sub-group template (subgroup= yes or collapsible=yes).

Should the documentation appear when it is unwanted, it can be hidden by setting the doc parameter doc=no on the template. In most cases, the doc parameter is NOT used and the parameter is removed completely.