Microsoft SharePoint Framework Training Module - Getting Started with SharePoint Framework Extensions
This module will introduce you to extending the SharePoint user interface with extensions.
In this lab you work with the SharePoint Framework to extend the user interface with extensions. This includes: application customers, field customizers and command sets.
This module has been recorded and is available in the SharePoint Development YouTube channel: SharePoint Framework Training - Developing with the SharePoint Framework: Getting started with SharePoint Framework Extensions
| Roles | Author(s) |
|---|---|
| Lab Manuals / Slides | Andrew Connell (Microsoft MVP, Voitanos) @andrewconnell |
| QA | Rob Windsor (Microsoft MVP, PAIT Group) @rob-windsor |
| Sponsor / Support | Vesa Juvonen (Microsoft) @VesaJuvonen |
| Version | Date | Comments |
|---|---|---|
| 1.5 | September 2, 2019 | 2020Q1 content refresh |
| 1.4 | June 10, 2019 | FY2019Q4 content refresh |
| 1.3 | March 6, 2019 | FY2019Q3 Content refresh |
| 1.2 | January 17, 2019 | Slide updates, added screencast link to readme |
| 1.1 | December 12, 2018 | Rewritten to use latest guidance |
| 1.0 | ~February 2017 | Initial release |
THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.
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.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., label, 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. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.