Skip to content

Commit 9e1211a

Browse files
authored
Create concept article template with guidelines
Added a template for concept articles with SEO guidance.
1 parent 88ef8e3 commit 9e1211a

File tree

1 file changed

+102
-0
lines changed

1 file changed

+102
-0
lines changed
Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
---
2+
title: [Follow SEO guidance at
3+
https://review.learn.microsoft.com/en-us/help/platform/seo-meta-title]
4+
description: "[Article description]."
5+
author: [your GitHub alias]
6+
ms.author: [your Microsoft alias or a team alias]
7+
ms.service: [the approved service name]
8+
ms.topic: concept-article #Don't change.
9+
ms.date: [mm/dd/yyyy]
10+
11+
#customer intent: As a <role>, I want <what> so that <why>.
12+
13+
---
14+
15+
<!-- --------------------------------------
16+
17+
- Use this template with pattern instructions for:
18+
19+
Concept
20+
21+
- Before you sign off or merge:
22+
23+
Remove all comments except the customer intent.
24+
25+
- Feedback:
26+
27+
https://aka.ms/patterns-feedback
28+
29+
-->
30+
31+
# [noun phrase] concept(s)
32+
33+
or
34+
35+
# [noun] overview
36+
37+
<!-- Required: Article headline - H1
38+
39+
Identify the product, service, or feature the
40+
article covers.
41+
42+
-->
43+
44+
[Introduce and explain the purpose of the article.]
45+
46+
<!-- Required: Introductory paragraphs (no heading)
47+
48+
Write a brief introduction that can help the user
49+
determine whether the article is relevant for them
50+
and to describe the concept the article covers.
51+
52+
For definitive concepts, it's better to lead with a
53+
sentence in the form, "X is a (type of) Y that does Z."
54+
55+
-->
56+
57+
## Prerequisites
58+
59+
<!--Optional: Prerequisites - H2
60+
61+
If this section is needed, make "Prerequisites" your
62+
first H2 in the article.
63+
64+
Use clear and unambiguous language and use
65+
an unordered list format.
66+
67+
-->
68+
69+
## [Main idea]
70+
71+
[Describe a main idea.]
72+
73+
<!-- Required: Main ideas - H2
74+
75+
Use one or more H2 sections to describe the main ideas
76+
of the concept.
77+
78+
Follow each H2 heading with a sentence about how
79+
the section contributes to the whole. Then, describe
80+
the concept's critical features as you define what it is.
81+
82+
-->
83+
84+
## Related content
85+
86+
- [Related article title](link.md)
87+
- [Related article title](link.md)
88+
- [Related article title](link.md)
89+
90+
<!-- Optional: Related content - H2
91+
92+
Consider including a "Related content" H2 section that
93+
lists links to 1 to 3 articles the user might find helpful.
94+
95+
-->
96+
97+
<!--
98+
99+
Remove all comments except the customer intent
100+
before you sign off or merge to the main branch.
101+
102+
-->

0 commit comments

Comments
 (0)