Do not make the same mistake as Jriver. They have a great product and a great support forum , but no manual.
The result is that the learning curve with each release becomes steeper for new users. They have to find out which FAQ, post etc. applies to which version of the soft.
Newbie questions are brushed off by the old gang and that is commercially not smart.
When you look at support sites from IT-companies as Oracle, MS, Cisco etc they always make a clear distinction between community support which is less formal and the very formal sections with manuals and questions and answers.
Both manuals and questions and answers are always tied to release numbers. If a company has that discipline from start, it is fairly easy to review questions and answers for their validity with each release.
The Knowledge Base is going to be the formal online manual and it will be updated as new versions are released. The work to fill it out with a lot of the material in the existing FAQs or on the forum is proceeding apace.
Ideas or comments about how the KB is looking, changes that should be made, why Roon should be doing something else etc., are all welcome.
Getting every last aspect of the app documented is a big task, and keeping it all up to date is work too, but we’re working on it!
We are putting the information in our knowledge base. This is where structured information about Roon will live. We scrubbed virtually every page for out-of-date information prior to the release of 1.2. It is a lot of work, but we agree, this is important.
The lowest-friction time to write documentation for something is right when that thing is being worked on. As we give love to the various functional areas of Roon over the coming months, expect their documentation to get stronger along with them.
I couldn’t agree with you more. Little pop-ups and FAQs do not come close to replacing a proper user manual. Contrary to popular belief not everything in this software is intuitive. Roon is not the only audio program guilty of this. I use JRiver as well and their documentation is just as shoddy. I find this to be really lazy. We’re paying for this software and paying customers deserve a proper user manual.