Moon Wizard
October 10th, 2013, 09:32
OK, I have been wrestling with the best way to handle documentation for quite a while.
I've been thinking that a wiki which can be limited to a handful of people editing each section (manual/guide/etc.) is the best approach. I've been investigating quite a number of solutions, trying to consider authentication, multiple-user editing, protecting content, etc. So, I have also looked at a few CMS systems, and I'm at a bit of an impasse.
One of the biggest challenges is finding a solution is that I really wanted to avoid another login, so I've been trying to find something that works with vBulletin. However, all the "bridges" I have found for various wikis to vBulletin are out of date. And, there doesn't seem to be any options for the vBulletin system to act as an open authentication provider to another system (other than building and maintaining your own).
Also, most wikis do not have the ability to lock down a page or set of pages to a specific set of users. They have more of a blanket on/off editing, or you have to use plugins which are not maintained or only allow author locking.
My best solution so far is VaultWiki, which is a vBulletin add-on which mimics some behavior of a wiki. However, I'm finding it difficult to get it set up the way I want. Here is an example of what can be done with VaultWiki:
https://www.fantasygrounds.com/forums/showwiki.php?title=Books:Manual+Core
At this point, it's either charge ahead with VaultWiki, or change gears to implement a CMS with a completely different login system that I can assign to only those users who want to help document.
Thoughts?
JPG
I've been thinking that a wiki which can be limited to a handful of people editing each section (manual/guide/etc.) is the best approach. I've been investigating quite a number of solutions, trying to consider authentication, multiple-user editing, protecting content, etc. So, I have also looked at a few CMS systems, and I'm at a bit of an impasse.
One of the biggest challenges is finding a solution is that I really wanted to avoid another login, so I've been trying to find something that works with vBulletin. However, all the "bridges" I have found for various wikis to vBulletin are out of date. And, there doesn't seem to be any options for the vBulletin system to act as an open authentication provider to another system (other than building and maintaining your own).
Also, most wikis do not have the ability to lock down a page or set of pages to a specific set of users. They have more of a blanket on/off editing, or you have to use plugins which are not maintained or only allow author locking.
My best solution so far is VaultWiki, which is a vBulletin add-on which mimics some behavior of a wiki. However, I'm finding it difficult to get it set up the way I want. Here is an example of what can be done with VaultWiki:
https://www.fantasygrounds.com/forums/showwiki.php?title=Books:Manual+Core
At this point, it's either charge ahead with VaultWiki, or change gears to implement a CMS with a completely different login system that I can assign to only those users who want to help document.
Thoughts?
JPG