Help:TemplateData

From MediaWiki.org
Jump to: navigation, search
This page is a translated version of the page Help:TemplateData and the translation is 34% complete.

Other languages:
asturianu • ‎azərbaycanca • ‎български • ‎বাংলা • ‎català • ‎dansk • ‎Deutsch • ‎Zazaki • ‎Ελληνικά • ‎emiliàn e rumagnòl • ‎English • ‎español • ‎euskara • ‎فارسی • ‎suomi • ‎føroyskt • ‎français • ‎Frysk • ‎galego • ‎hrvatski • ‎magyar • ‎Հայերեն • ‎Bahasa Indonesia • ‎Ilokano • ‎italiano • ‎日本語 • ‎ქართული • ‎한국어 • ‎Lëtzebuergesch • ‎lietuvių • ‎मराठी • ‎Nederlands • ‎occitan • ‎Oromoo • ‎polski • ‎پښتو • ‎português • ‎português do Brasil • ‎русский • ‎Scots • ‎slovenščina • ‎svenska • ‎українська • ‎Tiếng Việt • ‎ייִדיש • ‎中文
PD Note : lorsque vous modifiez cette page, vous acceptez de placer votre contribution sous licence CC0. Plus d'informations sont disponibles sur les pages d'aide du projet domaine public.
PD

Qu'est-ce que TemplateData ?

TemplateData est un moyen de stocker des informations au sujet d'un modèle et des ses paramètres, de manière à ce que l'ÉditeurVisuel puisse les récupérer et les afficher dans le gestionnaire de modèles, rendant ainsi plus facile la modification de modèles.

La syntaxe TemplateData permet aux utilisateur d'écrire de petits morceaux de données structurées dans une page de modèle, ou à transclure dans une page de modèle (par exemple sur sur la page de documentation d'un modèle). Une fois qu'un modèle a ces données structurées, il peut être affiché correctement dans l'ÉditeurVisuel. Bien que cela puisse sembler compliqué, c'est en fait très simple.

Éditeur de données TemplateData

Il y a un outil intégré pour modifier les TemplateData de façon simple.

Pour utiliser l'éditeur TemplateData, allez dans la page du modèle (ou dans sa sous page de documentation) et cliquez sur le bouton "Edit". Ceci fera apparaître un bouton nommé "Manage TemplateData", juste au dessus de la fenêtre ouverte d'édition :

Manage template documentation button for TemplateData 2014.png

Appuyez sur ce bouton pour entrer dans l'outil d'interface utilisateur pour l'édition des TemplateData.

A screenshot of the TemplateData editing tool

The editor allows you to add one row per template parameter and to set the most common attributes. If the page you edited already contains a block of TemplateData, then the information already documented will automatically be shown when you open the correct page in the TemplateData editor. In the first box, you can add or update a short description of the template in plain text. After that, you can use the "Import parameters" and "Add parameters" buttons to document the names and attributes of the parameters that the template uses. You can list the name of the parameter, any aliases for it, the label and the description that will display to users. The only required field is Name (the first field in each row), which is where you record the exact, case-sensitive name of the parameter. In the pop-up menu, you can choose the type of content that the parameter should receive, such as a string (for plain-text answers), page (for links to other pages), or dates. If the template will produce an error if this parameter is left blank, please mark it as "Required". If the parameter is commonly used or recommended, then mark it as "Suggested". The "Remove" button will delete the parameter's entry from TemplateData.

Screenshot of the TemplateData editor, showing a second parameter being added

When you are finished documenting each of the parameters, click "Apply" to insert the pre-formatted TemplateData into the open editing box. You must still save the page, using the normal "Save" button underneath the editing window.

Caution: The TemplateData editor will place TemplateData on either the template page or on a documentation subpage. You determine where the TemplateData will be added by opening (editing) the page that you want the TemplateData to be placed on. However, if multiple TemplateData blocks are placed on the same template, then only one of those TemplateData blocks will be used. If there is already TemplateData on a page, then you need to edit the page where the TemplateData was previously placed to avoid accidentally creating multiple blocks of TemplateData.

Limitations and questions

  • Fonctionnalités manquantes — TemplateData is very much an example of tool that was made available with few features, in hope that users would help to guide development of features that they desired. If you'd like to request new features for TemplateData, please let us know.
  • Delays in showing in templates — After adding TemplateData to a template, the metadata should be visible immediately when the template is opened in VisualEditor. However, it is possible that it takes hours before the metadata show. You can force an update by making a null edit to the template page itself (not the documentation subpage). To perform a null edit, open the template page for editing, and save the page without making any change.
  • Problèmes en cours — A list of current bugs and feature requests is available in the Wikimedia bug tracker.

Structure des TemplateData

TemplateData's structure is based around the JSON standard, and is fairly simple. Note that all descriptions in TemplateData must be in plain text (no wikitext, no links, etc.).

The first thing to do is to type out a pair of <templatedata> tags, anywhere on the template's documentation subpage, like so:

<templatedata>
{
    ...       // Le contenu du TemplateData va ici
}
</templatedata>

This tells the software that everything between the two tags is TemplateData, and should be referenced when the template is used.

Exemple

The descriptions inside TemplateData follow a standard layout; let's say that you have a template called "Commons" for linking to a Commons category about a topic. It takes one mandatory parameter: the name of the category on Commons. The TemplateData would look something like this:

<templatedata>
{
    "description": "A template for linking to a commons category about an article",
    "params": {
        "1": {
            "label": "Commons category",
            "description": "The commons category you want to link to.",
            "default": "Category:CommonsRoot",
            "type": "string",
            "required": true
        }
    }
}
</templatedata>

Ceci apparaîtrait, dans le modèle, ainsi :

A template for linking to a commons category about an article

Template parameters
Parameter Description Type Status
Catégorie de Commons 1

La catégorie de Commons vers laquelle vous voulez créer un lien.

Default
Category:CommonsRoot
Example
empty
Auto value
empty
string required

Description et paramètres

description Le premier drapeau est une "description", qui renseigne sur ce que fait le modèle.
"description": "A template for linking to a commons category",
params Il y a ensuite une étiquette "params", qui indique que les sections qui suivent recouvrent chacun des paramètres du modèle.

Tous les paramètres qui suivent sont inclus dans la section "params"

"params": {
    ...    // les paramètres vont ici
}
  Within each parameter's subsection, the first tag is the name of the template parameter within the template.

If the parameter has a name, like {{{category-link}}}, this tag would be "category-link".

If the parameter is "unnamed", meaning it's just a number like {{{1}}}, this tag would be "1".

All the bits of information about this parameter are included in the section that starts with the parameter's name.

"1": {     // nom du paramètre
    ...    // information about the parameter goes here
}
label Next we have "label", in which you put a human-readable title for the parameter that will be displayed within the template editor.
"label": "Commons category",
description We then have "description": this time, it's a description of the parameter, not of the template as a whole.
"description": "The commons category you want to link to.",
default Next is "default". Some templates have a default value that is used unless you change it. This item tells the user what the default value for this parameter is.

You can ignore this parameter if there's no default.

"default": "Category:CommonsRoot",
type After that we have "type", which controls how the template editor will interpret that parameter. This can be:
  • "string": un ensemble de caractères, comme cette phrase ;
  • "number": a set of digits;
  • "wiki-user-name": a set of characters that represents a user's name;
  • "wiki-page-name": a set of characters that represents a page's title.
  • "wiki-file-name": un nom de fichier.
"type": "string",
required We then have "required", which can be set to either true or false.

This simply controls whether filling out the parameter is mandatory for that template. If you don't specify, it will be assumed to be false.

"required": true
suggested Finally, there is "suggested", which can be set to either true or false.

This is a status for parameters which are not 'required' but are recommended to be high value (but not mandatory) for template users. If you don't specify, it will be assumed to be false.

"suggested": true

Once you're done, hit "save". If you've made errors, it will not let you save (which is disruptive, but means you can't break anything). Should you run into errors, explain on the feedback page what you were trying to do, and we will be happy to help.

Note that each bit of information is enclosed in quotation marks (except for true and false), and separated from the next bit by a comma (unless it's the last one).

Parameter aliases

Some templates allow a same parameter to have different names.

For example, {{Commons|category=Apples}} could also be written as {{Commons|Apples}} or {{Commons|link=Apples}}.

To add this information to TemplateData, you simply need to add the aliases to the parameter's information:

    "params": {
        "catégorie": {
            ...
            "aliases": ["1", "lien"]
        }

Auto value

You can specify an "autovalue" for a parameter. When users add the template to a page, this value will be added automatically. For example, many clean-up templates need to have the date added; if you specify an autovalue for the template's date parameter, then the date will be filled in automatically.

To add this information to TemplateData, simply add the autovalue to the parameter's information. You will probably want to use subst: to make the values stick:

    "params": {
        "date": {
            ...
            "autovalue": "{{subst:CURRENTMONTHNAME}} {{subst:CURRENTYEAR}}"
        }

Multiple parameters

If you have multiple parameters, just repeat each section (starting from the "1" tag) and fill it out as you see fit. Note that if a template has multiple parameters, you need to separate them with a comma in the templatedata, like so:

    "params": {
    "1": {
        ...
    },      // notice the comma here
    "2": {
        ...
    },      // et ici
    "3": {
        ...
    }
    }

Similar parameters

When a template has multiple parameters, sometimes some of them can be of the same kind. In this case, you only need to provide full properties for the first one, and the others can "inherit" their properties from it.

    "params": {
        "sujet1": {
            "label": "Sujet",
            "description": "A topic mentioned on this disambiguation page",
            "type": "string"
        },
        "sujet2": {
            "inherits": "sujet1"
        },
        "sujet3": {
            "inherits": "sujet1"
        },
    }

Blank boilerplate

You can copy the blank boilerplate below to add new TemplateData to a template. Only the most common tags are included.

<templatedata>
{
    "description": "",
    "params": {
        "1": {
            "label": "",
            "description": "",
            "type": ""
        },
        "2": {
            "label": "",
            "description": "",
            "type": ""
        }
    }
}
</templatedata>

Other tools