ထႅမ်းပလဵတ်ႉ:documentation
- The following documentation is located at ထႅမ်းပလဵတ်ႉ:documentation/documentation. [edit]
- Useful links: subpage list • links • redirects • transclusions • errors (parser/module) • sandbox
Uses Lua: |
This template automatically displays a documentation box like you are seeing now, of which the content is transcluded from another page. It is intended for pages which are transcluded in other pages, i.e. templates, whether in the template namespace or not.
လွင်ႈၸႂ်ႉတိုဝ်း
[မႄးထတ်း]template code ...<noinclude>
Lua error in မေႃႇၵျူး:parameters at line 600: attempt to index local 'param' (a boolean value).</noinclude>
or
<onlyinclude>
template code . . .</onlyinclude>
Lua error in မေႃႇၵျူး:parameters at line 600: attempt to index local 'param' (a boolean value).
The most common practice is to place the Lua error in မေႃႇၵျူး:parameters at line 600: attempt to index local 'param' (a boolean value). template in <noinclude>
tags. Alternatively, the template code itself can be wrapped in <onlyinclude>
tags and the Lua error in မေႃႇၵျူး:parameters at line 600: attempt to index local 'param' (a boolean value). template should be outside of those tags. Both of these methods ensure that the documentation is not transcluded onto other pages as part of the template.
If the template itself should be placed in a category, or should have interwiki links, those should be placed on the documentation page, inside <includeonly>
tags. If the documentation page contains includeonly or noinclude tags as part of the documentation, use Lua error in မေႃႇၵျူး:parameters at line 600: attempt to index local 'param' (a boolean value). or replace <
with <
.
ၾင်ႇသျိၼ်ႇ
[မႄးထတ်း]If the documentation page doesn't exist, the "edit" link includes a preload parameter so that clicking it will pre-fill the edit form with a stub documentation page.
Rationale
[မႄးထတ်း]Use of this template allows templates to be protected where necessary, while allowing anyone to edit the documentation, categories, and interwiki links. In addition, modules strictly require documentation pages as they cannot be categorized or documented any other way, so it makes sense to handle templates likewise.