Global templates/Taxonomy/nl

Dit is een poging om een eenvoudige taxonomie van sjablonen die gebruikt worden op Wikimedia wiki's te schrijven: waar sjablonen voor worden gebruikt en hoe kunnen ze worden gegroepeerd.

Het is moeilijk om een volledige lijst te maken van waarvoor sjablonen worden gebruikt, want er zijn letterlijk honderdduizenden van hen. De lijst in dit document zal slechts enkele veel voorkomende, opmerkelijke families sjablonen tonen, maar vanwege de aard van de technologie kan het niet echt uitgebreid zijn.

Een centrale technische overweging is dat het voorgestelde sjabloon van Globale sjablonen gebruikt kan worden voor "alle" sjablonen, ongeacht welke "familie" ze behoren (op een opt-in basis: geen sjablonen zullen worden geforceerd om in de globale repository te worden opgeslagen). De sjablonen zijn praktisch het enige hulpmiddel dat de wiki-redakteurs hebben om de inhoud efficiënt aan te passen, en "inhoud" betekent hier alles dat op wiki-pagina's wordt geschreven: encyclopedische artikelen, discussies, beleidspagina's, hulppagina' s, essays, geschreven boeken, gebruikerspagina's, vertalingen en al het andere. De voorgestelde repository is voor al deze scenario's.

Een ander relatief klein technisch probleem is dat er naast sjablonen ook modules zijn. Ze zijn vergelijkbaar met sjablonen en vanuit het oogpunt van de gebruiker zijn er slechts twee belangrijke verschillen tussen hen:


 * 1) Sjablonen worden geschreven in wikitext en modules worden geschreven in de programmeertaal Lua.
 * 2) Sjablonen worden geïmplementeerd als onderdeel van het kernplatform van MediaWiki, en modules worden geïmplementeerd in een extensie genaamd Scribunto.

Dit document behandelt zowel modules als sjablonen.

Tenzij anders vermeld, zijn de voorbeelden hier van de Engelse Wikipedia, maar het is cruciaal om op te merken dat dit niet betekent dat de Engelse Wikipedie de "bron" is, of zou moeten zijn, voor alle sjablonen of inhoud. Dit wordt simpelweg gedaan om de oorspronkelijke taal te zien waarin deze pagina is geschreven. In feite is er veel technische innovatie in de ontwikkeling van sjablonen in andere wiki's (Wiktionary, Commons, Wikidata, Wikinews, enz.), en in veel talen, met name Frans, Duits, Russisch, Spaans, Catalaans, Pools, Hebreeuws, Perzisch, Arabisch, Chinees, evenals in vele anderen. Sommige daarvan worden in dit document specifiek genoemd. 

Wat zijn sjablonen niet
Hoewel het technisch mogelijk is, worden sjablonen meestal niet gebruikt voor de proza van wiki-pagina's. Het beleid van de Engelse Wikipedia over sjablonen staat zelfs aan de bovenkant: ''Sjablonen mogen normaal niet worden gebruikt om artikeltekst te bewaren. ''

Sjablonen worden vaak ingebed in alinea's van wikipagina's, maar het wordt meestal alleen voor speciale opmaak en niet voor gewone tekst. 

Overzichtstabel
Elke rij van de tabel wordt in de volgende alinea's nader beschreven.

Citaten


Algemene citaten
"Basis" voetnoten worden ingevoegd met behulp van een uitbreiding die Cite wordt genoemd, en dit werkt op dezelfde manier in alle talen met behulp de tag  in wikitext. (Hoewel deze gelijkheid voor het grootste deel goed is, is het ook op sommige manieren problematisch. Bijvoorbeeld, het gebruik van dezelfde  tag in rechts-tot-links wiki's veroorzaakt enkele problemen; zie .)

De inhoud van de meeste citaties is echter geformatteerd met behulp van sjablonen. Citatiestijl vereist een uniforme opmaak. De meest opmerkelijke Engelse Wikipedia-sjablonen van dit soort zijn Cite web, Cite book en $Cite̠journal. Er zijn tientallen andere en ze worden in bijna alle artikelen gebruikt.

Sommige van deze zijn geïmporteerd naar veel andere talen, maar hun titels en parameters zijn niet noodzakelijkerwijs hetzelfde, zodat ze niet betrouwbaar en efficiënt kunnen worden hergebruikt over wiki's, waardoor vertaling moeilijker wordt. Veel bug-rapporten over Content Translation, bijvoorbeeld, hebben relaties met citaat sjablonen.

Ze zijn ook niet machineleesbaar, tenminste niet in een draagbaar formaat: men kan software ontwikkelen om citatiemetadata uit de Engelse Wikipedia te lezen, maar het zal bijna van het begin af moeten worden geschreven om citatietadata uit het Franse Wikipedia, de Duitse Wikipedia, enz. te lezen.



Bijzondere broncitaten
Deze sjablonen zijn vergelijkbaar met algemene citaat sjablonen, maar ze zijn gemaakt voor specifieke bronnen die op veel pagina's nodig zijn. Voorbeelden in het Engels: Cite Catholic Encyclopedia, Britannica (voor het citeren uit Encyclopædia Britannica).



Gestructureerd citeren: Cite Q
Een bijzonder opmerkelijk voorbeeld van een sjabloon dat citaties toont is Cite Q. Het probeert de kracht van gestructureerde data in Wikidata te combineren met de citatiebehoeften van Wikipedia (in verschillende talen!), en haalt de citatieinformatie uit Wikidata. Het is specifiek ontwikkeld voor eenvoudig hergebruik in verschillende talen, met een mogelijke toekomstige migratie naar een globale sjabloonrepository in gedachten.



Citatie-infrastructuur
Dit zijn sjablonen en modules die niet direct worden gebruikt door artikelredakteurs, maar intern worden gebruikt door andere citaat sjablonen om een gestandaardiseerde uitstraling te creëren. Opmerkelijke voorbeelden zijn Module:Citation/CS1 en Module:Citation/CS1/COinS. Deze modules worden vaak besproken als stukken infrastructuur die door alle wiki's moeten worden gedeeld.



Pagina metadata
Veel sjablonen implementeren artikel-metadata. Sommige van deze gegevens verschijnen in de naamruimte van het artikel en andere in de ruimte Overleg. Sommige van deze artikelen zijn in het artikel opgenomen, maar worden niet daadwerkelijk aan de lezers getoond.



Artikelstatus badges
Deze zijn meestal badges zoals Featured article, Good article, enz. Ze worden ingevoegd in de artikel wikitext bron, maar worden getoond in de balk bovenaan de pagina. Hoewel de functionaliteit vergelijkbaar is, kunnen de specifieke ontwerpen en interne implementaties van dit sjabloon in elke wiki verschillen. Het "featured article" proces is een teken van een actieve en zorgzame bewerkingsgemeenschap; het gebrek aan een dergelijke sjabloon is meerdere malen door redacteuren opgebracht in kleinere, maar zich ontwikkelende wiki's als een blokkade voor het versterken van de lokale bewerkingscommunity.



Interne informatie voor redacteuren
Dit zijn sjablonen die niet aan de lezers worden getoond, maar die informatie moeten geven die nuttig is voor de redacteurs. In de Engelse Wikipedia zijn er bijvoorbeeld sjablonen die de redacteuren informeren over het dialect van het Engels dat op die pagina moet worden gebruikt (Use American English, Use British English, $Use _Indian_English), of over het gebruik van een bepaald datumformaat (bijvoorbeeld Use dmy dates).



Metadata op overlegpagina's
De namespace Talk is oorspronkelijk gemaakt voor discussies/overleg over het artikel. Al in het midden van de jaren 2000 begonnen redacteurs het echter ook te gebruiken voor het opslaan van metadata en onderhoudssjablonen voor de activiteiten van de bewerkingsgemeenschap. Een opmerkelijk voorbeeld is de WikiProject-sjablonen op de Engelse Wikipedia, die artikelen sorteert volgens onderwerpen die nuttig zijn voor experts in de bewerkingsgemeenschap. Bijvoorbeeld, de discussiepagina van het artikel Shanghai toont verschillende dergelijke sjablonen: WikiProject China, WikiProject Cities, WikiProjekt Oost-Azië, WikiProjet Politiek, WikiPro project Geografie en Wikipedia Version 1.0 Editorial Team.

Deze sortering werd gemaakt door de Engelse Wikipedia gemeenschap om te worden gebruikt voor haar interne doeleinden. Het wordt echter zo vaak gebruikt dat het werd gebruikt door het WMF Research team om artikelen in onderwerpen te sorteren, en het werd vervolgens toepasbaar op andere talen en gebruikt om suggesties te tonen in de Growth extensies. Hoewel het een nuttig resultaat heeft, is dit ook vrij problematisch omdat de Engelse Wikipedia-gemeenschap taxonomie op alle talen afdwingt, zonder andere gemeenschappen de kans te geven om het rechtstreeks te beïnvloeden.

Vergelijkbare WikiProject-templates bestaan in het Pools, het Russisch, het Turks en enkele andere talen. Mensen die wiki's in meerdere talen bewerken, hebben interesse uitgesproken in het hergebruiken van dit systeem, maar het importeren was voor hen te ingewikkeld.

Een ander opmerkelijk voorbeeld is het informeren van redacteurs over belangrijke gemeenschapsbeslissingen over controversiële onderwerpen. Bijvoorbeeld, de kennisgevingen over de Engelse Wikipedia Arbitration Committee sancties op de overlegpagina van Kosovo worden ingevoegd met behulp van het generische sjabloon Mbox.

Media metadata and licensing
Commons and all other Wikimedia wikis are strict about using correct copyright licenses, checking the sources of media files, and describing the files usefully. This has always been done by adding templates such as Information, cc-by-sa-3.0, artwork, and many others to the file information page. Some of this information is gradually being transitioned to the Structured Data on Commons infrastructure, but the process is far from completion.

Infoboxes
This is one of the most notable examples of features implemented using templates.

There are hundreds of infobox templates in various wikis. Roughly, there are two types of those:


 * 1) Manual infoboxes, which require the adding of each parameter in the wikitext of the article itself.
 * 2) Automated infoboxes, which provide the formatting, but pull the actual information from Wikidata.

There’s also a wide spectrum of templates in between the two extremes: they can pull information by default, or under certain circumstances (for example, only if the Wikidata statement has a reliable source), but also allow adding of information locally using parameters.

The manual templates are more common in the English Wikipedia, although the usage of Wikidata-based ones is gradually increasing. The automated ones are common in Russian, Spanish, French, Hebrew, and many other languages.

There is huge demand for both types of infoboxes in smaller languages. In particular, this was brought by many editors in languages of Africa and the Philippines, but really from the whole world.

Article maintenance
Many templates are used to draw the readers’ and editors’ attention to issues of article tone, neutrality, reliability, completeness, and so on. They may apply to the whole page or to its part. In the English Wikipedia, they are sometimes known as “tags” or “hatnotes”.

Such templates often add the article to a category, for example, Articles needing additional references. Such categories are known as Backlogs: editors can go through them and continuously improve the wiki. In the larger Wikipedias, there may be dozens or even hundreds of such categories.

The impact of such templates has been the subject of research. For one example, see Templates and Trust-o-meters: Towards a widely deployable indicator of trust in Wikipedia by Andrew Kuznetsov, Margeigh Novotny, Jessica Klein, Diego Saez-Trumper, and Aniket Kittur.

Whole article
Examples of maintenance templates that apply to the whole article:


 * Unreferenced: “This article does not cite any sources.”
 * Current: “This article documents a current event. Information may change rapidly as the event progresses, and initial news reports may be unreliable.”
 * Underlinked: “This article needs more links to other articles to help integrate it into the encyclopedia.”
 * Disputed: “This article's factual accuracy is disputed. Relevant discussion may be found on the talk page.”

Some of these are now used in the Growth extensions, for example Underlinked. This is a nice integration with community workflows, but it also means that if a wiki wants to use the corresponding Growth feature, the template must exist and work in a way that is compatible with the extension, and this must be done in every wiki manually. If the template was global, this could be done effortlessly in all wikis.

Parts of an article
Perhaps the best known, iconic Wikipedia template is citation needed (for example, it is featured in the web comic XKCD: https://xkcd.com/285/). It’s used when some words in the article may be true, but there may be doubt about them and a reference should be added. It’s very common in the English Wikipedia, and in many other languages. In some languages, it’s also common to mark to which words exactly this template applies; it is possible in English, too, but it’s less common.

Visual Editor has some special support for this template: It can show an extra panel that shows the reason for the doubt, and a button for quick adding of a reference. This support is not universal, however: even if the template exists, this window must be configured manually on every wiki by writing a JSON file. A wiki that wants to use it must therefore create the template and the JSON file. This is a demonstration of how the lack of a global templates repository makes the development of WMF products inefficient.

This template is not just a signifier of doubt—it is a part of an editing workflow. Like some other maintenance templates, it adds the article to a backlog category categorized by date. Many editors go through these categories and improve these articles.

In addition to “citation needed”, there are other templates of this kind, such as clarify and who. For example, the English Wikipedia article Park Güell says (as of January 2023):

"On the other hand, many experts have tried to link the park to various symbols because of the complex iconography that Gaudí applied to the urban project."

The “ [who?] ” badge alerts the readers that this may be a “weasel word” and invites editors to add a specific citation.

Navigation boxes
Navigation templates, also known in English as “navboxes”, appear in millions of Wikipedia articles. They usually include links to articles on a related topic, and are manually curated by editors. Because an encyclopedia covers thousands of topics and every navigation box has up to several dozens of links, there are thousands of navigation templates.

Navigation boxes are used for various topics. For example, a navigation template about a musician, such as Neil Young, may show a list of their albums, collaborators, side projects, and other related subjects.

Multiple navigation templates may appear in the same article. For example, the article Nancy Pelosi has Nancy Pelosi, a navigation box for topics directly related to Pelosi herself, as well as some others, grouped under “Links to related articles”: Democratic Party, US House Speakers, US House Leaders, US Order of Precedence, and more.

Navigation templates can appear in different locations in the article, but typically, they are used on one of these three locations:


 * 1) At the bottom of the article: common with articles about people or groups.
 * 2) In the beginning: common in more abstract topics, such as Psychology sidebar (for example, in Cognitive bias) or Islam (for example, in Hajj).
 * 3) In the middle: when a section in an article is related to another topic.

That said, practices may fluctuate in different topics and languages.

Such templates may include red links, which signify that the target of the red link is related to the theme and an article about the topic should exist, but was not written yet.

They appear not just in the English Wikipedia, but in many other languages. The aforementioned Neil Young navbox appears in nine other languages with similar content.

Navigation boxes are useful for both editors and readers, for topic organization and for getting information about related subjects. As of January 2023, however, they are completely hidden from mobile users because of the difficulty to adapt their styling to small screens. With the current technology, this adaptation is possible, but it would have to be made for each wiki separately. If, at least, there was the same basic implementation shared across wikis, this would only have to be done once. Many users have asked to show them on mobile devices, but this wasn’t done yet.

Article navigation
These are templates that help people find information. Some examples:


 * Main: Used immediately after a section heading and shows a formatted link to another article that has expanded information about the subject of that section.
 * About and For: Show a note at the top of the page and helps people find articles with similar names. For an example, see the article Georgia (country): at the top, it shows the text This article is about the Country of Georgia. For the US State, see Georgia (U.S. state). For other uses, see Georgia (disambiguation).
 * Sister project links: Usually appears towards the end of the article and shows links to pages related to the same topic in Commons, Wikibooks, Wikivoyage, etc.
 * Page navigation templates in Wikisource. For an example, see Chapter 6 of Alice’s Adventures in Wonderland: The light-green bar at the top shows links to the previous and next chapters, the table of contents, and the author.

As with other sections, there are hundreds of templates that have similar functionality. These are essentially navigation and search functions that would be useful in all languages because all languages have articles with homographic titles and links to related and enhanced articles, but with the current technology, they have to be created in every wiki separately.

General formatting
Templates are used for various text and image formatting purposes, for example:


 * Blockquote: Shows quotations from books, poems, etc.
 * ISBN: Shows a formatted ISBN with a link to information about a book.
 * Center: Shows centered text.
 * Flex columns: Shows text formatted as columns.
 * Image array: Shows a gallery of images. Similar to the  tag, which is built into the core MediaWiki platform, but with more features.

There are hundreds of other templates of this kind.

Important comments that apply to all of them:


 * Many of them are available in other wikis and not only in English, but there are some differences in implementation.
 * Unlike it is with built-in formatting tools such as bold font ( ''' ) or section heading ( == ), it’s impossible to select some text and mark it as centered or as a book quote. The user has to cut the text, insert the template, and then paste the text as a parameter.
 * They are comparable to styles that are available in common word processors such as Microsoft Word and Google Docs, but none of them can be inserted using dedicated buttons in the Visual Editor toolbar. The user always has to know how the template name is written and then use the   button and type the template manually. In theory, it would be possible to add some of them to the toolbar, but it would have to be done for each wiki separately.

Advanced formatting and special data presentation
These templates are similar to text formatting, but usually show something more advanced.

Some examples:


 * Geographical maps: There are lots of different maps templates in different languages, some of which use OpenStreetMap, and some of which use templates that are custom-made by Wikipedians.
 * Railway maps: The Routemap template offers a special, complex, custom language for designing rail maps. They are used in thousands of articles about railways in multiple languages.
 * Coordinates: These are used in many languages to show the coordinates of places described in the articles. They are used not only for displaying the numbers, but also for showing “Nearby” articles in Wikipedia mobile apps, but this can only work in the wikis in which these templates work in a manner that the apps recognize, so someone has to manually maintain compatibility in each wiki.
 * IPA, Respell, and Lang: these are templates that show spelling and pronunciation of names, especially foreign ones, most often in parentheses in the first sentence.
 * Chess: Chess games are described using a precise language called Portable Game Notation (PGN). In some Wikipedias, there are templates that can get notation in this language and display a game. Interestingly, this is not available in the English Wikipedia, but can be found, for example, in the Hebrew Wikipedia article about Alexander Alekhine. Since late 2019, there has been an effort by several volunteers to rewrite this template as an extension so that it will be usable everywhere, but it’s unclear whether it will be deployed.
 * Unit conversion, such as Convert: Templates that help easily show values of distance, mass, temperature, etc., in miles/km, kg/lb, F°/C°, and so on. Even though it may seem as if it’s useful mostly for Americans, they are used in many wikis.

Some advanced formatting and content types are implemented as MediaWiki extensions, for instance math and chemistry formulas, musical notation, Egyptian hieroglyphics, and timelines. This makes it possible to reuse them equally across all wikis and languages, and to insert and edit them using the Visual editor toolbar. There is nothing inherently different between Egyptian hieroglyphics and IPA, for example—both content types could be implemented as templates or as extensions, and they were implemented as they were for arbitrary historical reasons: The person who wanted to add Egyptian hieroglyphics support knew PHP and decided to do it that way, and the first person who wanted to add IPA did it using a template because it seemed simple.

Wikidata
Templates and modules wrapped in templates are essentially the only way to embed structured data from Wikidata into Wikipedia articles. The basic technology for inserting such data into wikis is the same everywhere, but the “out-of-the-box” data embedding capabilities are so rudimentary that all the wikis that actually do it developed their own ways.

In addition to the aforementioned Infoboxes and Cite Q, Wikidata is also used for many other things, such as showing semantic maps, Authority control for partners and linked data, etc.

Another example is showing data about sports competitions. In the articles about Tour de France 2018 in French, Latvian, and Japanese, the tables were inserted using the same short code, for example,. This was possible thanks to the efforts of volunteers in these languages to manually synchronize the code of the templates in each wiki. If there was a global templates repository, no manual coordination would be needed, and it would have to be done just once and usable in all languages.

User page
Various templates are often used on user pages. The small userboxes, of which there are thousands, are the most obvious example, and there are also notifications of activity (active, retired, taking a break, etc.), fancy personal formatting, etc.

One of the most commonly used templates across all Wikimedia projects is a template that indicates that a certain user page belongs to a bot account. Example: User:DatBot.

User talk page
Templates are frequently used on user talk pages. Some examples:
 * Archive boxes, pointing to old discussions.
 * Warnings, posted by administrators and other users, when a user makes an unconstructive edit (vandalism, unreferenced information, copyright violation, etc.)
 * Notifications about blocks.
 * Notifications about events, such as editathons, competitions, meetups, etc.

Community discussion
Some community discussions use structures. Most notably:


 * Discussions about page deletion have special formatting achieved using templates.
 * Discussions about appointing users as administrators or receiving other permissions, have templates that help other users examine their contributions, deletions, blocks, etc.
 * In large wikis, arbitration committee discussions have a strict structure, some of which is enforced using templates. For an example, see Wikipedia:Arbitration/Requests/Case/Iranian politics.

Wiktionary
Wiktionaries heavily rely on templates to show grammatical information, conjugation tables, citations, gender and case declination, and so on. This creates a fairly nice presentation for readers, and indeed Wiktionary is Wikimedia’s most read project after Wikipedia. However, it makes Wiktionary quite difficult for editors to engage in because to make any contribution, one must learn how to use at least some templates, which tend to have cryptic names such as t+ (translation with superscript link), lb (sense for label), ux (usage examples), der (derived etymology), etc.

And this is just in the English Wiktionary; other editions, such as French, Dutch, Russian, etc., all of which are quite successful with readers, have templates of their own, even though their functionality is mostly the same.

In addition to making Wiktionary hard to edit for novice editors, it also makes it very difficult to write software that processes it. Even if someone writes software that makes the English Wiktionary data machine-readable, it will have to be completely rewritten for the French Wiktionary, the Russian Wiktionary, etc.

Internal infrastructure
Many templates and modules are usually not used directly in articles or discussion pages, but only in other templates and modules. They provide internal infrastructure functions for formatting, logic, data retrieval, etc. They are also sometimes known as “metatemplates”. Some of these are among the most frequently used templates in many wikis.

Because of their importance for using other templates, many of them are copied to hundreds of wikis with very little or no change, and they are frequently proposed for globalization of some sort.

Some examples:


 * Icon: provides uniform design of icons in various other templates.
 * Ambox: provides uniform design of hatnotes (see the “Article maintenance templates” above).
 * Module:Arguments: the most transcluded module in the English Wikipedia. Provides easy processing of arguments in Lua code.

Conclusion
This page only scratches the surface of demonstrating how templates are used. The world of templates on Wikimedia is enormous, and only the most notable examples are given here.

The ultimate goal of the Global templates proposal is to make every template that is useful to multiple wikis conveniently accessible. This will provide feature equity, and, thus, knowledge equity, to speakers of all languages and participants of all Wikimedia projects.