Wikitravel Shared:Using Mediawiki templates
The software we use, MediaWiki, has a feature to include the contents of one article into another automatically. This is called transclusion or templating. See the template index for a list of available templates.
Templates should be used for editorial markup and metadata. In general a template should be discussed prior to being created or modified. In some cases templates can be confusing for new users, and having large numbers of templates that perform similar functions is counter-productive. Be aware that problems such as difficulty in transferring templates to other formats (such as print or PDF), attribution issues, and maintainability may all be considerations that could make a template a non-ideal solution.
New Mediawiki Template proposals
Before a new Mediawiki Template is put into general use it needs to be discussed and accepted as good or preferably best practice. Mediawiki Templates have both advantages and disadvantages. Some situations lend themselves to Mediawiki Templates, others do not. Each application should discuss the merits and disadvantages of using a Mediawiki Template solution as opposed to other alternatives, if any.
If users wish to experiment with templates then they should explain what they are trying to do on the template talk page. That way we can all learn from the effort.
Each Mediawiki Template that is intended for use by contributors should have its usage documented before it is put into widespread use. This should be done on the template talk page, as well as on a project page or help page that explains how, where and when to use the template. Those templates that are in general use should be listed here too, with links to the documentation.
Changes to any Mediawiki template, especially popular ones, should be discussed and agreed to by users before it is implemented. A substantial change to a template might confuse or distress some users editing a page if the template text also changed at the same time as their edit was made. To safeguard against this, any proposed change to any popular template should have a change control plan that describes how the out of date page/page refresh issue is being addressed.