A "KNOWLEDGE BASE"?

[gbWilly]

My thoughts are that the initial post should have a template like ...(I'll get back to this later, people talking...)
and subsequent posts would be a sort of discussion session. Yeh, just like a wiki of note.

Seems like a good suggestion to have a template for each "Knowledgeable topic", with discussion below.
The top post should be the content (that can be adapted and modified by the manager ), the discussions should have to be public.

I like the idea.

[thatbruce]

Seems like a good suggestion to have a template for each "Knowledgeable topic", with discussion below.
The top post should be the content (that can be adapted and modified by the manager ), the discussions should have to be public.

I like the idea.

I am thinking the template is pretty simple. The post topic is the "How to" question, the body is just
Scenario: ...
Solution: ...

The top post should be modifiable by the manager and the author of that post (preferably in consultation with each other)
Discussion should indeed be public, but ruthlessly cullable by the manager and anyone caught using the word "app" will be taken outside and fed to the goats.

So,
Topic: How to fungle unmentioning brinseckles
Scenario: Your project has many brinseckle objects, some of which
appear to be unmentionable. You are desirous of fungling these occurrences
in an optimum manner which wont disturb the pixies.

Solution: This is easily accomplished by deconcreting each unmentionable
brinseckle using the Dissolve() method of the System.Magic class. See here (dont click it, it goes nowhere)

Any other thoughts?

[gbWilly]

I am thinking the template is pretty simple. The post topic is the "How to" question, the body is just
Scenario: ...
Solution: ...

The top post should be modifiable by the manager and the author of that post (preferably in consultation with each other)
Discussion should indeed be public, but ruthlessly cullable by the manager

I agree

and anyone caught using the word "app" will be taken outside and fed to the goats.

So,
Topic: How to fungle unmentioning brinseckles
Scenario: Your project has many brinseckle objects, some of which
appear to be unmentionable. You are desirous of fungling these occurrences
in an optimum manner which wont disturb the pixies.

Solution: This is easily accomplished by deconcreting each unmentionable
brinseckle using the Dissolve() method of the System.Magic class. See here (dont click it, it goes nowhere)

Any other thoughts?

Seems like a good start. It will probably evolve while using it.

[sholzy]

I just wanted to touch base on this.

Tips and tricks will most likely stay forum based with one entry per topic, and no ability to reply to the topic.

I've been working the past couple of weeks in between other things trying to set up some sort of knowledge base using the wiki function of the new site. The new site software is 1 version newer than what I used on my old site, and I'm not liking how the new version's wiki works as it's been too difficult to make it user friendly - too many opportunities for a user to really mess things up.

[sholzy]

I just wanted to touch base on this.

Tips and tricks will most likely stay forum based with one entry per topic, and no ability to reply to the topic.

I've been working the past couple of weeks in between other things trying to set up some sort of knowledge base using the wiki function of the new site. The new site software is 1 version newer than what I used on my old site, and I'm not liking how the new version's wiki works as it's been too difficult to make it user friendly - too many opportunities for a user to really mess things up.

I've come up with a working solution! The wiki function just wasn't going to work, so I decided to try using the catalog system, which worked out quite nicely. User friendly and very little chance for someone to mess up a submission.

With that system we have custom fields which can be marked either required or optional. I can also make it so a member has to be above a certain number of posts to bypass having the submission validated. A member can comment on the submission which will then create a website comment topic in the forum.

This is the Tips and Tricks section. The Knowledge Base section looks almost identical.

tips_tricks_lc.png