Setting up categories for Discourse

Who would volunteer for thinking (really hard) about a category structure for Discourse and setting it up? We should make use of sub categories, for example creating a “Groups” category (I just did that), and then cautiously fit all relevant topics into sub categories.

Don’t forget to take a look at the different use cases: a newbie, an experience site integrator, someone who starts helping with developing Neos itself, a designer, someone who is looking for a job, someone who wants to organise an event, a member of the Neos team, aaaaand so on.


PS: Bonus task (maybe @berit?): we’ll need a nice color scheme for the category colors, based on the Neos palette of course. So for example the “Groups” category could have a certain color and then sub categories a specific shade of that tone.

Sure can have a look at the category colors as far as someone came up with a great list of category names :smile:

The topic is too big for me currently, but my 2 cents

We need a “Neos User Group” (meetup) main category, maybe with per country subcategory (France, Germany, Switzerland, Moon, …) to keep track of the community activity in the real world.

I can’t take care of it either atm, but I want to point out a quote from the Discourse Guidelines that @sebastian already posted:

So we should maybe start with a more generic structure and add sub categories when needed

All right, I’ll give it a try:

  • Announcements
  • Lounge
  • Community
  • Community Building
  • Events & Meetups
  • Show & Tell
  • French Community
  • Polish Community
  • Development
  • Neos Userland
  • Neos Core
  • Flow Userland
  • Flow Core
  • Design & UX
  • Documentation
  • Finances & Fundraising
  • Tools & Operations
  • Marketing
  • Neos Team
  • Neos Team Internal

I suggest that projects (i.e. temporary ventures) don’t have their own, dedicated category but belong to a corresponding topic category. For example, the project “Github Move” should be discussed in Tools & Operations.


I’ve set up everything now, looks pretty good to me. What do you think?

1 Like

Good work so far, I like the system very much. Makes it easy to participate and it is nice to have such a great mobile access as well :wink:

Regarding categories here are my 2cents: I would suggest a special category for newbies like me e.g. Development > Beginners Corner and I could imagine questions raising about the topic of setting up Neos, though I did not really have troubles with that myself.


Good idea, as right now as a beginner you have no obvious place to go to in those categories. I’d place it on the top level, though so it can be used by new writers, designers, … and not just developers. :wink:

1 Like

@lordrhodos yes, great idea! For now I created a Newcomer’s Corner as a sub category of Lounge. Let’s see if it fits there.

One more thing… What about a place to discuss translation? It could go into Development, but that might scare off “non-developers”. But for a top-level category, it might be too “unimportant”. Or we just see how it develops…

The idea comes from this thought I just had: “Yeah, I finally have a place where I can put the overview of all things around the translation process!” :slight_smile:

I still miss a specific category for packages. This would be a very simple way to list existing packages until we have a more sophisticated package listing somewhere else. I wouldn’t expect to find that in “Neos Userland” (which should be in sync with Slack neos-general btw.).

@hlubek is your intention to list packages or discuss their usage? But I guess just in general, having a category where you could ask “is there a package for this and that already?” would make sense.

Do you think it should be top level?

Regarding neos-general – I think we should rename the channel in Slack then, “neos-general” and “neos-dev” wasn’t that intuitive IMO.

I don’t understand the “Development” category. What’s the reasoning behind it?

For Neos users the term “Development” might be misleading, we always have to keep in mind that frontend developers, integrators (and hopefully content strategists in the future) are a very important target group for Neos. Even more so than PHP developers if you ask me.

So let’s not scare off people by having a too dev-centric community.

1 Like

Don’t you think that Frontend Developers and Integrators are developers, too? That’s all Development.

:wink: Well… let’s try to be more welcoming here.

Let’s see it from the perspective of someone not involved with too much coding (no PHP etc.) it could be distracting to have very technical/PHP topics mixed with integration / frontend related topics.

I think both is fine. Users can ask questions about which package to use for a specific use case and packages can be submitted to have a better overview (I really have none so far) of what exists already.

I would also vote for changing the name “development”. A pure frontend dev with focus on html and stuff like that doesn’t necessarily see himself/herself as developer. This is the same for me, the word development lets me always think about PHP and with this as a first impression it doesn’t matter that from a technical point of view also frontend development is development.

I could imagine something like this:

  • Community
    • Community Building
    • Events & Meetups
  • “Using Neos” or “Working with Neos”
    • Installation & Deployment
    • Plugin Development
    • Frontend & Integration
  • Developing Neos/Flow
    • Neos Core
    • Flow Core
  • Design & UX

I like the suggestion of Berit, but still cannot avoid a chuckle here:

[quote=“berit, post:17, topic:51, full:true”]
A pure frontend dev […] doesn’t necessarily see himself/herself as developer[/quote]

Emphasis is mine. No pun intended! :wink:

I know what you mean but I only used the wording frontend development as we are used to it. But there are other words wich are used for the same people like for example web design.

@berit yes, that’s a great suggestion to distinguish between “Using Neos” and “Developing Neos”. Also, we didn’t have a category yet for Installation and Deployment.