This is a work in progress. The User Experience Guidelines exist as an effort to establish basic consistencies across TechNet Wiki. The guidelines are manual (you have to make the changes yourself), and a goal of creating manual guidelines is to eventually turn some of them into automatic guidelines (that occur automatically through tools) in order to reduce editing and communication around following the guidelines. In this article:
The title of the article determines the URL of the article. For example, an article is titled "Wiki: Style Guide", which results in a URL of http://social.technet.microsoft.com/wiki/contents/articles/wiki-style-guide.aspx. Note that spaces become '-' and characters such as ':' are ignored when creating the URL for an article. For more details, see the Wiki Title Guidelines.
↑ Return to Top
EXAMPLE:
This article is based on information from <article reference> written by <orginal author>.
As Ana mentioned in this blog post, Wikipedia has this to say about signatures: "When editing a page, main namespace articles should not be signed, because the article is a shared work, based on the contributions of many people, and one editor should not be singled out above others." - Wikipedia: Signatures The exception we make, is that we allow the Credits section (see "Credits Section" in "Layouts" above).
However, we want to give you credit for your work... We provide five ways for you to receive credit for your contributions in TechNet Wiki:
Follow these guidelines in order to provide a complete story of Wiki navigation and accessibility. We might try to automate more of these features in the future in order to require less manual work and maintenance. The related topic of Cross-Linking is discussed in Wiki: Cross-Linking NOTE: This section includes only brief explanations. For full guidelines and details, see the appropriate bullets in the Page Layout section above.
To make an article easier to discover using the wiki search, include tags that are relevant to the topic discussed in your article. For example, an article that discusses using SQL Server Express with PHP should be tagged with the 'SQL', 'SQL Express', and 'PHP' tags.
Commas
This section requires more information.
Ed Price - MSFT edited Revision 137. Comment: Added See Also
TEST
adsfasdf
Richard Mueller edited Revision 136. Comment: Added link to Wiki article on "Cross-Linking"
Ed Price - MSFT edited Revision 134. Comment: We're going with "Additional Resources" instead of "Community Resources". For example, if it's a link to an MSDN article, it goes here. That doesn't feel like a link to a "Community" resource. So "Additional" works better.
Peter Geelen - MSFT edited Revision 130. Comment: cleaned HMTL
Richard Mueller edited Revision 128. Comment: Clarified title and tag guidelines for non-English articles
Carsten Siemens edited Revision 127. Comment: Fixed misspelling
Richard Mueller edited Revision 122. Comment: Minor typo
Richard Mueller edited Revision 121. Comment: Remove blank heading from HTML
Ed Price - MSFT edited Revision 108. Comment: Added info and links about non-English language codes.
pkn2011 edited Revision 106. Comment: Just fixed a couple of typos.. pkn
Hacked By Mehedi
follow this Url to Earn a 500000$ prize
https://attacker.com
Perhaps change the "In this article" section to use the new [toc] tag?
Kevin, you can if you'd like. I haven't been doing that for articles that opted to do the manual TOCs.
Ed Price - MSFT edited Revision 97. Comment: Added bullet about code font in the "Font and Design" section
Excellent Article Ed! Just what I'm looking for. :) pkn
Peter Geelen edited Revision 100. Comment: Added TOC tag + updated procedure for TOC
Ed Price - MSFT edited Revision 101. Comment: Updated the TOC and Stub sections.
Ed Price - MSFT edited Revision 102. Comment: Updated the External Links section.
Peter and I updated the TOC section and info. Thanks Peter!