Maximize simplicity

I think that Discourse is a very powerful tool, mature, robust and customizable. I’m sure it can suit all our needs. I find only one danger that may compromise its success: too much complexity or an excess of information may be overwhelming for users.

The WEAll community doesn’t need to be the place where users connect every day, spend much of their online time inside and want to be up to date of all content. This may be one possible profile, but probably many of them will be more casual users. That enter here for one specific consult and then leave, or that subscribe to one or a few topics to be notified of new publications, and mainly ignore the rest. We need to take into account that if many people uses it, there will be a lot of information here. And casual users do not want to invest a lot of time in learning to use a new tool, or to customizing it to their needs. They want just to enter, get what they want and go on to other thinks in their lives.

E.g. imagine that in Scotland Hub they are very active in a project to influence some policy makers. But I don’t live in Scotland and I’m not interested in policy makers, I’m here for the narrative communication to the public. If every day I enter the site I see several new messages with the progress of this project and of two other ones from other hubs (and also receive emails of them), it’s possible that I end up stop using the site or muting everything. But perhaps I want to be notified, instead, when the project is finished and they write a summary post in a Special Announcements category.

I’m very fan of two principles:

  • Hiding things we aren’t interested in.
  • Opt-in better than opt-out.

In my ideal platform setup, a new user would find a clean interface, in their native language by default, with very little content and a clear path of the next step to do. At first, they should be presented an onboarding process, that ideally could be completed in a few minutes. It should show the basic working of the user interface, how to configure their minimal user profile and then go to a “new users” category to post a salutation message or ask for help.

The final step would be reaching a kind of “site map” with shows all kind of contents available in the platform, and explain how to subscribe to the information they are interested to (for example, watch the categories for your regional hub and the themes you want to actively follow). They should not receive push or email notifications until they start actively using the platform, and only after they choose what they do want to receive. For example, this final step should teach the user to go to “email” and “notifications” settings and choose their implication level.

And I also think we should avoid to show too much information in the screen at any time. For example, having only a few categories of first level or hiding tools and toolbars until user discovers them and set them opened if they want. And perhaps deactivate things like “Suggested Topics”, as explained here. I think this last one adds a lot of noise and may confuse users moving them to a different category they were navigating. Or at least give it less visual importance, by using CSS to make the text smaller, adding a grey background or similar.

We should take into account that this is not a commercial site, that wants to force users to “engage” and spend a lot of time trapped inside it. The objective should be to give the most valuable information with the least effort and time.

What do you think?

1 Like

Very much concur with this. Firstly on the Discourse platform. It appears very robust and much more workable that Hylo. However this idea of having ‘layers’ of content that people opt-in to is a vote winner for me. Must, however, not bury content under layers though - so that it becomes obtuse to access. So, a well worked out, intuitive graduation of content that flows with people’s existing engagement level (casual member up to hub activist for example)


Very much agree. In different roles I’ve found myself having to work recently with Teams, Slack, Circle, Zoom and now Discourse. And I’ve worked a lot with IT in my life. It is like having to learn multiple languages and that’s before getting into any content!

So please keep it as simple as possible to start with. A few broad headings and then see what emerges. Both topics and groups interested in them. Keep it macro. Sub-headings can come later in the light of experience. A blizzard of messages on anything and everything will just confuse and put people off.


This is a great discussion. Discourse has a couple features that can help with this out of the box. One is that new users are limited in what actions they can do, and only gain new functionality as they interact with the site. I think for the purposes of the testing period the team raised the default permissions so you can see / do more.

There’s a similar discussion in this thread about what an onboarding flow would look like, and what tools we might be able to use (pinned topics, links to youtube intros, etc) might be helpful. Community Inspiration (Zebra's United layout and structure) - #3 by nms

It looks like it is possible to set default notifications setting for a group, so it should be possible to implement @andres.moya 's idea of having a blank slate. @Aamirah-WeAll what do you think about experimenting with these settings?

However this idea of having ‘layers’ of content that people opt-in to is a vote winner for me
@clive.wychwood I’d be curious to get your thoughts on whether the tags are a helpful way to start to track content you are interested in. The sidebar should show you when new topics are posted in tags that you are following

Thanks. Yes it would. And I could see that being useful. However the perspective I was looking at is a beta tester really, seeing how this would play out with other users. And the points @andres.moya were getting at struck me. So I am thinking more in terms of how content can be layered so that it appears less over-whelming to begin with but as you peel back the layers more detail can emerge. Certainly the Hubs aspect will already assist with this - especially if Hub moderators can manage access/permissions and create categories/topics depending on user. But more broadly, it may be useful to have a greater degree of control over access depending on user level. Perhaps the badges, especially if they can be customised, might be more useful here than tags.

This discussion is really allied to here though - About organizing categories

Counterpoint - I would love something more robust that does allow depth and regular use.