So, first post about how we can manage contributions to the documentation.
Our goal is to have, in the end, the following guides:
- Developer User Guide: About Servoy Developer, how to install, configure, debugging, using the Script and Form Editor, Team Support etc. So this Guide is NOt about how to build solutions with Servoy
- Programming Guide: The main guide for info on how Servoy works, the concepts, how to build solutions etc. etc.
- Programming Reference Guide: A real reference guide to quickly lookup how x or y works
- Deployment Guide: Everything about deployment
Besides these guides there can be specific guides for developers coming form platform x or y, so for example “Servoy for Filemaker Pro developers” or “Servoy for Visual FoxPro developers”.
Besides real guides, we can also have tutorials, which would be self-contained documents that go into depth on a specific topic that is not part of the “core” of what Servoy is. don’t have a specific example right now. Feel free to add.
For now I can post the structure I have in mind for the Developer User Guide and the Programming Guide. That way you guys can have a look if the structure makes sense, if stuff is missing etc.
The idea of Carlos about identifying forum topics that contain interesting content that ought to go into the docs also makes sense to me.
Please let me know your thoughts.
Paul