Forum Posts Feed
Managing Sharing of a Knowledge Database
< Next Topic | Back to topic list | Previous Topic >
Posted by Garland Coulson
Nov 1, 2013 at 10:10 PM
I am a time management speaker, trainer and consultant. I would like to be able to share resources with my customers/members. I have written several ebooks, but they are difficult to keep up to date and distribute. I was thinking it might be better to have an online resource/knowledge database they could access instead. This way, everyone could access it and I could update just one place.
I am trying to decide what system to create it in. I have access to web designers and could do it in something like Wordpress, but I was thinking there might be a better way.
I use and love Evernote and do share some notes with people that way, but there is no way to properly order the notes within a shared notebook and the membership controls are poor.
I was wondering if a Wiki might be the best possibility to let me share online but also to control access. I was seeking your ideas on either a Wiki or another system that would work for this.
I should mention that I do not use markdown, I prefer WSYWIG so availability of WSYWIG is important.
I was looking at https://www.dokuwiki.org/ and was wondering if it might do the trick. If anyone has used a Wiki for public/members access I would like to hear your experiences with the systems you have used and any challenges you had.
Posted by 22111
Nov 2, 2013 at 11:09 AM
Garland, I just checked the recent thread about viewers: You didn’t bother to share some knowledge you undoubtedly must have about that subject, so…
Posted by Dr Andus
Nov 2, 2013 at 01:30 PM
Garland Coulson wrote:
>I am trying to decide what system to create it in.
One question is whether you want to host the site yourself or not.
If yes, you could use an HTML editor, desktop wiki, or Wordpress.org.
If no, you could use a website builder service, wiki farm, or a blogging platform (Wordpress.com or similar).
Some website builder services:
https://iwantmyname.com/services/website-builder/
Some wiki farms (some of which have WYSIWYG):
http://en.wikipedia.org/wiki/Comparison_of_wiki_farms
>I should mention that I do not use markdown, I prefer WSYWIG so
>availability of WSYWIG is important.
>I was looking at https://www.dokuwiki.org/ and was wondering if it might
>do the trick.
DokuWiki does seem to require markup.
https://www.dokuwiki.org/wiki:syntax
Posted by Garland Coulson
Nov 2, 2013 at 05:11 PM
22111 wrote:
Garland, I just checked the recent thread about viewers: You didn’t
>bother to share some knowledge you undoubtedly must have about that
>subject, so…
>
Not sure what you mean by this 22111. What knowledge would I undoubtedly have that I am not sharing somewhere? What thread is it you think I am withholding knowledge on?
Posted by Garland Coulson
Nov 2, 2013 at 05:22 PM
Thanks Dr.Andus
Dr Andus wrote:
Garland Coulson wrote:
>>I am trying to decide what system to create it in.
>
>One question is whether you want to host the site yourself or not.
I have my own hosting so hosting it myself is not a problem.
>If yes, you could use an HTML editor, desktop wiki, or Wordpress.org.
I do a lot of sites for clients in Wordpress and love it. It is a possible solution and I know of good membership plugins I could use to control access. But overall, it just doesn’t seem as intuitive as a wiki or Evernote notebook.
>Some wiki farms (some of which have WYSIWYG):
>http://en.wikipedia.org/wiki/Comparison_of_wiki_farms
Thanks, I will have a look at this.
>>I should mention that I do not use markdown, I prefer WSYWIG so
>>availability of WSYWIG is important.
>>I was looking at https://www.dokuwiki.org/ and was wondering if it
>might
>>do the trick.
>
>DokuWiki does seem to require markup.
>https://www.dokuwiki.org/wiki:syntax
DokuWiki does have a plugin extension that allows WSYWIG. I have asked my designer to install it on a test directory on my site so I can play with it to see what I think.
Thanks again for your help. This is a big decision for me as this is intended to hold a huge database of knowledge over time and it would be frustrating to build the knowledge base for a couple of years and then find I needed to change.
Garland