This topic is inspired by Wikipedia:Template messages. Message Template (or simply a “template” for short) is a standardized block of text that points to a specific characteristic of an article. You can put a template to any article if you want to draw reader's attention to some specific feature of the topic. Feel free to add and remove templates from your articles but please do not change template wording unless specifically directed to do so by template usage guidance.
NOTE: For examples of each sign, click the tag related to the template. It is located after the code of each template (see below). ISSUE: One issue is that by putting these at the top of your article, that's the intro text grabbed for scenarios like search results (Google, Bing, TechNet Wiki search), RSS feed summaries, and when an article is featured. So you might want to start with an intro paragraph or sentence first.
To put a template to an article page please do the following.
Every template also has a “Short form” version. It does not show the template message until you hover your mouse over its picture or title. It may be useful to save space when there are a lot of templates (3+) placed on one page and you prefer to place tham one-by-one instead of stacked. This type of template is a bit harder to use because you would need basic HTML skills in order to place each template as a separate cell in one table (that unites all the templates).
Here is one very important thing about templates: every template is meant to have a related tag. The template does not replace the tag! It just adds a visualization and clarity. When placing a template in an article—please, please, please don't forget to add the template tag to the list of other tags (it is located below the WYSIWYG editor box). When removing the template—please remove the tag as well.
If you wish to change something in existing templates, please avoid editing this page (either code or samples), if you are not completely, absolutely sure what are you doing. (Hint: you will need significant HTML editing skills for it!). If in doubt whether you could edit a template correctly please leave a comment to this page or participate in the templates discussion at TechNet Wiki Forums. Thanks in advance!
↑ Back to top
Template code
<table align="center"
style="background-color: #eee; width: 80%; border: #aaa 1px solid;">
<tbody>
<tr>
<td>
<img src="/wiki/resized-image.ashx/__size/550x0/__key/CommunityServer.Wikis.Components.Files/articles/4760.discussion04.png" />
</td>
<strong>This topic is a <em>discussion.</em></strong><br />
There's no best practice that suits all environments. This article
presents different options and points of view. If you disagree with some
point — <strong>do not delete</strong>. Add your own thoughts and
considerations instead. If they conflict with what was already written by
others — mark yours as an “Alternate opinion”.
</tr>
</tbody>
</table>
Short form (one message view example)
<table align="center" style="width: 90%;">
<td style="width: 30%;">
<acronym style="cursor: help;"
title="There's no best practice that suits all environments. This article presents different options and points of view. If you disagree with some point — do not delete. Add your own thoughts and considerations instead. If they conflict with what was already written by others — mark yours as an “Alternate opinion”.">
<table align="center" style="background-color: #eee;
border: #aaa 1px solid; width: 100%;">
<td style="text-align: center;">
<strong>Discussion</strong>
</acronym>
The tag related to this template is Discussion.
NOTE: Click the tag to see examples of this template.
<img src="/wiki/resized-image.ashx/__size/550x0/__key/CommunityServer.Wikis.Components.Files/articles/1220.highlevel03.png" />
<strong>This topic is a <em>high-level overview.</em></strong><br />
Here we discuss theory and general concepts. Do not be too specific.
Avoid referencing specific product names or procedures (except as required
for examples).
Short form (two messages view example)
title="Here we discuss theory and general concepts. Do not be too specific. Avoid referencing specific product names or procedures (except as required for examples).">
<strong>High-Level Overview</strong>
The tag related to this template is High Level.
<img src="/wiki/resized-image.ashx/__size/550x0/__key/CommunityServer.Wikis.Components.Files/articles/0474.howto03.png" />
<strong>This topic is a <em>how to.</em><br />
</strong>Please keep it as clear and simple as possible. Avoid
speculative discussions as well as a deep dive into underlying mechanisms
or related technologies.
Short form (three messages view example)
title="Please keep it as clear and simple as possible. Avoid speculative discussions as well as deep dive into underlying mechanisms or related technologies.">
<strong>How to</strong>
The tag related to this template is How To.
(please add your suggestions here or post in forum)
<img src="/wiki/resized-image.ashx/__size/550x0/__key/communityserver-wikis-components-files/00-00-00-00-05/6165.RR.png" style="width: 60px; height: 60px;" />
<strong>This topic is a <em>recommended reading.</em></strong><br />
This article indicates a suggested or recommended reading that will provide you with accurate and importante informations for a better understanding of the covered topic.
title="This article indicates a suggested or recommended reading that will provide you with accurate and important informations for a better understanding of the covered topic.">
<img src="/wiki/resized-image.ashx/__size/550x0/__key/communityserver-wikis-components-files/00-00-00-00-05/6165.RR.png" style="width: 50px; height: 50px;" />
<strong>Recommended reading</strong>
The tag related to this template is Recommended reading.
<img src="/wiki/resized-image.ashx/__size/550x0/__key/CommunityServer.Wikis.Components.Files/articles/3286.vendoragnostic07.png" />
<strong>This topic is <em>vendor-agnostic.</em></strong><br />
Here we talk about theory that applies to any hypervisor. For specific
implementation and technical details please refer to other topics, for
example those tagged “<a
href="/wiki/contents/articles/tags/Hyper-V/default.aspx">Hyper-V</a>”
and “<a href="/wiki/contents/articles/tags/How+To/default.aspx">How
To</a>”.
title="Here we talk about theory that applies to any hypervisor. For specific implementation and technical details please refer to other topics, for example those tagged “Hyper-V” and “How To”.">
<strong>Vendor-agnostic</strong>
The tag related to this template is Vendor-agnostic.
Usage guidance
Please replace “hypervisor” with the name of actual discussion topic. Also edit the list of tags to make it more relevant to discussion topic.
<img src="/wiki/resized-image.ashx/__size/550x0/__key/CommunityServer.Wikis.Components.Files/articles/8623.workinprogress.png" />
<strong>This topic is <em>work in progress.</em></strong><br />
Please abstain from editing it right now. You're welcome to contribute
here in a couple of hours or days, though!<br />
<em><span style="font-size: xx-small;">Please remove this sign if there
are no changes made in last 48 hours.</span></em>
title="Please abstain from editing it right now. You're welcome to contribute here in a couple of hours or days, though! (Please remove this sign if there are no changes made in last 48 hours).">
<strong>Work in progress</strong>
The tag related to this template is In progress.
As the template says, place the template when you want to “check out” the article and politely ask the others to not edit it in order to avoid conflicts. Please remove the template as quickly as you finish your work. If you don't introduce any changes for a long time, be ready for someone to remove the template and edit the article him- or herself. Don't use this template if you just want to edit the article someday. Use it only when you are actually working on content or just took a little break.
Other Languages
yottun8 edited Revision 39. Comment: Updated a link.
Richard Mueller edited Revision 37. Comment: Fixed typo
yottun8 edited Revision 35. Comment: Added the ja-JP link.
Luigi Bruno edited Revision 34. Comment: Edited the "Recommended reading" template.
Ed Price - MSFT edited Revision 33. Comment: Updating headers for formatting
Ana Paula de Almeida edited Revision 32. Comment: Fixing the code of message template 'Recommended reading': Picture size and title (Discussion for Recommended reading)
Luigi Bruno edited Revision 31. Comment: Edited the "Recommended reading" message template. Added a link in the "In this article" section.
Luigi Bruno edited Revision 30. Comment: Edited the "Recommended reading" message template.
Luigi Bruno edited Revision 29. Comment: Added the "Recommended reading" message template.
Luigi Bruno edited Revision 28. Comment: Added "en-US" to the article's title and tags list. Added a link in the "Other Languages" section.
Tony Soper_MSFT edited Revision 9. Comment: added example
Pronichkin edited Revision 10. Comment: Added notes on how to see usage examples in Wiki by clicking the tag.
Ed Price MSFT edited Revision 11. Comment: Made minor grammar edits, Note style edits (for wiki-wide consistency, and added See Also link).
Ed Price MSFT edited Revision 12. Comment: Updated title.
I'm voting on a good template to do next... Link Collection. I started a tag for "Link Collection" to get us closer.
Ed Price MSFT edited Revision 13. Comment: Fixed a link and added the "More to do" item of a "Troubleshooting" template.
Ed Price MSFT edited Revision 14. Comment: Minor edit.
Ed Price MSFT edited Revision 15. Comment: Added the templates to this article.
Ed Price MSFT edited Revision 16. Comment: Minor edit.
Great Idea! Any suggestions on what exactly the message should say? I.e. what do we want folks do with this type of articles? My suggestion:
This title is a Link Collection
Please add more relevant links if they are not similar to those already in the list. We'd appreciate it if you not just type the link title but also provide the name of the website or specific publication and it author(s). E.g.: “TechNet Wiki – Contribute Boldly! (Craig Landis, “Ask the Directory Services Team” blog)”. So one could have more information to decide whether he's really interested in that particular link.
KimDitto_MSFT edited Revision 18. Comment: Paste did not work.
Ed Price MSFT edited Revision 19. Comment: Testing link change.
Ed Price MSFT edited Revision 20. Comment: Updated first forums link.
Ed Price MSFT edited Revision 21. Comment: Updated two "post in forum" links.
How about a template for "Content Requested" or something similar for topics that people would like to get information about, but they don't know enough about to write an article. Then people with knowledge about the area requested could go ahead and add information.