these subjects are quite dynamic (storage providers based on standard protocols like S3 or SSH come and go).What I’ve thought about, but didn’t make it to the manual is: “FAQ’s”, “Troubleshooting”, “Specific operations / Hacks / Tips & Tricks”, “Howto’s” and “Using specific Storage providers”. This completes all subjects I want to cover in the manual (General information, Installation, Graphical Interface, Storage Providers, Commandline Interface, Disaster Recovery, Commandline Reference, Advanced Options Reference, selected whitepapers in Appendices). In the mean time, things may evolve, and thoughts may change on what’s the best approach for releasing it to the public. When I download a program I want to try, I first click on the Support/Documentation/Features link and not dive straight into a discussion board to find out how things work.īut nothing has been decided yet, first let’s try to complete the docs as soon as possible. I’m not feeling very comfortable by the idea to put as much as possible in the forum, as I still see the primary usecase for a forum is discussion, mainly “User X helps User Y” and discussions about how to improve the product. I have thought of several options how to share it, but still not sure what the best option is and what’s technically possible. It’s probably also a good idea to add a link to the pdf manual at the beginning of each post, mentioning that what follows is an excerpt of that manual. copy and paste each section (or sub-section) into a new topic here on the forum to make it searchable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |