Skip to content
This repository has been archived by the owner on Aug 28, 2024. It is now read-only.
VesaJuvonen edited this page Jun 13, 2016 · 15 revisions

Office 365 Developer Patterns and Practices

SharePoint Patterns and Practices Core Component Wiki

Welcome! If you are new to the library you might want to check out the getting started page to setup your environment for development. Perhaps you would like to contribute? Or looking for more information on our vision or roadmap? Maybe you are just looking for links to help you find things?

What's PnP JavaScript Core Library?

The new Patterns and Practices JavaScript Core Library was created to help developers by simplifying common operations within SharePoint. This is aligned with helping folks transitioning into client side development in support of the upcoming SharePoint Framework. Currently it contains a fluent API for working with the full SharePoint REST API as well as utility and helper functions. This takes the guess work out of creating REST requests, letting developers focus on the what and less on the how.

What's the PnP SIG?

The SharePoint Client Development Special Interest Group (SIG) was started under the larger PnP organization to provide folks with a desire to learn more about the upcoming SP Fx and client development a place to interact with their peers. This is the first of likely many SIGs within the PnP org and as such we will learn and evolve as we grow.

The SIG is tasked with developing this library contained in this repo, generating guidance on SharePoint client side development practices, and creating samples across the various development scenarios.

The Team

We hold the idea of Worldwide, One Team as being a central tenant to what we do. Everyone is welcome to join and participate - whether that is on the weekly calls, through the Yammer or Gitter conversations, or through contributing to the repository here. Bring your ideas and share your experience, we will all be better for it! We have three core team principles:

  • Elastic Team - We understand everyone has work, family, hobbies, and life. When you have time to contribute and participate - fantastic! When you are busy, no worries, this is completely understood and expected.
  • Community Driven - We are always open to and listen to all feedback. This doesn't mean your idea will necessarily jump to the top of the priorities, but everything will be considered and given careful thought.
  • Enabling Developers - This has two facets: the first being enabling those folks that want to contribute to have a great experience and get to do some fun and interesting work, while learning new skills; and the second is to enable consumers of our work to have an equally great experience using our library, samples, and guidance.
Clone this wiki locally