mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-07 18:17:22 +00:00
added article for release notes
This commit is contained in:
Nidhi Doshi
parent
55a160eba3
commit
1c4a249480
161
windows/deployment/do/mcc-ent-release-notes.md
Normal file
161
windows/deployment/do/mcc-ent-release-notes.md
Normal file
@ -0,0 +1,161 @@
|
||||
---
|
||||
title: MCC for Enterprise and Education Release Notes
|
||||
description: Release Notes for Microsoft Connected Cache (MCC) for Enterprise and Education.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.author: nidos
|
||||
author: cmknox
|
||||
manager: aaroncz
|
||||
ms.reviewer: mstewart
|
||||
ms.collection: tier3
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
ms.date: 09/04/2024
|
||||
---
|
||||
|
||||
<!--
|
||||
Remove all the comments in this template before you sign-off or merge to the main branch.
|
||||
|
||||
This template provides the basic structure of a Concept article pattern. See the [instructions - Concept](../level4/article-concept.md) in the pattern library.
|
||||
|
||||
You can provide feedback about this template at: https://aka.ms/patterns-feedback
|
||||
|
||||
Concept is an article pattern that defines what something is or explains an abstract idea.
|
||||
|
||||
There are several situations that might call for writing a Concept article, including:
|
||||
|
||||
* If there's a new idea that's central to a service or product, that idea must be explained so that customers understand the value of the service or product as it relates to their circumstances. A good recent example is the concept of containerization or the concept of scalability.
|
||||
* If there's optional information or explanations that are common to several Tutorials or How-to guides, this information can be consolidated and single-sourced in a full-bodied Concept article for you to reference.
|
||||
* If a service or product is extensible, advanced users might modify it to better suit their application. It's better that advanced users fully understand the reasoning behind the design choices and everything else "under the hood" so that their variants are more robust, thereby improving their experience.
|
||||
|
||||
-->
|
||||
|
||||
<!-- 1. H1
|
||||
-----------------------------------------------------------------------------
|
||||
|
||||
Required. Set expectations for what the content covers, so customers know the content meets their needs. The H1 should NOT begin with a verb.
|
||||
|
||||
Reflect the concept that undergirds an action, not the action itself. The H1 must start with:
|
||||
|
||||
* "\<noun phrase\> concept(s)", or
|
||||
* "What is \<noun\>?", or
|
||||
* "\<noun\> overview"
|
||||
|
||||
Concept articles are primarily distinguished by what they aren't:
|
||||
|
||||
* They aren't procedural articles. They don't show how to complete a task.
|
||||
* They don't have specific end states, other than conveying an underlying idea, and don't have concrete, sequential actions for the user to take.
|
||||
|
||||
One clear sign of a procedural article would be the use of a numbered list. With rare exception, numbered lists shouldn't appear in Concept articles.
|
||||
|
||||
-->
|
||||
|
||||
# [\<noun phrase\> concept(s)]
|
||||
TODO: Add your heading
|
||||
|
||||
<!-- 2. Introductory paragraph
|
||||
----------------------------------------------------------
|
||||
|
||||
Required. Lead with a light intro that describes what the article covers. Answer the fundamental “why would I want to know this?” question. Keep it short.
|
||||
|
||||
* Answer the fundamental "Why do I want this knowledge?" question.
|
||||
* Don't start the article with a bunch of notes or caveats.
|
||||
* Don’t link away from the article in the introduction.
|
||||
* For definitive concepts, it's better to lead with a sentence in the form, "X is a (type of) Y that does Z."
|
||||
|
||||
-->
|
||||
|
||||
[Introductory paragraph]
|
||||
TODO: Add your introductory paragraph
|
||||
|
||||
<!-- 3. Prerequisites --------------------------------------------------------------------
|
||||
|
||||
Optional: Make **Prerequisites** your first H2 in the article. Use clear and unambiguous
|
||||
language and use a unordered list format.
|
||||
|
||||
-->
|
||||
|
||||
## Prerequisites
|
||||
TODO: [List the prerequisites if appropriate]
|
||||
|
||||
<!-- 4. H2s (Article body)
|
||||
--------------------------------------------------------------------
|
||||
|
||||
Required: In a series of H2 sections, the article body should discuss the ideas that explain how "X is a (type of) Y that does Z":
|
||||
|
||||
* Give each H2 a heading that sets expectations for the content that follows.
|
||||
* Follow the H2 headings with a sentence about how the section contributes to the whole.
|
||||
* Describe the concept's critical features in the context of defining what it is.
|
||||
* Provide an example of how it's used where, how it fits into the context, or what it does. If it's complex and new to the user, show at least two examples.
|
||||
* Provide a non-example if contrasting it will make it clearer to the user what the concept is.
|
||||
* Images, code blocks, or other graphical elements come after the text block it illustrates.
|
||||
* Don't number H2s.
|
||||
|
||||
-->
|
||||
|
||||
## [Section 1 heading]
|
||||
TODO: add your content
|
||||
|
||||
## [Section 2 heading]
|
||||
TODO: add your content
|
||||
|
||||
## [Section n heading]
|
||||
TODO: add your content
|
||||
|
||||
<!-- 5. Next step/Related content ------------------------------------------------------------------------
|
||||
|
||||
Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
|
||||
- For Next step, provide one link to the next step in a sequence. Use the blue box format
|
||||
- For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
|
||||
|
||||
-->
|
||||
|
||||
## Next step
|
||||
|
||||
TODO: Add your next step link(s)
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Write concepts](article-concept.md)
|
||||
|
||||
<!-- OR -->
|
||||
|
||||
## Related content
|
||||
|
||||
TODO: Add your next step link(s)
|
||||
|
||||
- [Write concepts](article-concept.md)
|
||||
|
||||
<!--
|
||||
Remove all the comments in this template before you sign-off or merge to the main branch.
|
||||
-->
|
||||
|
||||
|
||||
<!-- 6. Next step/Related content ------------------------------------------------------------------------
|
||||
|
||||
Optional: You have two options for manually curated links in this pattern: Next step and Related
|
||||
content. You don't have to use either, but don't use both. For Next step, provide one link to the
|
||||
next step in a sequence. Use the blue box format For Related content provide 1-3 links. Include some
|
||||
context so the customer can determine why they would click the link. Add a context sentence for the
|
||||
following links.
|
||||
|
||||
-->
|
||||
|
||||
## Next step
|
||||
TODO: Add your next step link(s)
|
||||
> [!div class="nextstepaction"]
|
||||
> [Write concepts](article-concept.md)
|
||||
|
||||
<!-- OR -->
|
||||
|
||||
## Related content
|
||||
TODO: Add your next step link(s)
|
||||
- [Write concepts](article-concept.md)
|
||||
|
||||
<!--
|
||||
Remove all the comments in this template before you sign-off or merge to the
|
||||
main branch.
|
||||
|
||||
-->
|
||||
Loading…
x
Reference in New Issue
Block a user