This article is contributed. See the original author and article here.
The Microsoft 365 Community Docs is a valuable resource for “makers”: site owners, citizen developers, power users, and more. Really, anyone who would like to understand the platform better to support their organization. Articles provide many different types of content, from simple definitions of terms, to explanation of common concepts using everyday examples, to scenario-based decision-making tools, to in-depth discussion of specific apps and services.
Community-generated content has tremendous value because it is written by people in the trenches – the people who work with the platform every day. Sometimes people in the community devise solutions Microsoft couldn’t have imagined or ways to combine different services uniquely to solve business problems. As a community, we can talk about what works well and what doesn’t.
If you are interested in becoming a contributor, you have several options:
- Make an article suggestion by adding an Issue in Github
- Suggest those fixes or changes in an article issue
- Make edits or improvements to existing articles yourself based on your experience
- Review the open issues, most of which are articles suggestions. See if there are any suggestions you would like to write about. If you see something you would like to tackle, add a comment requesting to be assigned to the issue.
- Write a new article describing aspects of the platform you are passionate about. If you’re not sure if your idea is “fully baked”, add an article suggestion with a request for it to be assigned to you and we can help you refine your idea.
- As an open source effort, we can partner you with other authors and contributors if you feel you could use some support. Simply ask a question in the repo and we’ll get back to you as quickly as we can.
We’ve got some interesting content ideas in the pipeline. One of them will be based on the excellent work Sadie Van Buren did back in the 2010-2012 timeframe around the SharePoint Maturity Model. (Old Web site at the Wayback Machine.) Sadie’s framework was invaluable for SharePoint shops to gauge and evaluate their level of maturity in using the platform. We plan to expand and update the model to cover more of Microsoft 365 over the coming months. Sound interesting? Think you might like to be involved? Drop a comment on the issue Update and Modernize Sadie Van Buren’s SharePoint Maturity Model.The repo continues to expand and evolve. Since the last post, we have new articles in the repo as well as new contributors
These articles have been added since we last posted.
- Living Large with Large Lists and Large Libraries
- SharePoint Naming Guidelines
- Should I store my files in Microsoft Teams or in SharePoint? An understanding of behind the scenes
- Why SharePoint Training is Important
New articles make the repo more useful, but updates to existing articles are equally important. These updates have expanded existing articles or improved them by adding clarifications or corrections.
- Importing data into SharePoint
- Planning Permissions with Group-based SharePoint Sites… when you’re used to Regular SharePoint Permissions
- Understanding Power Platform Licensing
- Team Site vs. Communication Site: Which one should I choose?
- Versioning in SharePoint
We thank our contributors: without the community, this effort would not exist!
- Beth Hall
- Emily Mancini
- Eric Skaggs
- Hugo Bernier
- Jim Love
- Jimmy Hang
- Joanne Klein
- Julie Turner
- Marc D. Anderson
- Norm Young
- Patrick Doran
- Paul Bullock
- Pedro Marques Santos
- Prasad Kasireddy
- Ralph Rivas
- Susan Hanley
- Thomas Daly
- Veronique Lengelle
As always, thanks to the great Microsoft team helping with this effort. As they say, it takes a village:
- Joanne Hendrickson
- Pam Green
- Tom Resing
- Thomas Raya
- David Strome
- Vesa Juvonen
Author of this article – Marc D Anderson (Sympraxis Consulting). Sharing is caring!
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.