Proposal: Forum board for RTFM

There is a single thread here for forum enhancements, and it's quite old. I think we could use a board dedicated to documentation so that people can find information, so that people can make suggestions and post requests, and so that people can post errata and new content to be added by whomever has time and access.

I don't see any reason not to do this at all. Suggestions on title/description and location? There's still plenty of cleanup work to do in the forums in general.

Location:

- Documentation could be considered a "product".
- It's not just related to Revo/Evo/xPDO, etc, so it shouldn't go under one of those.
- I'm thinking a new board could be positioned as the last Product board below Evo Development.

OR

- Some people don't see docs as a product but as a feature of the products
- In this case I'm thinking the board can be placed in the General category, maybe right at the top, or beneath General Support.
- It could also fit within General Support, right above or below MODX 101.

In my mind, Documentation should figure prominently, not be hidden. That's the first place people should go for information - where we teach people how to fish instead of tossing fish. The better the docs the fewer the forum postings, which is good for everyone here. That's the problem with Drupal and Wordpress - the docs are poor and the (awful) forums have become the primary info sources where people usually ask questions without even searching because they know they're not going to find what they need in the muck of a million other forum postings. Discussions about doc improvement should be easily accessible so that the docs get attention before the forum becomes like those others.

Description: "Documentation" : "Topics related to all documentation available for MODX"
I don't believe it should follow the fond moniker "RTFM", as the content should be about all docs including those provided on community sites. RTFM is just one resource.

I think that's a start - if it doesn't work it can't hurt to change it later...

Thanks for your consideration.

By the same token you could treat the Bug Tracker & Feature Requests in a similar fashion, don't you think? Granted, unless the conclusions of the discussions don't ultimately wind up in the right spot (e.g., the Bug Tracker) they might as well not exist because they'll slip beneath the surface of the deluge of discussions that occur here.

Well, documentation is something that is produced just like software. It's researched, designed, coded, debugged, put into production, and then it gets updates. It's also something we talk about changing. Those are not features attributed to Bug Tracker & Feature Requests.

In a general sense and here too, I hope people to go to Bug Tracker & Feature Requests only after they have been through the rest of the forum and the documentation. One could say it should be easy to find documentation and perhaps not so easy to jump into making a new request. I don't play games like that and don't want to make anything difficult, but SEO and web design do employ a significant amount of psychology, so it's not too out of place in a forum either. (Too deep)