Clean up categories

[repeatedly]

I noticed some articles are placed under incorrect category.

• trouble-shooting, signals and etc articles are in Configuration.
• Community is in Developer.
• etc...

We should move above artciles into correct category.

[hkmurakami]

+1

[kiyoto]

I think Community under Developer is okay (where else would you put it?)

I agree with Troubleshooting is miscategorized. So is Performance Tuning, Signals and Failure Scenarios, and possibly Monitoring.

I am thinking of moving them to a new category called Operations. Thoughts?

[repeatedly]

@kiyoto Community includes useful information for non-developer, e.g. SNS links and Meetup. So it seems common information.

@komamitsu suggested that use 'Operations' instead of 'Configuration' at first. After that, separating articles into another categories.

[hkmurakami]

I'm personally going to work on removing "mailing list", "source code" and "bug tracking" since they're now redundant with the community article.

Unless there's a good reason to keep redundancy (visibility?)

[kiyoto]

@repeatedly I don't think it's wise to call the top level category "Operations" since most people don't care to "operate" Fluentd instances at first. They probably want to configure it to play with it before they run a cluster of them.

@hkmurakami We definitely want to keep specific second level navs such as ML, source code, bug tracking. One idea:

1. Create a category/section called Community
2. Put stuff like mailing list, Twitter, Facebook there.

[hkmurakami]

@kiyoto Could we keep the second level navs but have them link to community#mailing-list, community#source-code, etc?

Presentation wise, having all the social/community stuff in one document seems like a better user experience than having many separate small docs.

[kiyoto]

@hkmurakami 👍

[kiyoto]

Let's leave this issue open as we make iterative improvements on categorization.

[hkmurakami]

👍