Basic Product Documentation

feature
1

Hi, I’m new to Discourse and I’m just looking for basic documentation about features. Searching these forums so far hasn’t yielded the kind of information I’m looking for. I particularly want to know about what badges, groups, and trust levels are intended for, and what functionality options they carry. Sorry if this is a duplicate.

1 Like
2

Badges are there to encourage experimenting with features and reward great content. They are a substitute for the user manual.

Groups are 100% about security, if you need a particular group of users to see content that nobody else can see, you start with a group. Then you assign the group to a category.

There is a trust level explanation topic in the faq category here, but in general, trust level lets users have more community cleanup and moderation powers as they spend more time on the site.

3 Likes
3

Jeff,

Thanks for the info! Can you elaborate on what you mean when you say badges are a substitute for the user manual? That’s the only part I’m not sure I understand.

1 Like
4

Here’s an example:

http://blog.codinghorror.com/level-one-the-intro-stage/

Badges give you a set of objectives that you can achieve in your own order, on your own terms, and you “explore” the product to get there.

5

This is great information. Thanks again!

6

+1 for this. Where is the Discourse documentation?

Is there actually no documentation for this project other than the API documentation??

1 Like
7

Start with the #howto category particularly the #howto:faq subcategory which has some basic user and admin guides.

4 Likes
8

awesome! Is it possible to add links to these pages in https://docs.discourse.org? They’re not at all obvious to find, and their URIs are perplexingly obtuse

9

I can’t speak for discourse.org but I don’t think so because https://docs.discourse.org is the Discourse API Documentation for developers. Those links are for other interests.

By the way, using those links without a useful label is rather unhelpful behaviour.

The documentation could be improved but it is a massive job for a constantly changing open-source product.

If you look at the #howto category you will see a diversity of interests which cannot be catered for in one document anyway:

There’s also an awful lot of crossover in topics and that is very obvious in other categories that impact the UX:

2 Likes