Tweet
* Please note, this is a suggestion for the vBulletin corporate website, not the actual software.
There are a respectable number of people who complain about how the official vBulletin manual is lacking. Personally, I think it's OK, but will fully admit it has a lot more potential and even completely misses some technical items. It's also not the most user-friendly thing around in comparison to modern Documentation resources.
With that said, I'm proposing that vBulletin(.com) integrate MediaWiki or similar onto this website, in the same regard to how Jira works. This would allow existing licensed customers to share and document their knowledge of the vBulletin software, provide a more "user-friendly" documentation resource and enable a better and more accurate searching for specific functions and/or terms. Everybody has used Wikipedia at least once, this would create a familiar experience.
It could enable modification and style creators to create in-depth reviews on how the system works and what changes what and how x applies to y, etc - something that has been requested several times. It would be similar to vB.org's article section, but more efficient and practical.
This would not be a replacement for the classic Online Documentation, no, instead it would compliment it as a community-driven resource while the Online Documentation remains the "official" documentation.
I've been following Simple Machines for a while (since 2007 actually) and they have done this exact thing. They still have their official documentation, but also have community-driven documentation through the wiki. It works quite well and is fully integrated into their user database. Not to mention the potential to have incredibly rich documentation without having to pay a dime to the documenters.
Of course this has the potential for inaccurate or misleading information, however labeling it as a community driven resource and limiting editing to Licensed members and support staff, that potential is greatly reduced.
I know this won't happen, but I just wanted to throw my 2 cents in. (Maybe I'll be wrong)
There are a respectable number of people who complain about how the official vBulletin manual is lacking. Personally, I think it's OK, but will fully admit it has a lot more potential and even completely misses some technical items. It's also not the most user-friendly thing around in comparison to modern Documentation resources.
With that said, I'm proposing that vBulletin(.com) integrate MediaWiki or similar onto this website, in the same regard to how Jira works. This would allow existing licensed customers to share and document their knowledge of the vBulletin software, provide a more "user-friendly" documentation resource and enable a better and more accurate searching for specific functions and/or terms. Everybody has used Wikipedia at least once, this would create a familiar experience.
It could enable modification and style creators to create in-depth reviews on how the system works and what changes what and how x applies to y, etc - something that has been requested several times. It would be similar to vB.org's article section, but more efficient and practical.
This would not be a replacement for the classic Online Documentation, no, instead it would compliment it as a community-driven resource while the Online Documentation remains the "official" documentation.
I've been following Simple Machines for a while (since 2007 actually) and they have done this exact thing. They still have their official documentation, but also have community-driven documentation through the wiki. It works quite well and is fully integrated into their user database. Not to mention the potential to have incredibly rich documentation without having to pay a dime to the documenters.
Of course this has the potential for inaccurate or misleading information, however labeling it as a community driven resource and limiting editing to Licensed members and support staff, that potential is greatly reduced.
I know this won't happen, but I just wanted to throw my 2 cents in. (Maybe I'll be wrong)
Comment