Contribute to the Microsoft 365 & Power Platform Community

You can contribute to SharePoint development through the Microsoft 365 & Power Platform Community, also known as PnP. Contributions include documentation, code, answers to questions, and demos.

Ways to contribute

• Fix an article or suggest missing guidance in SharePoint developer documentation.
• Share an SPFx web part sample or a Copilot UX component sample. Use the gallery's repository link to find submission instructions.
• Report or fix issues in projects in the SharePoint and PnP GitHub organizations. Use the repository catalog to find the current project rather than an archived predecessor.
• Join community calls, ask questions, or propose a demo.
• Participate in SharePoint Developer discussions on Microsoft Tech Community.
• Suggest product improvements in the SharePoint developer platform feedback portal.

Before submitting a contribution

1. Read the target repository's README, contribution instructions, license, and code of conduct, where provided. Requirements differ between projects.
2. Search existing issues and pull requests to avoid duplicate work. For a substantial change, discuss the proposal with the maintainers using the project's preferred channel.
3. Follow the repository's instructions for submitting an issue or pull request. Include the problem being solved, relevant versions, and validation results.
4. For samples, document prerequisites, setup steps, and dependencies. Don't include credentials, tenant data, or other sensitive information.

For documentation changes, follow the sp-dev-docs contribution guide and pull request guidance. Follow any contributor license agreement instructions presented by the repository.

FAQ

Why would I contribute?

Contributions help other developers solve problems and give you an opportunity to learn from project maintainers and other contributors.

Can I share a sample from my own repository?

Check the submission guidance for the sample gallery or repository you want to contribute to. Ask its maintainers if the guidance doesn't cover your scenario; there isn't a single submission process for every community project.

I've built a cool SharePoint development sample; can I contribute it?

Yes. Find the relevant sample repository, review its contribution requirements, and submit a pull request. Include instructions so reviewers can build and run the sample. Review timing depends on the project and maintainer availability.

We're working on cool guidance for SharePoint development; could we contribute that?

Yes. Propose an article or improvement in the documentation repository, or share a technical walkthrough through a community demo. Explain the audience, the problem, and how the guidance complements existing material.

I'd like to help, but I'm not sure where to find suitable tasks or what to do.

Start with a project you use:

• Reproduce a reported issue and provide missing details.
• Improve setup instructions or fix an unclear article.
• Test a sample and document its requirements.
• Look for contributor-friendly issues identified by that repository's maintainers.

For help choosing where to ask a question or report a defect, see Support and feedback.