Initial commit
This commit is contained in:
Meaghan Lewis
Коммит
46282a65f3
|
|
@ -0,0 +1,9 @@
|
|||
# Microsoft Open Source Code of Conduct
|
||||
|
||||
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
|
||||
|
||||
Resources:
|
||||
|
||||
- [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/)
|
||||
- [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
|
||||
- Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns
|
||||
|
|
@ -0,0 +1,10 @@
|
|||
# FAQ
|
||||
|
||||
## What's the timeline for getting artwork for badges/trophies?
|
||||
|
||||
Practically speaking, the ETA has been about 3 weeks due to backlog.
|
||||
|
||||
## What languages are our content localized into?
|
||||
|
||||
We're localized into the same languages Azure. Localization is based on what folder you put the content into.
|
||||
See this doc for more info: https://review.docs.microsoft.com/en-us/learn-docs/docs/microsoftlearn-faq?branch=master
|
||||
|
|
@ -0,0 +1,395 @@
|
|||
Attribution 4.0 International
|
||||
|
||||
=======================================================================
|
||||
|
||||
Creative Commons Corporation ("Creative Commons") is not a law firm and
|
||||
does not provide legal services or legal advice. Distribution of
|
||||
Creative Commons public licenses does not create a lawyer-client or
|
||||
other relationship. Creative Commons makes its licenses and related
|
||||
information available on an "as-is" basis. Creative Commons gives no
|
||||
warranties regarding its licenses, any material licensed under their
|
||||
terms and conditions, or any related information. Creative Commons
|
||||
disclaims all liability for damages resulting from their use to the
|
||||
fullest extent possible.
|
||||
|
||||
Using Creative Commons Public Licenses
|
||||
|
||||
Creative Commons public licenses provide a standard set of terms and
|
||||
conditions that creators and other rights holders may use to share
|
||||
original works of authorship and other material subject to copyright
|
||||
and certain other rights specified in the public license below. The
|
||||
following considerations are for informational purposes only, are not
|
||||
exhaustive, and do not form part of our licenses.
|
||||
|
||||
Considerations for licensors: Our public licenses are
|
||||
intended for use by those authorized to give the public
|
||||
permission to use material in ways otherwise restricted by
|
||||
copyright and certain other rights. Our licenses are
|
||||
irrevocable. Licensors should read and understand the terms
|
||||
and conditions of the license they choose before applying it.
|
||||
Licensors should also secure all rights necessary before
|
||||
applying our licenses so that the public can reuse the
|
||||
material as expected. Licensors should clearly mark any
|
||||
material not subject to the license. This includes other CC-
|
||||
licensed material, or material used under an exception or
|
||||
limitation to copyright. More considerations for licensors:
|
||||
wiki.creativecommons.org/Considerations_for_licensors
|
||||
|
||||
Considerations for the public: By using one of our public
|
||||
licenses, a licensor grants the public permission to use the
|
||||
licensed material under specified terms and conditions. If
|
||||
the licensor's permission is not necessary for any reason--for
|
||||
example, because of any applicable exception or limitation to
|
||||
copyright--then that use is not regulated by the license. Our
|
||||
licenses grant only permissions under copyright and certain
|
||||
other rights that a licensor has authority to grant. Use of
|
||||
the licensed material may still be restricted for other
|
||||
reasons, including because others have copyright or other
|
||||
rights in the material. A licensor may make special requests,
|
||||
such as asking that all changes be marked or described.
|
||||
Although not required by our licenses, you are encouraged to
|
||||
respect those requests where reasonable. More_considerations
|
||||
for the public:
|
||||
wiki.creativecommons.org/Considerations_for_licensees
|
||||
|
||||
=======================================================================
|
||||
|
||||
Creative Commons Attribution 4.0 International Public License
|
||||
|
||||
By exercising the Licensed Rights (defined below), You accept and agree
|
||||
to be bound by the terms and conditions of this Creative Commons
|
||||
Attribution 4.0 International Public License ("Public License"). To the
|
||||
extent this Public License may be interpreted as a contract, You are
|
||||
granted the Licensed Rights in consideration of Your acceptance of
|
||||
these terms and conditions, and the Licensor grants You such rights in
|
||||
consideration of benefits the Licensor receives from making the
|
||||
Licensed Material available under these terms and conditions.
|
||||
|
||||
|
||||
Section 1 -- Definitions.
|
||||
|
||||
a. Adapted Material means material subject to Copyright and Similar
|
||||
Rights that is derived from or based upon the Licensed Material
|
||||
and in which the Licensed Material is translated, altered,
|
||||
arranged, transformed, or otherwise modified in a manner requiring
|
||||
permission under the Copyright and Similar Rights held by the
|
||||
Licensor. For purposes of this Public License, where the Licensed
|
||||
Material is a musical work, performance, or sound recording,
|
||||
Adapted Material is always produced where the Licensed Material is
|
||||
synched in timed relation with a moving image.
|
||||
|
||||
b. Adapter's License means the license You apply to Your Copyright
|
||||
and Similar Rights in Your contributions to Adapted Material in
|
||||
accordance with the terms and conditions of this Public License.
|
||||
|
||||
c. Copyright and Similar Rights means copyright and/or similar rights
|
||||
closely related to copyright including, without limitation,
|
||||
performance, broadcast, sound recording, and Sui Generis Database
|
||||
Rights, without regard to how the rights are labeled or
|
||||
categorized. For purposes of this Public License, the rights
|
||||
specified in Section 2(b)(1)-(2) are not Copyright and Similar
|
||||
Rights.
|
||||
|
||||
d. Effective Technological Measures means those measures that, in the
|
||||
absence of proper authority, may not be circumvented under laws
|
||||
fulfilling obligations under Article 11 of the WIPO Copyright
|
||||
Treaty adopted on December 20, 1996, and/or similar international
|
||||
agreements.
|
||||
|
||||
e. Exceptions and Limitations means fair use, fair dealing, and/or
|
||||
any other exception or limitation to Copyright and Similar Rights
|
||||
that applies to Your use of the Licensed Material.
|
||||
|
||||
f. Licensed Material means the artistic or literary work, database,
|
||||
or other material to which the Licensor applied this Public
|
||||
License.
|
||||
|
||||
g. Licensed Rights means the rights granted to You subject to the
|
||||
terms and conditions of this Public License, which are limited to
|
||||
all Copyright and Similar Rights that apply to Your use of the
|
||||
Licensed Material and that the Licensor has authority to license.
|
||||
|
||||
h. Licensor means the individual(s) or entity(ies) granting rights
|
||||
under this Public License.
|
||||
|
||||
i. Share means to provide material to the public by any means or
|
||||
process that requires permission under the Licensed Rights, such
|
||||
as reproduction, public display, public performance, distribution,
|
||||
dissemination, communication, or importation, and to make material
|
||||
available to the public including in ways that members of the
|
||||
public may access the material from a place and at a time
|
||||
individually chosen by them.
|
||||
|
||||
j. Sui Generis Database Rights means rights other than copyright
|
||||
resulting from Directive 96/9/EC of the European Parliament and of
|
||||
the Council of 11 March 1996 on the legal protection of databases,
|
||||
as amended and/or succeeded, as well as other essentially
|
||||
equivalent rights anywhere in the world.
|
||||
|
||||
k. You means the individual or entity exercising the Licensed Rights
|
||||
under this Public License. Your has a corresponding meaning.
|
||||
|
||||
|
||||
Section 2 -- Scope.
|
||||
|
||||
a. License grant.
|
||||
|
||||
1. Subject to the terms and conditions of this Public License,
|
||||
the Licensor hereby grants You a worldwide, royalty-free,
|
||||
non-sublicensable, non-exclusive, irrevocable license to
|
||||
exercise the Licensed Rights in the Licensed Material to:
|
||||
|
||||
a. reproduce and Share the Licensed Material, in whole or
|
||||
in part; and
|
||||
|
||||
b. produce, reproduce, and Share Adapted Material.
|
||||
|
||||
2. Exceptions and Limitations. For the avoidance of doubt, where
|
||||
Exceptions and Limitations apply to Your use, this Public
|
||||
License does not apply, and You do not need to comply with
|
||||
its terms and conditions.
|
||||
|
||||
3. Term. The term of this Public License is specified in Section
|
||||
6(a).
|
||||
|
||||
4. Media and formats; technical modifications allowed. The
|
||||
Licensor authorizes You to exercise the Licensed Rights in
|
||||
all media and formats whether now known or hereafter created,
|
||||
and to make technical modifications necessary to do so. The
|
||||
Licensor waives and/or agrees not to assert any right or
|
||||
authority to forbid You from making technical modifications
|
||||
necessary to exercise the Licensed Rights, including
|
||||
technical modifications necessary to circumvent Effective
|
||||
Technological Measures. For purposes of this Public License,
|
||||
simply making modifications authorized by this Section 2(a)
|
||||
(4) never produces Adapted Material.
|
||||
|
||||
5. Downstream recipients.
|
||||
|
||||
a. Offer from the Licensor -- Licensed Material. Every
|
||||
recipient of the Licensed Material automatically
|
||||
receives an offer from the Licensor to exercise the
|
||||
Licensed Rights under the terms and conditions of this
|
||||
Public License.
|
||||
|
||||
b. No downstream restrictions. You may not offer or impose
|
||||
any additional or different terms or conditions on, or
|
||||
apply any Effective Technological Measures to, the
|
||||
Licensed Material if doing so restricts exercise of the
|
||||
Licensed Rights by any recipient of the Licensed
|
||||
Material.
|
||||
|
||||
6. No endorsement. Nothing in this Public License constitutes or
|
||||
may be construed as permission to assert or imply that You
|
||||
are, or that Your use of the Licensed Material is, connected
|
||||
with, or sponsored, endorsed, or granted official status by,
|
||||
the Licensor or others designated to receive attribution as
|
||||
provided in Section 3(a)(1)(A)(i).
|
||||
|
||||
b. Other rights.
|
||||
|
||||
1. Moral rights, such as the right of integrity, are not
|
||||
licensed under this Public License, nor are publicity,
|
||||
privacy, and/or other similar personality rights; however, to
|
||||
the extent possible, the Licensor waives and/or agrees not to
|
||||
assert any such rights held by the Licensor to the limited
|
||||
extent necessary to allow You to exercise the Licensed
|
||||
Rights, but not otherwise.
|
||||
|
||||
2. Patent and trademark rights are not licensed under this
|
||||
Public License.
|
||||
|
||||
3. To the extent possible, the Licensor waives any right to
|
||||
collect royalties from You for the exercise of the Licensed
|
||||
Rights, whether directly or through a collecting society
|
||||
under any voluntary or waivable statutory or compulsory
|
||||
licensing scheme. In all other cases the Licensor expressly
|
||||
reserves any right to collect such royalties.
|
||||
|
||||
|
||||
Section 3 -- License Conditions.
|
||||
|
||||
Your exercise of the Licensed Rights is expressly made subject to the
|
||||
following conditions.
|
||||
|
||||
a. Attribution.
|
||||
|
||||
1. If You Share the Licensed Material (including in modified
|
||||
form), You must:
|
||||
|
||||
a. retain the following if it is supplied by the Licensor
|
||||
with the Licensed Material:
|
||||
|
||||
i. identification of the creator(s) of the Licensed
|
||||
Material and any others designated to receive
|
||||
attribution, in any reasonable manner requested by
|
||||
the Licensor (including by pseudonym if
|
||||
designated);
|
||||
|
||||
ii. a copyright notice;
|
||||
|
||||
iii. a notice that refers to this Public License;
|
||||
|
||||
iv. a notice that refers to the disclaimer of
|
||||
warranties;
|
||||
|
||||
v. a URI or hyperlink to the Licensed Material to the
|
||||
extent reasonably practicable;
|
||||
|
||||
b. indicate if You modified the Licensed Material and
|
||||
retain an indication of any previous modifications; and
|
||||
|
||||
c. indicate the Licensed Material is licensed under this
|
||||
Public License, and include the text of, or the URI or
|
||||
hyperlink to, this Public License.
|
||||
|
||||
2. You may satisfy the conditions in Section 3(a)(1) in any
|
||||
reasonable manner based on the medium, means, and context in
|
||||
which You Share the Licensed Material. For example, it may be
|
||||
reasonable to satisfy the conditions by providing a URI or
|
||||
hyperlink to a resource that includes the required
|
||||
information.
|
||||
|
||||
3. If requested by the Licensor, You must remove any of the
|
||||
information required by Section 3(a)(1)(A) to the extent
|
||||
reasonably practicable.
|
||||
|
||||
4. If You Share Adapted Material You produce, the Adapter's
|
||||
License You apply must not prevent recipients of the Adapted
|
||||
Material from complying with this Public License.
|
||||
|
||||
|
||||
Section 4 -- Sui Generis Database Rights.
|
||||
|
||||
Where the Licensed Rights include Sui Generis Database Rights that
|
||||
apply to Your use of the Licensed Material:
|
||||
|
||||
a. for the avoidance of doubt, Section 2(a)(1) grants You the right
|
||||
to extract, reuse, reproduce, and Share all or a substantial
|
||||
portion of the contents of the database;
|
||||
|
||||
b. if You include all or a substantial portion of the database
|
||||
contents in a database in which You have Sui Generis Database
|
||||
Rights, then the database in which You have Sui Generis Database
|
||||
Rights (but not its individual contents) is Adapted Material; and
|
||||
|
||||
c. You must comply with the conditions in Section 3(a) if You Share
|
||||
all or a substantial portion of the contents of the database.
|
||||
|
||||
For the avoidance of doubt, this Section 4 supplements and does not
|
||||
replace Your obligations under this Public License where the Licensed
|
||||
Rights include other Copyright and Similar Rights.
|
||||
|
||||
|
||||
Section 5 -- Disclaimer of Warranties and Limitation of Liability.
|
||||
|
||||
a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
|
||||
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
|
||||
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
|
||||
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
|
||||
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
|
||||
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
|
||||
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
|
||||
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
|
||||
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
|
||||
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
|
||||
|
||||
b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
|
||||
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
|
||||
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
|
||||
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
|
||||
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
|
||||
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
|
||||
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
|
||||
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
|
||||
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
|
||||
|
||||
c. The disclaimer of warranties and limitation of liability provided
|
||||
above shall be interpreted in a manner that, to the extent
|
||||
possible, most closely approximates an absolute disclaimer and
|
||||
waiver of all liability.
|
||||
|
||||
|
||||
Section 6 -- Term and Termination.
|
||||
|
||||
a. This Public License applies for the term of the Copyright and
|
||||
Similar Rights licensed here. However, if You fail to comply with
|
||||
this Public License, then Your rights under this Public License
|
||||
terminate automatically.
|
||||
|
||||
b. Where Your right to use the Licensed Material has terminated under
|
||||
Section 6(a), it reinstates:
|
||||
|
||||
1. automatically as of the date the violation is cured, provided
|
||||
it is cured within 30 days of Your discovery of the
|
||||
violation; or
|
||||
|
||||
2. upon express reinstatement by the Licensor.
|
||||
|
||||
For the avoidance of doubt, this Section 6(b) does not affect any
|
||||
right the Licensor may have to seek remedies for Your violations
|
||||
of this Public License.
|
||||
|
||||
c. For the avoidance of doubt, the Licensor may also offer the
|
||||
Licensed Material under separate terms or conditions or stop
|
||||
distributing the Licensed Material at any time; however, doing so
|
||||
will not terminate this Public License.
|
||||
|
||||
d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
|
||||
License.
|
||||
|
||||
|
||||
Section 7 -- Other Terms and Conditions.
|
||||
|
||||
a. The Licensor shall not be bound by any additional or different
|
||||
terms or conditions communicated by You unless expressly agreed.
|
||||
|
||||
b. Any arrangements, understandings, or agreements regarding the
|
||||
Licensed Material not stated herein are separate from and
|
||||
independent of the terms and conditions of this Public License.
|
||||
|
||||
|
||||
Section 8 -- Interpretation.
|
||||
|
||||
a. For the avoidance of doubt, this Public License does not, and
|
||||
shall not be interpreted to, reduce, limit, restrict, or impose
|
||||
conditions on any use of the Licensed Material that could lawfully
|
||||
be made without permission under this Public License.
|
||||
|
||||
b. To the extent possible, if any provision of this Public License is
|
||||
deemed unenforceable, it shall be automatically reformed to the
|
||||
minimum extent necessary to make it enforceable. If the provision
|
||||
cannot be reformed, it shall be severed from this Public License
|
||||
without affecting the enforceability of the remaining terms and
|
||||
conditions.
|
||||
|
||||
c. No term or condition of this Public License will be waived and no
|
||||
failure to comply consented to unless expressly agreed to by the
|
||||
Licensor.
|
||||
|
||||
d. Nothing in this Public License constitutes or may be interpreted
|
||||
as a limitation upon, or waiver of, any privileges and immunities
|
||||
that apply to the Licensor or You, including from the legal
|
||||
processes of any jurisdiction or authority.
|
||||
|
||||
|
||||
=======================================================================
|
||||
|
||||
Creative Commons is not a party to its public
|
||||
licenses. Notwithstanding, Creative Commons may elect to apply one of
|
||||
its public licenses to material it publishes and in those instances
|
||||
will be considered the “Licensor.” The text of the Creative Commons
|
||||
public licenses is dedicated to the public domain under the CC0 Public
|
||||
Domain Dedication. Except for the limited purpose of indicating that
|
||||
material is shared under a Creative Commons public license or as
|
||||
otherwise permitted by the Creative Commons policies published at
|
||||
creativecommons.org/policies, Creative Commons does not authorize the
|
||||
use of the trademark "Creative Commons" or any other trademark or logo
|
||||
of Creative Commons without its prior written consent including,
|
||||
without limitation, in connection with any unauthorized modifications
|
||||
to any of its public licenses or any other arrangements,
|
||||
understandings, or agreements concerning use of licensed material. For
|
||||
the avoidance of doubt, this paragraph does not form part of the
|
||||
public licenses.
|
||||
|
||||
Creative Commons may be contacted at creativecommons.org.
|
||||
|
|
@ -0,0 +1,21 @@
|
|||
MIT License
|
||||
|
||||
Copyright (c) Microsoft Corporation.
|
||||
|
||||
Permission is hereby granted, free of charge, to any person obtaining a copy
|
||||
of this software and associated documentation files (the "Software"), to deal
|
||||
in the Software without restriction, including without limitation the rights
|
||||
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
||||
copies of the Software, and to permit persons to whom the Software is
|
||||
furnished to do so, subject to the following conditions:
|
||||
|
||||
The above copyright notice and this permission notice shall be included in all
|
||||
copies or substantial portions of the Software.
|
||||
|
||||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
||||
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
||||
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
||||
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
||||
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
||||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
||||
SOFTWARE
|
||||
|
|
@ -0,0 +1,163 @@
|
|||
|
||||
# Learn Template
|
||||
|
||||
This repo is designed to help you create and scaffold your Student/Step 0 content for Microsoft Learn.
|
||||
|
||||
If you've found this repo, but haven't yet:
|
||||
|
||||
1. Read our [Student/Step 0 content strategy doc](https://microsoft-my.sharepoint.com/:w:/g/personal/shanama_microsoft_com1/EWcQMH7tyKNNstzafKABeTwB7TVKhOm5AUoWcBjIvwA3kg?e=zXatFa)
|
||||
1. Reached out to Shana Matthews (shanama)
|
||||
|
||||
Please take those steps before starting on your content creation journey.
|
||||
|
||||
## Requirements
|
||||
|
||||
Talk about the general process:
|
||||
- Do your research:
|
||||
- Does this content already exist? What are you bringing new?
|
||||
- Will this work on a student account? (not a deal breaker if not, but would be nice)
|
||||
- Will this work on Mac and PC? How about browser (with CodeSpaces)?
|
||||
- Propose to Shana 💍 with [these instructions](./module-proposal.md)
|
||||
- Decide on a timeline for project completion
|
||||
- Decide what you're building (module, lp)
|
||||
- Outline it using [this module design template](./module-design-template.md) and share with Shana to ensure it is the right size and format
|
||||
- Review the [Learn content requirements](https://review.docs.microsoft.com/en-us/learn-docs/docs/content-requirements?branch=master)
|
||||
- Clone this template repo
|
||||
- Write your content
|
||||
- Work with Shana to fill in the yml files
|
||||
- Get someone to review it
|
||||
- Deliver the repo to Shana
|
||||
- Respond to PR/DevOps requests from Aquent in the Learn repo
|
||||
- Review the content once it's live
|
||||
- Participate in a monthly bug bash (if necessary for your content, Shana will let you know)
|
||||
|
||||
# Module
|
||||
|
||||
So you want to write a module on it's own or part of a learning path, great!
|
||||
|
||||
## Files
|
||||
|
||||
- Module Folder:
|
||||
- index.yml: Contains the outline of hte content and the actual titles, descriptions, etc
|
||||
- unit.yml (for each unit): Contains the outline of hte content and the actual titles, descriptions, etc
|
||||
- Each module should have an introduction.yml and summary.yml file
|
||||
- summary.yml: Additionally contains the knowledge check questions (see below)
|
||||
- Media Folder
|
||||
- README.md: Table containing the file, URL, Date Accesses, and Copyright information if taken from the web for an easy legal review if necessary
|
||||
- All images/media to be used throughout the module
|
||||
- Includes Folder
|
||||
- unit.md (for each unit): Contains the actual content for each unit
|
||||
- Each module should have an introduction.md and summary.md file
|
||||
|
||||
## Knowledge Checks
|
||||
|
||||
All modules are **required** to either have at least one knowledge check or at least one hands-on exercise unit that uses the sandbox in some way. Having both is better.
|
||||
|
||||
We recommend having at least one knowledge check per module, even if you do have hands-on exercises that use the sandbox. Knowledge checks are:
|
||||
- Multiple choice (no True/False)
|
||||
- Don't have "All/None of the above" as an option
|
||||
- Should actually contribute to learning
|
||||
- Need to have the correct answer indicated
|
||||
- Need to have explanations for why each answer is either correct or incorrect
|
||||
|
||||
Knowledge checks can be embedded in a unit or a standalone unit. If embedded, knowledge checks should be 2-3 questions. If standalone, they must be the second-to-last unit in a module and must be 3-5 questions. They should not be combined with the Summary unit, instead they should come right before.
|
||||
|
||||
# Learning Path
|
||||
|
||||
So you decided to build a Learning Path for your Modules! Awesome!
|
||||
|
||||
## Files
|
||||
|
||||
Learning paths are defined by a single index.yml file.
|
||||
|
||||
LP Folder
|
||||
- README.md: Contains the LP title and the Module Titles for quick reference
|
||||
- index.yml: Contains the outline of the Modules within the Learning Path and the actual titles, descriptions, etc
|
||||
|
||||
# Getting Started
|
||||
|
||||
If you are going to build a module on it's own, we recommend starting from the module-1 folder and deleteing the learning-path-1 folder from your repo. Copy the module-1 folder for each module you want to create.
|
||||
|
||||
If you are going to build modules as part of a learning path, copy the lp1-module-1 folder for each module you want to create and the learning-path-1 folder for each learning path you want to create. Module folders do not live within a Learning Path's folder structure.
|
||||
|
||||
Don't Forget:
|
||||
- Rename folders and files to match YOUR content.
|
||||
- Change the contents of this README to only have the following:
|
||||
|
||||
|
||||
# TITLE THE PROJECT
|
||||
|
||||
This repo contains new Microsoft Learn content for....< DESCRIBE YOUR CONTENT >
|
||||
|
||||
## Timeline
|
||||
|
||||
< TO BE FILLED IN WITH SHANA >
|
||||
|
||||
| Item | Owner | Status | Deadline |
|
||||
|------|-------|--------|----------|
|
||||
| Propose content | < YOUR NAME > | Not Started | < DATE > |
|
||||
| Get content into Learn and with the vendor | @shanama | Not Started | < DATE > |
|
||||
| Request art assets | @shanama | Not Started | < Date > |
|
||||
| Write Content | < YOUR NAME > | Not Started | < DATE > |
|
||||
| Review Content | < YOUR REVIEWER(S) NAME(S) > | Not Started | < DATE > |
|
||||
| Content to Aquent | < YOUR NAME > | Not Started | < DATE > |
|
||||
| Content Draft on Learn | Aquent | Not Started | < DATE > |
|
||||
| Sign off on Content on Learn | < YOUR NAME > | Not Started | < DATE > |
|
||||
| Publish Content | @shanama | Not Started | < DATE > |
|
||||
| Review Live Content | < YOUR NAME > | Not Started | < DATE > |
|
||||
|
||||
## Content Overview
|
||||
|
||||
< Description of content here >
|
||||
|
||||
| Type | Title | Description | Duration |
|
||||
|------|-------|-------------|----------|
|
||||
| Learning Path | My LP 1 | This LP is so cool | <sum of modules> |
|
||||
| Module | My M1 as part of LP1 | This module is awesome | 15-45 min |
|
||||
| Module | My M2 as part of LP1 | This module is awesome | 15-45 min |
|
||||
| Module | My M2 as part of LP1 | This module is awesome | 15-45 min |
|
||||
| Learning Path | My LP 2 | This LP is so cool | <sum of modules> |
|
||||
| Module | My M1 as part of LP2 | This module is awesome | 15-45 min |
|
||||
| Module | My M2 as part of LP2 | This module is awesome | 15-45 min |
|
||||
| Module | My M2 as part of LP2 | This module is awesome | 15-45 min |
|
||||
|
||||
## Promotion and Marketing
|
||||
|
||||
[Link to marketing plan](TBD): Sarah will have a template for this
|
||||
|
||||
## Other Information
|
||||
|
||||
< Any comments you want to add here, brainstorming, research, etc >
|
||||
|
||||
|
||||
# Contributing
|
||||
|
||||
This project welcomes contributions and suggestions. Most contributions require you to agree to a
|
||||
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
|
||||
the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
|
||||
|
||||
When you submit a pull request, a CLA bot will automatically determine whether you need to provide
|
||||
a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
|
||||
provided by the bot. You will only need to do this once across all repos using our CLA.
|
||||
|
||||
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
|
||||
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
|
||||
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
|
||||
|
||||
# Legal Notices
|
||||
|
||||
Microsoft and any contributors grant you a license to the Microsoft documentation and other content
|
||||
in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode),
|
||||
see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the
|
||||
[LICENSE-CODE](LICENSE-CODE) file.
|
||||
|
||||
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation
|
||||
may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
|
||||
The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
|
||||
Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
|
||||
|
||||
Privacy information can be found at https://privacy.microsoft.com/en-us/
|
||||
|
||||
Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents,
|
||||
or trademarks, whether by implication, estoppel or otherwise.
|
||||
|
||||
|
|
@ -0,0 +1,41 @@
|
|||
<!-- BEGIN MICROSOFT SECURITY.MD V0.0.5 BLOCK -->
|
||||
|
||||
## Security
|
||||
|
||||
Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
|
||||
|
||||
If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below.
|
||||
|
||||
## Reporting Security Issues
|
||||
|
||||
**Please do not report security vulnerabilities through public GitHub issues.**
|
||||
|
||||
Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).
|
||||
|
||||
If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc).
|
||||
|
||||
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
|
||||
|
||||
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
|
||||
|
||||
* Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
|
||||
* Full paths of source file(s) related to the manifestation of the issue
|
||||
* The location of the affected source code (tag/branch/commit or direct URL)
|
||||
* Any special configuration required to reproduce the issue
|
||||
* Step-by-step instructions to reproduce the issue
|
||||
* Proof-of-concept or exploit code (if possible)
|
||||
* Impact of the issue, including how an attacker might exploit the issue
|
||||
|
||||
This information will help us triage your report more quickly.
|
||||
|
||||
If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://microsoft.com/msrc/bounty) page for more details about our active programs.
|
||||
|
||||
## Preferred Languages
|
||||
|
||||
We prefer all communications to be in English.
|
||||
|
||||
## Policy
|
||||
|
||||
Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).
|
||||
|
||||
<!-- END MICROSOFT SECURITY.MD BLOCK -->
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
# Learning Path
|
||||
|
||||
- Learning paths must be at least 3 modules and preferably no longer than 7.
|
||||
- Modules can be contained within multiple learning paths.
|
||||
- You may put other, already existing modules in your learning path.
|
||||
|
||||
Please fill out the below info to help us keep your learning path organized properly.
|
||||
|
||||
Learning Path Title:
|
||||
< TITLE >
|
||||
|
||||
Module Titles:
|
||||
- < TITLE >
|
||||
- < TITLE >
|
||||
- < TITLE >
|
||||
- < TITLE >
|
||||
|
||||
## Instructions
|
||||
|
||||
Learning paths are defined by a single yaml file. Please fill out all commented fields in the example yaml file in this folder.
|
||||
|
||||
For each new module in your learning path, copy the module folder and do all content development there. Modules & their content do NOT live inside a learning path folder.
|
||||
|
|
@ -0,0 +1,38 @@
|
|||
### YamlMime:LearningPath
|
||||
|
||||
# Fill out all fields with comments
|
||||
uid:
|
||||
metadata:
|
||||
title: # Add your desired learning path title. All titles must be sentence-case.
|
||||
description: # Add a short description of your learning path for search engines.
|
||||
brand:
|
||||
ms.date:
|
||||
author: # Your GitHub username (or whomever you'd like to give author attribution to)
|
||||
ms.author: shanama # Leave this as shanama unless you want content bugs assigned directly to you
|
||||
ms.topic: interactive-tutorial
|
||||
ms.prod: learning-azure
|
||||
title: # Your desired learning path title. Same as above.
|
||||
summary: | # Add a description for your learning path to be displayed to users in the given form. Can include the description from above.
|
||||
<Short description of your learning path>
|
||||
|
||||
In this learning path you will:
|
||||
- <learning objective 1>
|
||||
- <learning objective 2>
|
||||
- <learning objective 3>
|
||||
|
||||
prerequisites: | # Fill in a detailed list of prerequisites in this form
|
||||
# - prereq 1
|
||||
# - prereq 2
|
||||
iconUrl: /learn/achievements/generic-trophy.svg # TODO change
|
||||
levels:
|
||||
- beginner
|
||||
roles:
|
||||
# - Add relevant user role(s) (developer, data scientist, etc.)
|
||||
- student
|
||||
products:
|
||||
-
|
||||
modules:
|
||||
-
|
||||
-
|
||||
trophy:
|
||||
uid:
|
||||
|
|
@ -0,0 +1,14 @@
|
|||
### YamlMime:ModuleUnit
|
||||
uid:
|
||||
metadata:
|
||||
title: Introduction
|
||||
description: Introduction
|
||||
ms.date:
|
||||
author: # Your GitHub username (or whomever you'd like to give author attribution to)
|
||||
ms.author: shanama # Leave this as shanama unless you want content bugs assigned directly to you
|
||||
ms.topic: interactive-tutorial
|
||||
ms.prod: learning-azure
|
||||
title: Introduction
|
||||
durationInMinutes:
|
||||
content: |
|
||||
[!include[](includes/0-introduction.md)]
|
||||
|
|
@ -0,0 +1,14 @@
|
|||
### YamlMime:ModuleUnit
|
||||
uid:
|
||||
metadata:
|
||||
title:
|
||||
description:
|
||||
ms.date:
|
||||
author: # Your GitHub username (or whomever you'd like to give author attribution to)
|
||||
ms.author: shanama # Leave this as shanama unless you want content bugs assigned directly to you
|
||||
ms.topic: interactive-tutorial
|
||||
ms.prod: learning-azure
|
||||
title:
|
||||
durationInMinutes:
|
||||
content: |
|
||||
[!include[](includes/1-unit.md)]
|
||||
|
|
@ -0,0 +1,59 @@
|
|||
### YamlMime:ModuleUnit
|
||||
uid:
|
||||
metadata:
|
||||
title:
|
||||
description:
|
||||
ms.date:
|
||||
author: # Your GitHub username (or whomever you'd like to give author attribution to)
|
||||
ms.author: shanama # Leave this as shanama unless you want content bugs assigned directly to you
|
||||
ms.topic: interactive-tutorial
|
||||
ms.prod: learning-azure
|
||||
title:
|
||||
durationInMinutes:
|
||||
content: |
|
||||
[!include[](includes/2-unit.md)]
|
||||
quiz:
|
||||
title: Check your knowledge
|
||||
questions:
|
||||
- content: "Question1"
|
||||
choices:
|
||||
- content: "Answer1"
|
||||
isCorrect: false
|
||||
explanation: "Explanation1"
|
||||
- content: "Answer2"
|
||||
isCorrect: false
|
||||
explanation: "Explanation2"
|
||||
- content: "Answer3"
|
||||
isCorrect: false
|
||||
explanation: "Explanation3"
|
||||
- content: "Answer4"
|
||||
isCorrect: true
|
||||
explanation: "Explanation4"
|
||||
- content: "Question2"
|
||||
choices:
|
||||
- content: "Answer1"
|
||||
isCorrect: false
|
||||
explanation: "Explanation1"
|
||||
- content: "Answer2"
|
||||
isCorrect: false
|
||||
explanation: "Explanation2"
|
||||
- content: "Answer3"
|
||||
isCorrect: false
|
||||
explanation: "Explanation3"
|
||||
- content: "Answer4"
|
||||
isCorrect: true
|
||||
explanation: "Explanation4"
|
||||
- content: "Question3"
|
||||
choices:
|
||||
- content: "Answer1"
|
||||
isCorrect: false
|
||||
explanation: "Explanation1"
|
||||
- content: "Answer2"
|
||||
isCorrect: false
|
||||
explanation: "Explanation2"
|
||||
- content: "Answer3"
|
||||
isCorrect: false
|
||||
explanation: "Explanation3"
|
||||
- content: "Answer4"
|
||||
isCorrect: true
|
||||
explanation: "Explanation4"
|
||||
|
|
@ -0,0 +1,14 @@
|
|||
### YamlMime:ModuleUnit
|
||||
uid:
|
||||
metadata:
|
||||
title: Summary
|
||||
description: Summary
|
||||
ms.date:
|
||||
author: # Your GitHub username (or whomever you'd like to give author attribution to)
|
||||
ms.author: shanama # Leave this as shanama unless you want content bugs assigned directly to you
|
||||
ms.topic: interactive-tutorial
|
||||
ms.prod: learning-azure
|
||||
title: Summary
|
||||
durationInMinutes:
|
||||
content: |
|
||||
[!include[](includes/3-summary.md)]
|
||||
|
|
@ -0,0 +1,50 @@
|
|||
# Module
|
||||
|
||||
Please fill out the below info to help us keep your module organized properly.
|
||||
|
||||
Module Title:
|
||||
< TITLE >
|
||||
|
||||
Unit Titles:
|
||||
- Introduction
|
||||
- < TITLE >
|
||||
- < TITLE >
|
||||
- Summary
|
||||
|
||||
## Instructions
|
||||
|
||||
All modules should have this folder structure:
|
||||
|
||||
- top level module folder
|
||||
- includes
|
||||
- 0-unitname.md
|
||||
- 1-unitname.md
|
||||
- 2-unitname.md
|
||||
- etc.md
|
||||
- media
|
||||
- yourimagefile.png
|
||||
- 0-unitname.yml
|
||||
- 1-unitname.yml
|
||||
- 2-unitname.yml
|
||||
- index.yml
|
||||
|
||||
In **each** .yml file, please fill out all commented fields to the best of your ability. If you have any questions, reach out to Shana.
|
||||
|
||||
## Knowledge checks
|
||||
|
||||
All modules are required to either have at least one knowledge check or at least one hands-on exercise unit that uses the sandbox in some way. Having both is better.
|
||||
|
||||
We recommend having at least one knowledge check, even if you do have hands-on exercises that use the sandbox. Knowledge checks are:
|
||||
|
||||
- Multiple choice (no True/False)
|
||||
- Don't have "All/None of the above" as an option
|
||||
- Should actually contribute to learning
|
||||
- Need to have the correct answer indicated
|
||||
- Need to have explanations for why each answer is either correct or incorrect
|
||||
|
||||
Knowledge checks can be embedded in a unit or exist as a standalone unit.
|
||||
|
||||
- If embedded, knowledge checks should be 2-3 questions.
|
||||
- If standalone, they must be the second-to-last unit in a module and must be 3-5 questions. They should not be combined with the Summary unit, instead they should be their own unit right before.
|
||||
|
||||
Knowledge checks live inline in a unit's .yml file. It can be tedious to put them in with the correct syntax so if you'd like, you can instead put them in the unit's .md file in a reasonable format and we will translate them. Standalone knowledge check units won't have (don't need) a .md file, but you can put a dummy .md file in as a placeholder to keep consistent.
|
||||
|
|
@ -0,0 +1,13 @@
|
|||
# Introduction
|
||||
|
||||
< Introductory Content >
|
||||
|
||||
## Learning Objectives
|
||||
|
||||
In this module, you will begin to discover:
|
||||
|
||||
-
|
||||
|
||||
## Prerequisites
|
||||
|
||||
-
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
# Title matches yml
|
||||
|
||||
< Unit Text >
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
# Title matches yml
|
||||
|
||||
< Unit Text >
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
# Summary
|
||||
|
||||
< Text to go above the knowledge check >
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
### YamlMime:Module
|
||||
uid: ""
|
||||
metadata:
|
||||
title: # Add your desired module title. All titles must be sentence-case.
|
||||
description: # Add a short description for your module for search engines.
|
||||
ms.date:
|
||||
author: # Your GitHub username (or whomever you'd like to give author attribution to)
|
||||
ms.author: shanama # Leave this as shanama unless you want content bugs assigned directly to you
|
||||
ms.topic: interactive-tutorial
|
||||
ms.prod: learning-azure
|
||||
title: # Your desired module title. Same as above.
|
||||
summary: # Add a short description for your module to be displayed to users. Can be the same as above.
|
||||
abstract: |
|
||||
In this module, you will:
|
||||
# - Learning objective 1
|
||||
# - Learning objective 2
|
||||
# - etc.
|
||||
prerequisites: | # Fill in a detailed list of prerequisites in this form
|
||||
# - prereq 1
|
||||
# - prereq 2
|
||||
iconUrl: /learn/achievements/generic-badge.svg # TODO change
|
||||
levels:
|
||||
- beginner
|
||||
roles:
|
||||
# - Add relevant user role(s) (developer, data scientist, etc.)
|
||||
- student
|
||||
products:
|
||||
- ""
|
||||
units:
|
||||
- ""
|
||||
badge:
|
||||
uid: ""
|
||||
|
|
@ -0,0 +1,13 @@
|
|||
# Media folder
|
||||
|
||||
All images you include in your markdown should live in this folder and be referenced in the markdown from this folder.
|
||||
|
||||
Please fill out the below information for any images you've added to this folder that you didn't create yourself (e.g. screenshots).
|
||||
|
||||
Please ensure no screenshots have any PII (even your own email address) in them.
|
||||
|
||||
# Image copyrights and information
|
||||
|
||||
| File | URL | Date Accessed | Copyright |
|
||||
|------|-----|---------------|-----------|
|
||||
| EXAMPLE: [capecanaveral.jpg](LaunchProject\images\capecanaveral.jpg) | [Wikipedia](https://commons.wikimedia.org/wiki/File:Space_Launch_Complex_40_at_Cape_Canaveral_(aerial).jpg#mw-jump-to-license) | July 21, 2020 | This file is made available under the Creative Commons CC0 1.0 Universal Public Domain Dedication. The person who associated a work with this deed has dedicated the work to the public domain by waiving all of their rights to the work worldwide under copyright law, including all related and neighboring rights, to the extent allowed by law. You can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission. |
|
||||
|
|
@ -0,0 +1,88 @@
|
|||
# Title
|
||||
|
||||
*Add the working title [(Title guidance)](https://review.docs.microsoft.com/en-us/learn-docs/docs/id-guidance-title)*
|
||||
|
||||
## Role(s)
|
||||
|
||||
- *Add the role(s)* [Role guidance](https://review.docs.microsoft.com/en-us/new-hope/information-architecture/metadata/taxonomies?branch=master#role)
|
||||
- *This will probably include "student"*
|
||||
|
||||
## Level
|
||||
|
||||
- *Add the level* [Level guidance](https://review.docs.microsoft.com/en-us/new-hope/information-architecture/metadata/taxonomies?branch=master#level)
|
||||
- *This will probably be "beginner"*
|
||||
|
||||
## Product(s)
|
||||
|
||||
- *Add the product(s)*
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- *List the prerequisites [(Prerequisite guidance)](https://review.docs.microsoft.com/en-us/learn-docs/docs/id-guidance-prerequisites)*
|
||||
|
||||
## Summary
|
||||
|
||||
*Add the summary [(Summary guidance)](https://review.docs.microsoft.com/en-us/learn-docs/docs/id-guidance-introductory-summaries)*
|
||||
|
||||
## Learning objectives
|
||||
|
||||
1. *Add numbered Learning Objectives [(Learning objective guidance)](https://review.docs.microsoft.com/en-us/learn-docs/docs/id-guidance-learning-objectives)*
|
||||
|
||||
## Chunk your content into subtasks
|
||||
|
||||
Identify the subtasks of *module title*
|
||||
|
||||
| Subtask | What part of the introduction scenario does this subtask satisfy? | How will you assess it: **Exercise or Knowledge check**? | Which learning objective(s) does this help meet? | Does the subtask have enough learning content to justify an entire unit? If not, which other subtask will you combine it with? |
|
||||
| ---- | ---- | ---- | ---- | ---- |
|
||||
| TODO | TODO | TODO | TODO | TODO |
|
||||
| TODO | TODO | TODO | TODO | TODO |
|
||||
| TODO | TODO | TODO | TODO | TODO |
|
||||
|
||||
## Outline the units
|
||||
|
||||
*Add more units as needed for your content*
|
||||
|
||||
1. **Introduction**
|
||||
|
||||
Provide a scenario of a real-world job-task that shows how the technology is used in practice:
|
||||
|
||||
*Add your scenario [(Scenario guidance)](https://review.docs.microsoft.com/en-us/learn-docs/docs/id-guidance-scenarios)*
|
||||
|
||||
1. **Learning-content unit title**
|
||||
|
||||
List the content that will enable the learner to *subtask*:
|
||||
|
||||
- Enabling objective
|
||||
- Information needed to accomplish the enabling objective
|
||||
- Information needed to accomplish the enabling objective
|
||||
- Enabling objective
|
||||
- Information needed to accomplish the enabling objective
|
||||
- Information needed to accomplish the enabling objective
|
||||
- Enabling objective
|
||||
- Information needed to accomplish the enabling objective
|
||||
- Information needed to accomplish the enabling objective
|
||||
|
||||
**Knowledge check**
|
||||
|
||||
What types of questions will test *learning objective*? *[(Knowledge check guidance)](https://review.docs.microsoft.com/en-us/learn-docs/docs/id-guidance-knowledge-check)*
|
||||
|
||||
- Question type
|
||||
- Question type
|
||||
|
||||
1. **Exercise - exercise unit title**
|
||||
|
||||
List the steps which apply the learning content from previous unit:
|
||||
|
||||
1. Step
|
||||
1. Step
|
||||
1. Step
|
||||
|
||||
1. **Summary**
|
||||
|
||||
How did you solve the problem in the initial scenario with the knowledge learned in the module?
|
||||
|
||||
*Add your summary [(Summary guidance)](https://review.docs.microsoft.com/en-us/learn-docs/docs/id-guidance-module-summary-unit)*
|
||||
|
||||
## Notes
|
||||
|
||||
Note any additional information that may be beneficial to this content such as links, reference material, etc.
|
||||
|
|
@ -0,0 +1,20 @@
|
|||
# Propose new content for Microsoft Learn
|
||||
|
||||
Please fill out each section below and then copy/paste this doc into an email to Shana!
|
||||
|
||||
## Tell me about your content
|
||||
|
||||
Title:
|
||||
|
||||
Number of modules/learning paths you expect:
|
||||
|
||||
Your elevator pitch for the content:
|
||||
|
||||
Are there any related projects or content that's relevant?:
|
||||
|
||||
## When are we trying to launch this stuff?
|
||||
|
||||
Desired launch date:
|
||||
|
||||
Is this content connected to any other events/launch dates/deadlines?
|
||||
|
||||
Загрузка…
Ссылка в новой задаче