Integrating EDI guidance into the conceptual type (#60443)

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Thom Wong <101249231+supergranular@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: 4 people

…content-model/conceptual-content-type.md …d-content-model/concepts-content-type.mdcontent/contributing/style-guide-and-content-model/conceptual-content-type.md renamed to content/contributing/style-guide-and-content-model/concepts-content-type.md content/contributing/style-guide-and-content-model/conceptual-content-type.md renamed to content/contributing/style-guide-and-content-model/concepts-content-type.md

@@ -1,32 +1,39 @@
 ---
-title: Conceptual content type
+title: Concepts content type
 intro: People most often use conceptual content when they are learning about something new to them.
+category:
+  - Follow the style guide and content model
 versions:
   fpt: '*'
   ghec: '*'
   ghes: '*'
-category:
-  - Follow the style guide and content model
+redirect_from:
+  - /contributing/style-guide-and-content-model/conceptual-content-type
 ---
 
 Conceptual content helps people understand a feature or topic by providing a clear, high-level overview, explanation of how the feature or topic can help them on their journey, and context like use cases or examples.
 
-We create conceptual articles and conceptual sections within other articles. Most major products, features, or subjects have their own conceptual article.
+We create concepts articles and conceptual sections within other articles. Most major products, features, or subjects have their own concepts article.
+
+## Deciding between an article or a section
+
+How-tos or tutorials can have 1-2 brief introductory sentences before the steps. If more explanation beyond a couple of sentences is needed, that’s when we should consider whether it merits a spot in a concepts article. 
+
+However, we should be selective. Not every concept or “About X” section needs its own article. Generally this comes down to how much information will be useful to the user that we need to include.  
 
 ## How to write conceptual content
 
-For the conceptual content template, see [AUTOTITLE](/contributing/writing-for-github-docs/templates#conceptual-article-template).
+For the conceptual content template, see [AUTOTITLE](/contributing/writing-for-github-docs/templates#concepts-article-template).
 
 * Describe in plain language what the feature, product, or topic is.
 * Describe its purpose and why it’s useful to the reader.
 * Share use cases or examples.
-* If relevant, describe how the feature or topic works (be mindful of audience and the right location for deep dives into technical details).
-* Highlight any details the reader needs to know to use the feature.
-* Include next steps for getting started with the feature (whether through further reading links or content within the article itself).
 
 ## Titles for conceptual content
 
-* Conceptual articles or headers of conceptual sections start with "About [subject]”.
+Short titles for articles should be one word or a noun phrase. If the articles appear under Concepts in the sidebar avoid using "About", unless the article appears under a heading of the same name. Ex: "Coding agent" and "About coding agent".  
+
+Headers of conceptual sections in articles start with "About [subject]”.
 * Use a noun to describe the subject.
   * Use: "About {% data variables.product.prodname_code_scanning %}"
   * Avoid: "About scanning your code for vulnerabilities"

content/contributing/style-guide-and-content-model/index.md

@@ -9,7 +9,7 @@ children:
     - /style-guide
     - /about-the-content-model
     - /contents-of-a-github-docs-article
-    - /conceptual-content-type
+    - /concepts-content-type
     - /reference-content-type
     - /how-to-content-type
     - /troubleshooting-content-type

content/contributing/writing-for-github-docs/templates.md

@@ -9,9 +9,9 @@ category:
   - Follow the style guide and content model
 ---
 
-## Conceptual article template
+## Concepts article template
 
-Use the content model for full instructions and examples on how to write conceptual content. For more information, see [AUTOTITLE](/contributing/style-guide-and-content-model/conceptual-content-type).
+Use the content model for full instructions and examples on how to write conceptual content. For more information, see [AUTOTITLE](/contributing/style-guide-and-content-model/concepts-content-type).
 
 <!-- markdownlint-disable search-replace -->
 
@@ -27,7 +27,7 @@ versions:
 ---
 
 {% comment %}
-- Follow the guidelines in https://docs.github.com/contributing/writing-for-github-docs/content-model#conceptual to write this article.
+- Follow the guidelines in https://docs.github.com/contributing/writing-for-github-docs/content-model to write this article.
 - Great intros give readers a quick understanding of what's in the article, so they can tell whether it's relevant to them before moving ahead. For more tips, see https://docs.github.com/contributing/writing-for-github-docs/content-model
 - For product callout info, see https://github.com/github/docs/tree/main/content#product
 - For product version instructions, see https://github.com/github/docs/tree/main/content#versioning