| title | titleSuffix | description | ms.date | ms.prod | ms.technology | ms.topic | ms.assetid | author | ms.author | manager | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Configuration Manager |
mm/dd/yyyy |
configuration-manager |
configmgr-other |
conceptual |
|
aczechowski |
aaroncz |
dougeby |
Applies to: Configuration Manager (current branch, technical preview branch, long-term servicing branch)
This docs.ms template contains examples of markdown syntax, as well as guidance on setting the metadata. It is available in the root directory of each EM Pilot repository (e.g. ~/Azure-RMSDocs-pr /template.md) and is meant to be read as a markdown file, although you can refer to the published version to see how the markdown examples rendeer.
When creating a markdown file you should copy the template to a new file, fill out the metadata as specified below, set the H1 heading above to the title of the article, and delete the content.
The full metadata block is above, divided into required fields and optional fields; see the OPS metadata cheatsheet for more details. Some key notes:
- You must have a space between the colon (:) and the value for a metadata element.
- If an optional metadata element does not have a value, comment out the element with a # (do not leave it blank or use "na"); if you are adding a value to an element that was commented out, be sure to remove the #.
- Colons in a value (e.g., a title) break the metadata parser. In their place, use the HTML encoding of : (e.g., "title: Azure Rights Management: the basics | Azure RMS").
- title: This title will appear in search engine results. The title should end with a pipe (|) followed by the name of the service (e.g. see above). The title need not (and probably should not) be identical to the title in your H1 heading. It should be roughly 65 characters (including | SERVICE NAME)
- author, manager, reviewer: The author field should contain the Github username of the author, not their alias. The "manager" and "reviewer" fields, on the other hand, should contain aliases. ms.reviewer specifies the name of the PM associated with the article or service.
- ms.assetid: This is the GUID of the article from CAPS. When creating a new markdown file, get a GUID from https://www.guidgenerator.com.
- ms.prod, ms.service, ms.technology, ms.devlang, ms.topic, ms.tgt_pltfrm: Possible values for these elements can be found here.
All basic and Github-flavored markdown is supported. For more information on these, see:
Examples of first- and second-level headings are above.
There must be only one first-level heading in your topic, which will be displayed as the on-page title.
Second-level headings will generate the on-page TOC that appears in the "In this article" section underneath the on-page title.
Italics
Bold
Strikethrough
To link to a markdown file in the same repo, use relative links.
- Example: What is Azure Rights Management
To link to a header in the same markdown file, view the source of the published article, find the id of the head (e.g. id="blockquote", and link using # + id (e.g. #blockquote).
- Example: Blockquotes
To link to a header in a markdown file in the same repo, use relative linking + hashtag linking.
To link to an external file, use the full URL as the link.
- Example: Github
If a URL appears in a markdown file, it will be transformed into a clickable link.
- Example: http://www.github.com
- This
- Is
- An
- Ordered
- List
- Here
- comes
- an
- embedded
- Miss Scarlett
- Professor Plum
- ordered
- list
- This
- is
- a
- bulleted
- list
- This
- bulleted
- list
- Mrs. Peacock
- Mr. Green
- contains
- other
- Colonel Mustard
- Mrs. White
- lists
| Tables | Are | Cool |
|---|---|---|
| col 3 is | right-aligned | $1600 |
| col 2 is | centered | $12 |
| col 1 is default | left-aligned | $1 |
function fancyAlert(arg) {
if(arg) {
$.docs({div:'#foo'})
}
}
This is an example of in-line code.
The drought had lasted now for ten million years, and the reign of the terrible lizards had long since ended. Here on the Equator, in the continent which would one day be known as Africa, the battle for existence had reached a new climax of ferocity, and the victor was not yet in sight. In this barren and desiccated land, only the small or the swift or the fierce could flourish, or even hope to survive.
Note
This is NOTE
Warning
This is WARNING
Tip
This is TIP
Important
This is IMPORTANT
[!div class="button"] button links
[!div class="op_single_selector"]