Agree a content structure

[johnpuddephatt]

Initially it makes sense to gather all available resources in one place. These resources collectively act as valuable source material for the docs. In order that the finished product meets the needs of Symphony users, however, we can't let ourselves be limited by what source material already exists – there may (/will) be gaps that need filling!

We should therefore agree a content structure that we can work towards.

Added benefits of this will be: 1) it makes it easier for others to contribute (as they can see what needs to be done), and 2) it will provide a useful way of tracking progress as pages/sections are completed and ticked off.

Usefully, some content structures have already been proposed, both in the Google Drive Factory notes, and here on Github.

At first glance these seem quite reasonable and don't conflict with one another too much. It might be useful to get a bit of wider input here to see if there are any glaring omissions.

[bernardodiasc]

Very good stuff!

The content structure I did so far is pretty much for prototyping Jekyll (learning now how to use the tool), feel free to reorganize the content at will. Also we can make use of placeholder markdown files using the desired content structure.

[johnpuddephatt]

Yes that makes perfect sense. It is also very useful to begin by collecting everything together in one place!