├── CODE_OF_CONDUCT.md ├── LICENSE ├── README.md ├── SECURITY.md ├── SUPPORT.md ├── logo.png ├── presentation.pptx ├── short-workshop ├── README.md ├── solution │ └── README.md └── workshop-designer.md ├── video-guidance.md └── workshop ├── README.md ├── images └── placeholder.png ├── slides.pptx ├── solution └── README.md └── workshop-designer.md /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Microsoft Open Source Code of Conduct 2 | 3 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 4 | 5 | Resources: 6 | 7 | - [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) 8 | - [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) 9 | - Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns 10 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) Microsoft Corporation. 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## Workshop Template 2 | 3 | Welcome to the Next Generation Team's design template for [building workshops](presentation.pptx), a system designed to help Microsoft Student Ambassadors and their partners to create and deliver excellent technical workshops. 4 | 5 | ## Types of Workshops 6 | 7 | In this template you will find two types of workshops that you can build: 8 | 9 | * **[Workshops](./workshop/README.md)** - a workshop that is designed to be completed within 30-90 minutes with content derived from [Microsoft Learn](https://learn.microsoft.com). 10 | * **[Short Workshops](./short-workshop/README.md)** - a workshop that is designed to be completed within 15-30 minutes with content derived from [Microsoft Learn](https://learn.microsoft.com). 11 | 12 | ## Style Guide 13 | 14 | To present a unified voice, please use [this style guide](https://github.com/jlooper/curriculum-template/wiki/Voice) to shape your writing. 15 | 16 | ## Building a Workshop 17 | 18 | - [ ] Decide what kind of workshop you want to design and sync with project lead to work out details. 19 | - [ ] Discuss your plan with your lead and add it to our DevOps board. 20 | - [ ] Design your workshop following these steps. 21 | - [ ] Fork this template repo to your local machine. 22 | - [ ] In the folder of your chosen type of workshop, fill out the [workshop-designer](./workshop/workshop-designer.md) document to design the experience. 23 | - [ ] Build slides for the workshop using the appropriate template, depending on which type of workshop you are building. 24 | - For Workshops, use our Particle tool to generate slides. Contact Chris Noring for help. 25 | - For Short-form workshops, slides are optional. 26 | - [ ] Write instructions for your workshop based on the README.md file in your folder's template. Your README.md work is minimal, and mostly links back to the source Learn module. Make sure to include a Call to Action with an instrumented link leading back to Docs and/or Learn to learn more. 27 | - [ ] If your workshop needs to diverge significantly from the Learn module, write out the steps as milestones, adding images and screenshots as needed. 28 | - [ ] Give your folder a descriptive name and PR the folder to the Next Generation Team's workshop library using [the library's PR template](https://github.com/microsoft/workshop-library) 29 | - [ ] Trainers: Contact Chris Noring to present your workshop to Microsoft Student Ambassadors to generate a Train the Trainer video for inclusion in the library. 30 | - [ ] Ambassadors: present workshops to your communities sourced from [the workshop library](https://github.com/microsoft/workshop-library). You can edit and use a [copy of this poster](https://www.canva.com/design/DAEuDXXR9us/share/preview?token=Je0_213uqxmYaXnNYz1v-Q&role=EDITOR&utm_content=DAEuDXXR9us&utm_campaign=designshare&utm_medium=link&utm_source=sharebutton) to publicize it. 31 | 32 | ## Slides about this project 33 | 34 | - [Explanatory slide deck](https://github.com/microsoft/workshop-template/blob/main/presentation.pptx?raw=true) 35 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Security 4 | 5 | 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/). 6 | 7 | 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. 8 | 9 | ## Reporting Security Issues 10 | 11 | **Please do not report security vulnerabilities through public GitHub issues.** 12 | 13 | Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report). 14 | 15 | 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). 16 | 17 | 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). 18 | 19 | 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: 20 | 21 | * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) 22 | * Full paths of source file(s) related to the manifestation of the issue 23 | * The location of the affected source code (tag/branch/commit or direct URL) 24 | * Any special configuration required to reproduce the issue 25 | * Step-by-step instructions to reproduce the issue 26 | * Proof-of-concept or exploit code (if possible) 27 | * Impact of the issue, including how an attacker might exploit the issue 28 | 29 | This information will help us triage your report more quickly. 30 | 31 | 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. 32 | 33 | ## Preferred Languages 34 | 35 | We prefer all communications to be in English. 36 | 37 | ## Policy 38 | 39 | Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd). 40 | 41 | -------------------------------------------------------------------------------- /SUPPORT.md: -------------------------------------------------------------------------------- 1 | # Support 2 | 3 | ## How to file issues and get help 4 | 5 | This project uses GitHub Issues to track bugs and feature requests. Please search the existing 6 | issues before filing new issues to avoid duplicates. For new issues, file your bug or 7 | feature request as a new Issue. 8 | 9 | For help and questions about using this project, please contact Jen Looper via Teams or tag me in the issues. 10 | 11 | ## Microsoft Support Policy 12 | 13 | Support for this Workshop Template is limited to the resources listed above. 14 | -------------------------------------------------------------------------------- /logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/workshop-template/b7780881a307278ae31252f3ee2d13d6925ab93d/logo.png -------------------------------------------------------------------------------- /presentation.pptx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/workshop-template/b7780881a307278ae31252f3ee2d13d6925ab93d/presentation.pptx -------------------------------------------------------------------------------- /short-workshop/README.md: -------------------------------------------------------------------------------- 1 | # Short Workshop Title 2 | 3 | ## Module Source Link 4 | 5 | Link the source Learn module here 6 | 7 | ## Goals 8 | 9 | In this workshop, we will discuss *insert your topic*. 10 | 11 | | **Goal** | *describe the goal of the workshop* | 12 | | ----------------------------- | --------------------------------------------------------------------- | 13 | | **What will you learn** | *describe your learning goals* | 14 | | **What you'll need** | *link all the necessary tooling, subscriptions, and downloads needed* | 15 | | **Duration** | *specify the duration* | 16 | | **Microsoft Cloud Topics taught** | *M365, Azure, GitHub, other?* | 17 | | **Just want to try the app or see the solution?** | *an optional link to the completed project sample app or solution folder* | 18 | 19 | ## Video 20 | 21 | Train the Trainer video embed 22 | 23 | ## Pre-Learning 24 | 25 | *add a link to Microsoft Learn for students to pre-learn the topic, if possible* 26 | 27 | ## Prerequisites 28 | 29 | *any installations that will be helpful, any hardware or software needed* 30 | 31 | ## What students will learn 32 | 33 | *describe the milestones students will accomplish in the workshop* - These are sourced from the Learn headings 34 | 35 | *optional: add a screenshot of the completed project* 36 | 37 | ![image of completed project](images/placeholder.png) 38 | 39 | ## Milestone 1 40 | 41 | text 42 | 43 | link 44 | 45 | ## Milestone 2 46 | 47 | text 48 | 49 | link 50 | 51 | ## Milestone 3 52 | 53 | text 54 | 55 | link 56 | 57 | ## Quiz or Code Challenge 58 | 59 | Link to quiz or challenge on Learn 60 | 61 | ## Next steps 62 | 63 | *links to Microsoft Learn to further learning progress, and/or a path to certifications* 64 | 65 | ## Practice 66 | 67 | *suggest, or add as an addendum, a way to extend students knowledge of the topic by creating a new app or demo that builds on the original workshop materials.* 68 | 69 | ## Feedback 70 | 71 | Be sure to give [feedback about this workshop](https://forms.office.com/r/MdhJWMZthR)! 72 | 73 | [Code of Conduct](../CODE_OF_CONDUCT.md) 74 | 75 | -------------------------------------------------------------------------------- /short-workshop/solution/README.md: -------------------------------------------------------------------------------- 1 | This optional folder contains solution files as a baseline for students to check their work. -------------------------------------------------------------------------------- /short-workshop/workshop-designer.md: -------------------------------------------------------------------------------- 1 | 2 | # UBD: Understanding By Design 3 | 4 | The UBD technique of curriculum design was created by Jay McTighe and Grant Wiggins and outlined in their book, "[Understanding By Design](https://www.amazon.com/Understanding-Design-second-Grant-Wiggins/dp/B006NPF8D0/ref=sr_1_15?crid=26FTBZ6E9Q53K&keywords=understanding+by+design&qid=1636052567&sprefix=understanding+by+design%2Caps%2C94&sr=8-15)". UBD is a process of "backwards design" where the curriculum designer works through three stages, starting with the desired goals of the learning experience and moving backwards through assessments and then to the lesson design. It bears some similarities to TDD (test-driven development) processes in Engineering, where tests are to be written before the code. Use this template to outline your workshop's desired outcomes. 5 | 6 | ## Workshop Title 7 | 8 | ## Workshop Source 9 | 10 | List the workshop source from Microsoft Learn (usually a module) 11 | 12 | ## Stage 1: Desired Results 13 | 14 | > List your established goals of the workshop experience here. These are the takeaways that you want students to have after completing the workshop. 15 | 16 | 1. Students will be skilled at: 17 | 18 | 1. Students will be able to independently use their learning to: 19 | 20 | ## Stage 2: Evidence 21 | 22 | > List any evaluative criteria and Assessment Evidence. Students will demonstrate their understanding of the concepts by doing the following: 23 | 24 | 1. Performance Tasks (these are tasks that a student can complete to demonstrate comprehension, such as a quiz or code challenge) 25 | 26 | ## Stage 3: Learning Plan 27 | 28 | > Now you are ready to build out your lesson plan. Summarize the key learning events here by creating an outline of the milestones that you can lay out to structure the course. 29 | 30 | 1. List the key learning events in the workshop - for a short workshop, we recommend 3 milestones 31 | 32 | -------------------------------------------------------------------------------- /video-guidance.md: -------------------------------------------------------------------------------- 1 | 2 | ### Video Best Practice 3 | 4 | Authors: Chloe Condon and April Speight 5 | 6 | #### Set the Scene 7 | Consider a neutral background for your streams. Remember, you want the viewer to focus on you and a noisy or distracting background can detract from your presentation! Here are some things to consider while setting the scene for your recording: 8 | 9 | What’s in the background? Ideally, use a solid neutral background, or set up the area behind you to look clean and professional. Think of what’s behind you as a set/stage. Be aware that anything in your background can be zoomed in on & enhanced! Try to avoid highlighting any branded items behind you (other than Microsoft), and be wary of accidentally sharing any product announcements, whiteboards of internal info, other important papers, etc. that may be visible in the background. 10 | 11 | Example: If you’re presenting in front of a book shelf, note the books, art, and other items behind you. Think of your background like a movie/television set, and make sure what is visible is appropriate for the content/aesthetic/style of the video you’re recording! 12 | 13 | #### Sound Check 14 | Your sound quality makes a huge difference in your final recording! Take special care to make sure you sound clear and professional in your video. 15 | 16 | Can you hear me now? Make sure to test your sound before recording! Ideally, you’ll want to use a high quality headset, microphone, or other professional equipment to record your video. Always do a sound check before recording- it’s better to test this before you record to make sure you don’t have to re-record again with better audio. You’ll want to test audio quality for echos, extra background noises, microphone placement, etc. 17 | 18 | Tip 💡: Avoid using wired cellphone headphones with the mic on the cord- the microphone will move/rub against clothing as you move, and cause sound issues that are difficult to fix in post. 19 | 20 | #### Costumes 21 | Think of your outfit for videos like a costume- does what you're wearing match the tone of the video you're recording? Remember- you're representing Microsoft! Take time to choose clothing that will showcase you and the company in the best light. 22 | 23 | Always consider what you’re wearing when filming, just as you would with a live talk on stage! Think of your outfit like a costume. You should avoid any brands/logos (other than Microsoft) when possible, avoid bold/distracting/intricate patterns, and try to wear a contrasting color to your background (example: a red shirt on a red background may create a floating head effect). 24 | 25 | Tip 💡: Using a green screen? Make sure to avoid any green clothing! 26 | 27 | #### Lights 28 | Make sure you have proper lighting for your video (we literally want to see you and showcase you in your best light)! Recording a video at night vs. day time can make a huge difference in how you look on camera, and will require some extra time, tools, and steps to make sure you're seen on screen. Remember- there's a reason why they award people Oscars & Tonys for lighting design- it's truly an art! 29 | 30 | Consider using external lighting tools, and make sure you're lighting your face/from behind your camera/computer/recording device! Even many cheap light tools available online provide you with different modes/brightness settings, and options. You'll need to adjust this for each stream, as lighting always varies by time of day, room, etc! 31 | There are many different kinds of light! Things like overhead fluorescents, natural lighting, and more can change the entire look of your presentation. Many lighting tools provide warm vs. bright light, and allow you to adjust brightness. 32 | Ask your manager about what tools and resources are available to expense! 33 | 34 | #### Final Touches 35 | Once you’ve recorded your video, consider adding some music, transitions, captions, and other additional nice touches! iMovie, Camtasia, or other tools can assist with this. 36 | 37 | Tip 💡: Music must be used legally! Speak with your manager/team about using tools for music licensing like Epidemic Sound. -------------------------------------------------------------------------------- /workshop/README.md: -------------------------------------------------------------------------------- 1 | # Full Workshop Title 2 | 3 | ## Module Source Link 4 | 5 | Link the source Learn module here 6 | 7 | ## Goals 8 | 9 | In this workshop, we will discuss *insert your topic*. 10 | 11 | | **Goal** | *describe the goal of the workshop* | 12 | | ----------------------------- | --------------------------------------------------------------------- | 13 | | **What will you learn** | *describe your learning goals* | 14 | | **What you'll need** | *link all the necessary tooling, subscriptions, and downloads needed* | 15 | | **Duration** | *specify the duration* | 16 | | **Microsoft Cloud Topics taught** | *M365, Azure, GitHub, other?* | 17 | | **Just want to try the app or see the solution?** | *an optional link to the completed project sample app or solution folder* | 18 | | **Slides** | [Powerpoint](slides.pptx) 19 | 20 | ## Video 21 | 22 | Embed your Train the Trainer video here. Instructions on how to create a great video experience is [available on this page](../video-guidance.md). 23 | 24 | ## Pre-Learning 25 | 26 | *add a link to Microsoft Learn for students to pre-learn the topic, if possible* 27 | 28 | ## Prerequisites 29 | 30 | *any installations that will be helpful, any hardware or software needed* 31 | 32 | ## What students will learn 33 | 34 | *In this area, describe the scenario and intended solution, paraphrasing what is in the module or creating a brief description here* 35 | 36 | Example: Have you ever wanted to visit a museum virtually or explore its collections right from your home computer? In this workshop, use an API, or Application Programming Interface, to learn more about a museum collection. 37 | 38 | *add a screenshot of the completed project* 39 | 40 | ![image of completed project](images/placeholder.png) 41 | 42 | ## Milestone 1 (example) 43 | 44 | In this segment, you'll query an API at the Metropolitan Museum of Art 45 | 46 | [link to Learn module area](link) 47 | 48 | ## Milestone 2 49 | 50 | text 51 | 52 | link 53 | 54 | ## Milestone 3 55 | 56 | text 57 | 58 | link 59 | 60 | ## Milestone 4 61 | 62 | text 63 | 64 | link 65 | 66 | ## Milestone 5 67 | 68 | text 69 | 70 | link 71 | 72 | ## Quiz or Code Challenge 73 | 74 | Link to quiz or challenge on Learn 75 | 76 | ## Next steps 77 | 78 | *links to Microsoft Learn to further learning progress, and/or a path to certifications* 79 | 80 | ## Practice 81 | 82 | *suggest, or add as an addendum, a way to extend students knowledge of the topic by creating a new app or demo that builds on the original workshop materials.* 83 | 84 | ## Feedback 85 | 86 | Be sure to give [feedback about this workshop](https://forms.office.com/r/MdhJWMZthR)! 87 | 88 | [Code of Conduct](../CODE_OF_CONDUCT.md) 89 | 90 | -------------------------------------------------------------------------------- /workshop/images/placeholder.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/workshop-template/b7780881a307278ae31252f3ee2d13d6925ab93d/workshop/images/placeholder.png -------------------------------------------------------------------------------- /workshop/slides.pptx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/workshop-template/b7780881a307278ae31252f3ee2d13d6925ab93d/workshop/slides.pptx -------------------------------------------------------------------------------- /workshop/solution/README.md: -------------------------------------------------------------------------------- 1 | This optional folder contains solution files as a baseline for students to check their work. -------------------------------------------------------------------------------- /workshop/workshop-designer.md: -------------------------------------------------------------------------------- 1 | 2 | # UBD: Understanding By Design 3 | 4 | The UBD technique of curriculum design was created by Jay McTighe and Grant Wiggins and outlined in their book, "[Understanding By Design](https://www.amazon.com/Understanding-Design-second-Grant-Wiggins/dp/B006NPF8D0/ref=sr_1_15?crid=26FTBZ6E9Q53K&keywords=understanding+by+design&qid=1636052567&sprefix=understanding+by+design%2Caps%2C94&sr=8-15)". UBD is a process of "backwards design" where the curriculum designer works through three stages, starting with the desired goals of the learning experience and moving backwards through assessments and then to the lesson design. It bears some similarities to TDD (test-driven development) processes in Engineering, where tests are to be written before the code. Use this template to outline your workshop's desired outcomes. 5 | 6 | ## Workshop Title 7 | 8 | ## Workshop Source 9 | 10 | List the workshop source from Microsoft Learn (usually a module) 11 | 12 | ## Stage 1: Desired Results 13 | 14 | > List your established goals of the workshop experience here. These are the takeaways that you want students to have after completing the workshop. 15 | 16 | 1. Students will be skilled at: 17 | 18 | 1. Students will be able to independently use their learning to: 19 | 20 | ## Stage 2: Evidence 21 | 22 | > List any evaluative criteria and Assessment Evidence. Students will demonstrate their understanding of the concepts by doing the following: 23 | 24 | 1. Performance Tasks (these are tasks that a student can complete to demonstrate comprehension, such as a quiz or code challenge) 25 | 26 | ## Stage 3: Learning Plan 27 | 28 | > Now you are ready to build out your lesson plan. Summarize the key learning events here by creating an outline of the milestones that you can lay out to structure the course. 29 | 30 | 1. List the key learning events in the workshop - for a one-hour workshop, we recommend 5 milestones 31 | 32 | --------------------------------------------------------------------------------