Hi everyone, kudos to you seasoned forum members for all your effort trying to improve the FAQs and consolidating commonly asked forum topics
Personally I use the wiki a lot and although my own contributions have been minimal i would very much like to see it maintained and improved with up to date information in line with the vision Steven has.
Can we be clear on what the boundaries are with the Wiki?
I see the Wiki as like a user manual where a new user can read and learn from scratch how to use MusicBee, where-as what is being proposed in this new board is a collection of common problems users have and what the solution might be.
For new (and not so new) users, a wiki/user guide is a commonly understood format, and in my opinion should be the first port of call for 'how to' documentation. Psychoadept has done a great job documenting a complex piece of software and with a bit more support it could be really good.
As a comparison I like the depth of information and clear examples given on the Audacity wiki (
https://manual.audacityteam.org/) - although navigating it is a really poor user experience.
With reference to the MP3TAG FAQs I think it is only partially effective at what it aims to do. It resides in the 'How To' section and collects together answers to common tasks that users want to achieve. In this way i would say it is more similar to the MusicBee wiki than an FAQ resource. When i've used it in the past I found the format a bit unstructured and not that easy to find the answers i was searching for. I would rather search in a wiki or a more structured form of documentation.
As for the discussion about which parent topics to have in the new FAQs, and how many levels of hierarchy is acceptable my advice would be to take a bottom up 'card sorting' approach and start by identifying the topics where there are a lot of similar forum posts and make them all top level categories. As more topics are added you will be able to see when it makes sense to combine similar topics under a new parent. This is likely to result in an information architecture that is more commonly understood by most users rather than trying to impose a top down structure from the get go.