Structure and high level working model

This is high level plan on how to start contribution and how we will release new monthly versions of the package.

• Use ‘Dev’ branch for your development and contributions
• We will do monthly releases of the ‘Main’ branch with more detailed testing
• We will do monthly release communications to this wiki, including credits for the active contributed persons in GitHub.
• We will start monthly web casts on showing latest development and the next steps in the roadmap. More detailed contact information for this in our Yammer group when schedule is locked. We are expecting to have the first session on mid-September.
• We are working on converting existing word documents to markdown format and to have additional content on the demonstrated patterns and practices in MSDN, dev.office.com and in the PnP wiki
• We are working gradually to get the v1.0 of the core component out. Right now the component is in 0.5 version level due constantly evolving code. All changes are introduced in way that we should have full backward compatibility for previously used methods. Old methods are marked to be deprecated.
• We will continue adding relevant simple samples on the specific patterns under Samples section
• We will continue adding new scenario samples to the structure. Scenarios are targeted on showing how the core component works and how certain specific capability can be achieved using core component implementation
• We will continue expanding the solution category with more comprehensive solutions, which can be used as a reference for your own development.

If you have good suggestions or feedback with the above high level pattern, please provide us feedback and input. Program exists for the benefit of the community, so we are more than willing to hear your input on things.

Folder structure for GitHub

Here’s a short description of the different folders in the GitHub project. This is how we currently group the code and other elements in the overall package.

• Components - Reusable components targeted to be used as such in projects
• Samples - Individual samples demonstrating a capability or functionality. Intentionally kept pretty simple to concentrate on covered topic
• Solutions - Complex reusable solution. Demonstrating combining multiple different patterns to provide needed end user capability

Visual Studio solution structure

Each Visual Studio solution has linked resources in it, including documentation and possible reference to the Core component.