WIP look at replacing "procedural" with "how-to" (#59790)

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Melanie Yarbrough <11952755+myarb@users.noreply.github.com>
Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: 5 people

content/contributing/style-guide-and-content-model/how-to-content-type.md

@@ -0,0 +1,48 @@
+---
+title: How-to content type
+intro: Explain how to complete a task using {% data variables.product.github %} products and features.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+category:
+  - Follow the style guide and content model
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /contributing/style-guide-and-content-model/procedural-content-type
+---
+
+How-tos contain numbered steps that describe how to use {% data variables.product.prodname_dotcom %} products to accomplish a task. Generally, they are necessary to get the most from using {% data variables.product.prodname_dotcom %}. 
+
+How-to articles focus on the minimum essential steps for completing a task. They may link to other content types as prerequisites (especially concepts or reference) or next steps (especially tutorials). In keeping with our linking strategy, these should be used only when explicitly useful and necessary.
+
+Generally including 1-2 brief introductory sentences before the steps is fine. If more explanation beyond a couple of sentences is needed, consider adding the information instead as a conceptual article. 
+
+Troubleshooting is its own content type, but how-to articles can include short troubleshooting sections where this helps people complete the task.
+
+## Titles for how-to articles
+
+How-to article titles and sections within articles are task-based and begin with a gerund.
+* Use: "Applying for a student developer pack"
+Use active and specific verbs (brainstorm or use a thesaurus when needed).
+Titles specifically describe the task contained within the article or header, but are general enough to reflect all of the content.
+
+How-to article short titles use short, non-gerund verb phrases. Short titles appear in the sidebar navigation.
+* Use: “Manage your plan” or “Create issues with Copilot”
+
+## How-to considerations
+
+For the how-to content template, see [AUTOTITLE](/contributing/writing-for-github-docs/templates#procedural-article-template).
+
+* Follow the style guidelines for procedural steps in [AUTOTITLE](/contributing/style-guide-and-content-model/style-guide#procedural-steps).
+* How-to content can get repetitive––look for opportunities to group related content into a single longer article.
+  * Group multiple related how-tos into a single article unless there's a compelling reason not to.
+  * If disabling a setting or undoing a task requires the same steps and has no special implications, do not write a separate how-to.
+  * If disabling a setting or undoing a task requires different steps or has important or special implications, create a longer article to contain both how-tos. 
+* Always include the intended outcome of the how-to (generally this will be the title).
+* Include troubleshooting tips in known pain points.
+
+## Examples of how-to content
+
+{% ifversion fpt or ghec %}* [AUTOTITLE](/copilot/how-tos/provide-context/use-copilot-spaces/create-copilot-spaces){% endif %}
+* [AUTOTITLE](/actions/using-workflows/using-starter-workflows)

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

@@ -11,7 +11,7 @@ children:
     - /contents-of-a-github-docs-article
     - /conceptual-content-type
     - /referential-content-type
-    - /procedural-content-type
+    - /how-to-content-type
     - /troubleshooting-content-type
     - /release-note-content-type
     - /quickstart-content-type