When you started your first Discourse community, what did you find hard to do?

Yeah, category creation is buried pretty hard. It’s only on /categories, and in a drop-down that only has one item on most forums (on some it has two).


Partly intentional, though, as site owners tend to create too many categories:


To start


Ah! Thanks for clearing it up Jeff. I agree with Riking too though because it can be so buried sometimes that it can be difficult to find although I see where you are coming from with creating too many categories. The first article was definitely an interesting read.


A tutorial that simplified email setup. I went months with mine misconfigured.


Do you mean technical setup? In this topic we’re talking more along the lines of community management or software onboarding.


I found (and still find) it hard to set up a good moderation model. Detached interfaces for administration and moderation could be a great help there.

This could make it easier and more visual to grasp how moderation is setup and how adjustments change the model and processes. It could also better support on-boarding of new moderators and revising moderation decisions.


Neat suggestion, I haven’t looked at it like that before. Have you set up something similar before? Any ideas you can share here?


Maybe we should have two settings
I mean in settings page only show the settings that are mostly used by the new users and add a :white_check_mark: Show advanced setting checkbox in top alongside :white_check_mark: Only show overridden checkbox to show all the settings below Advanced settings text.


Nice suggestions! We are actively discussing splitting advanced settings even!

This will be tricky to figure out which settings new users use, any thoughts?


For this we should ask community managers which settings did you overridden like now i only edited
these 26 settings.

site description
short site description
contact email
contact url
site contact username
exclude rel nofollow domains

logo small
large icon
short title

base font
heading font

enable google oauth2 logins
google oauth2 client id
google oauth2 client secret
enable facebook logins
facebook app id
facebook app secret

min password length
password unique characters

tagging enabled
max tag length
min trust to create tag
tags listed by group
force lowercase tags


The hardest part of onboarding is figuring out how to deliver information to my users with optimal visibility, concision, and friction.

I’m using Versatile Banner for anonymous users just to give them an idea of what we’re about.

Then I have a category called Start Here

And here is where I’m stuck. I’d like to have about eight fixed topics that are always in the same order. That would let me deliver bite-sized chunks of information. But I don’t see how to freeze the topic order.

I’ve seen people put everything into a massively long topic with a TOC, but I think that’s a bit overwhelming. I could create eight sub-categories with one post each, but then they’re needing to click on the category followed by the topic.

Any ideas?


I never saw all of this in one place, so here’s my partial checklist to personalize a new Discourse install

Menu / About

  • edit the tabs: About, FAQ, Terms of Service, and Privacy

Menu / Admin / Customize / Text

  • Edit the recommended texts
  • Then search for blog.discourse You’ll see a lot of links you might want to change

Most of those links point to the following guides that you might want to copy over onto your site:

You can also search for meta.discourse but most of those references are not visible to most users

Menu / Admin / Customize / Email /

  • Welcome Staff also points to the Moderation Guide

When you say search for, do you mean search in?

What references here are not visible to most users? It will be helpful to work on those and fix.

Do you mean to edit the Welcome Staff to include a link to the Moderation guide?


One thing that i found difficult was lock post vs the close topic function. Yes, they are easy now but I always was locking posts when I wanted to close. I think it would be best to change the lock post icon to make it look different from the close icon.


In Customize / Text, there is a search box that says: Search for the text you'd like to edit. I mean, type “blog.discourse” (without quotes) right there and hit enter.

That’s how you will see all the references to posts on blog.discourse that you might want to relink to your own posts

If you search for meta.discourse (in Customize / Text) you will find, for example, dashboard.s3_cdn_warning which talks about uploading files to S3, which most users would probably never see.

I mean Welcome Staff already includes a link to the moderation guide on meta.discourse, so if you create your own moderation guide, you would want to change that link. I went through all the emails and that’s the only one I saw that includes an external link that someone might want to personalize.


I have set up Discourse for a local political party organisation, that has a complex structure of responsibilities and access rights for the normal members, activists, or members of parliament, etc.

To reflect this in Discourse with permissions and roles, turned out to be hard.


Did you draw out a role assignment table of some sort? How did you design the permissions and roles before trying to implement them?

1 Like

No, I did not draw a table, but now that you mention it, I probably should have. Because political organisations have such a clear structure and hierarchy, I started with the expectation that I could simply mirror the real-world roles and access.

But that turned out to be impossible. So, in the end, I simplified across all elements. Fewer members, fewer roles, fewer rooms.

This did make it much easier to manage, but it also meant less engagement because some people and/or groups did not find themselves in the online version.

1 Like

I’ll say list out all the different roles and write out the access you want, then list our the different Discourse user states and the access they give – you can also leverage category and group permissions, then do a matchup.

You should definitely get something.

I say this because Discourse is a tool, and a tool is only as good as how it is used. You need to use Discourse and customise it to your exact needs.

1 Like

Thank you @osioke,

I hope that you do not misunderstood me. I was answering the question what I found a challenge. I am not complaining or giving up.

Thank you for your ideas how best to proceed.