ᥗᥦᥛᥰ ᥙᥣ ᥘᥥᥐᥳ:Format TemplateData/doc

Everything below this line is a demo of Format TemplateData: read the source code, and expand the raw TemplateData section, to see how it all works.

ᥘᥩᥒᥲᥓᥬᥳᥖᥪᥰ

ᥑᥩᥲ ᥛᥧᥢᥰ ᥓᥫᥰ ᥚᥣᥭᥱ ᥖᥬᥲ ᥢᥭᥳ ᥙᥥᥢᥴ ᥖᥨᥝᥴ ᥗᥖᥰ ᥖᥣᥴ ᥞᥢᥴ(VisualEditor) ᥟᥢᥴ ᥛᥤᥰ ᥖᥤᥲ ᥝᥤᥱ ᥑᥤᥱ ᥚᥤᥰᥖᥤᥰ ᥕᥣᥰ ᥢᥢᥳ ᥕᥫᥒᥰ ᥟᥣᥢᥰ ᥖᥣᥱ ᥟᥝᥴ ᥑᥫᥒᥲ ᥓᥫᥰ ᥢᥢᥳ ᥓᥬᥳ ᥘᥭᥲ ᥖᥤᥲ ᥝᥤᥱ ᥑᥤᥱ ᥚᥤᥰ ᥖᥤᥰ ᥕᥣᥰ ᥖᥭᥰ ᥔᥥᥴ ᥓᥒᥱ ᥘᥭᥲ ᥟᥝᥴ ᥙᥫᥒᥴ ᥑᥩᥲ ᥛᥧᥢᥰ ᥗᥦᥛᥰ ᥙᥘᥥᥐᥳ (TemplateData) ᥟᥢᥴ ᥛᥤᥰ ᥖᥤᥲ ᥝᥤᥱ ᥑᥤᥱ ᥚᥤᥰ ᥖᥤᥰ ᥕᥣᥰ ᥟᥤᥒᥰ ᥐᥘᥥᥖᥲ ᥢᥢᥳ ᥞᥥᥖᥰ ᥝᥭᥳ ᥙᥥᥢᥴ ᥖᥤᥲ ᥛᥣᥭᥴ ᥖᥤᥲ ᥖᥩᥒᥰ ᥕᥝᥳ။ ᥞᥨᥛᥲ ᥝᥣᥲ ᥙᥭᥱ ᥓᥬᥳ ᥑᥫᥒᥲ ᥓᥫᥰ ᥢᥢᥳ ᥔᥥᥴ ᥖᥣᥳ ᥙᥩᥰ ᥙᥥᥢᥴ ᥐᥨᥢᥰ ᥞᥧᥳ ᥘᥩᥒᥲ ᥖᥦᥛᥲ ᥙရᥨᥝᥱ ᥐᥦᥛᥱ (computer programming) ᥟᥤᥖᥰ ᥟᥩᥖᥰ ᥐᥩᥲ ᥞᥬᥲ ᥙᥩᥰ ᥞᥢᥴ ᥘᥭᥲ ᥓᥦᥒᥲ ᥘᥦᥒᥰ ᥘᥤᥴᥢᥭᥴ ᥔᥥᥴ ᥓᥣᥒᥲ ᥟᥝᥴ ᥓᥬᥳ ᥘᥭᥲ ᥔᥚᥩᥰ ᥖᥤᥲ ᥐᥦᥙᥲ ᥛᥢᥰ ᥘᥭᥲ ᥕᥧᥱ.

Format TemplateData

This template formats TemplateData nicely on doc pages. It hides irrelevant information such as "Default: empty", and allows the use of formatting. Remember that the users of VisualEditor will not see this formatting; it is important to test your new TemplateData in VisualEditor to check that it makes sense without. (For all details of formatting available, see the template's page.) By default, {{TemplateData header}} is automatically inserted before the table.

Parameter		Description	Type	Status
<templatedata> template information	1	If the JSON and TNT parameters are not specified, this will be processed to extract the JSON. This option allows you to use the GUI TemplateData Editor, but it's a bit wonkier than giving the actual JSON object directly. Default See {{{JSON}}}.	String	optional
JSON template information	JSON	The code that would normally be wrapped in <templatedata> tags (not including the <templatedata> tags themselves. Links and basic text formatting should just work in the displayed table; see this template's page for full details. You should use HTML entities for special characters such as <>. Formatting options Wikilinks can be specified in the usual way. They will only work in the table; in VisualEditor, the title of the link will be displayed as plain text. External links can be specified by just inserting the URL; this will be clickable in the table and viewable in VisualEditor. If the URL is specified as [https://en.wikipedia.org Wikipedia], this will appear as Wikipedia in the table and https://en.wikipedia.org in VisualEditor. HTML entities: you may specify &lt; &gt; &amp; &quot; &nbsp; and any numeric entity.*HTML tags may be used; they won't appear in VisualEditor. <noexport></noexport> Content wrapped in these tags will appear only in the table. It will not appear in VisualEditor at all; it is useful for detailed explanations of parameters, and for content that is only useful with formatting. Newline characters are respected here. Templates may be transcluded. However some templates may output content that makes the JSON invalid. Default If neither {{{1}}}, {{{JSON}}}, nor {{{TNT}}} is given, the page's source code is scanned for a <templatedata> tag.	String	suggested
Show table of contents	TOC	If set to 1, inserts a table of contents for the whole page just after the description and before any parameter table. Default False 0	Boolean	suggested
Show TemplateDataHeader	header	If set to 0, hides the {{TemplateData header}} template. This is not generally recommended. Default True 1	Boolean	optional
Prevent TemplateData output	lazy	If set, other than to 0, prevents any real TemplateData being produced. Potentially useful if there are multiple instances of this template on a page but only one should be active. To clarify, this means that this template will not be understood by VisualEditor. Default False 0	Boolean	optional

Format: block

ᥘᥩᥒᥲᥓᥬᥳᥖᥪᥰ ᥗᥦᥛᥰᥙᥘᥥᥖᥳ

Add the <templatedata> as usual, and then enclose it in a template call like {{Format TemplateData|1=<templatedata>...</templatedata>}}.

Maintenance categories

• Category:Templates with TemplateData errors (0) – the template adds this category to template documentation pages with malformed TemplateData code.