Support
This step talks about how to get help for the open source SharePoint modernization guidance and provide some ideas about potential next steps.
Getting help
For questions on this deck and on the used scripts the best place to get help is the issue list in the sp-dev-modernization GitHub repository: https://github.com/SharePoint/sp-dev-modernization/issues.
You’ve added a cool extension, fixed a type, fixed a bug…any contribution to the existing content that you can share back will help the SharePoint community:
- Sharing can be done by creating a Pull Request against the dev branch of the https://github.com/SharePoint/sp-dev-modernization repository.
- If you’re unfamiliar with Git you can also describe the change in the issue list.
What's next?
What else can you consider combining with the modernization:
- Make the Teams experience richer by populating the created Teams team with channels and messages. See /sharepoint/dev/solution-guidance/pnp-provisioning-tenant-templates on how to get started with PnP Tenant templates that provision Teams content.
- Create SharePoint Framework based customizations to replace existing, business critical, classic customizations. The customizations can also be hosted in Teams. See /sharepoint/dev/spfx/sharepoint-framework-overview to learn more.
意見反應
https://aka.ms/ContentUserFeedback。
即將登場:在 2024 年,我們將逐步淘汰 GitHub 問題作為內容的意見反應機制,並將它取代為新的意見反應系統。 如需詳細資訊,請參閱:提交並檢視相關的意見反應