Great suggestion! It never hurts to revisit how things are organized, and update them based on usage. My one suggestion based on your suggested structure would be as follows:
- General MODX Chat
- General Web Dev Chat
- Web Dev Lounge / Off Topic
- Other
- - Design & Templates
- - Tips & Tricks
- - Misc...
In short if a topic isn't directly related to a product/service it shouldn't fall under the Products grouping. My two cents on version sub-boards would be reduce and/or eliminate them. Ideally, put a
required (Currently Installed?) version field for posts and include that with the subject (like Question/Answered). I would think this might help search results more than grouping post to version sub-boards.
That approach also eliminates version confusion when making a post, for example if they just upgraded or want to upgrade. It would also be AWESOME to adopt an EOL/LTS (End of Life/Long Term Support) strategy, which is mirrored in the forums. It's unrealistic to support all versions of all products indefinitely, people need to upgrade at some point in time.
A few EOL/LTS examples:
cPanel - 12 months from initial release -
https://documentation.cpanel.net/display/ALD/cPanel%2520&%2520WHM%2520Long-Term%2520Support
modmore - Varies -
https://www.modmore.com/about/versions/
PHP - Varies -
http://php.net/eol.php
I'm personally amazed MODX supports PHP 5.1.x still (
http://rtfm.modx.com/revolution/2.x/getting-started/server-requirements), I would think they could save countless hours of testing by limiting support to say PHP 5.3.20+, but that's a bone for another post
Enough rambling, thanks again for the suggestions! I look forward to seeing them implemented.