Jump to content

Inyandikorugero:documentation/documentation

Kubijyanye na Wiktionary

Inyandikorugero:documentation subpage Inyandikorugero:uses lua

This template automatically displays a documentation section like you are seeing now. The content of this section comes from a subpage named Inyandikorugero:cd; e.g. the documentation for Template:affix is located on the page named Inyandikorugero:cd. In order for this documentation to be displayed, templates must manually invoke Tagalog inside of a Inyandikorugero:cd section; see #Usage below. (However, Tagalog is automatically invoked on module and JavaScript pages. The mechanism implementing this is described in more detail in the documentation for Module:documentation, which implements the Tagalog template.)

Usage

[hindura]
template code
...Inyandikorugero:wt{{documentation}}Inyandikorugero:wt

or

Inyandikorugero:wttemplate code . . .Inyandikorugero:wt
{{documentation}}

The most common practice is to place the {{documentation}} template in Inyandikorugero:wt tags. Alternatively, the template code itself can be wrapped in Inyandikorugero:wt tags and the {{documentation}} 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.

In order to place the template itself in a category, or supply interwiki links, put those categories and interwiki links on the documentation page, inside Inyandikorugero:wt tags. If the documentation page contains Inyandikorugero:wt or Inyandikorugero:wt tags as part of the documentation, use Tagalog or replace Inyandikorugero:cd with Inyandikorugero:cd.

Functions

[hindura]

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

[hindura]

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.

See also

[hindura]