Where should we store documentation?

Right now the documentation is scattered about make.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//training. Some of it is in the regular navigational structure, but quite a lot of it is hidden within the P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. blog. Especially as the team is currently focused on streamlining processes and inventing new processes for things that need it, we need a centralized place to keep all of our documentation.

After looking through all of the other Make sites, it seems that the other teams nearly universally use the handbook  to store their documentation. Thus far, we’ve used the handbook to store lesson plans in progress only.
The questions we have for the team are:
  1. What are the pain points with the current structure of where data is located on make.wordpress.org/training?
  2. What needs do we have in terms of organizing documents and collateral for the training team?

Thus far we’ve identified some of the problems, but need to think through and determine if there are other issues that we haven’t considered yet. Finding a solution for this one will take some time and thought – please note any thoughts you have either on pain points (question 1) or team needs (question 2) in the comments below.

Note: This topic was initially discussed during our regular team meeting on September 29, 2015.