Category Cleanup: 4 Ways Your Discussions Categories Can Be Better Optimized
Tags: github, community, githubdiscussions, opensource
Published: 2024-01-30 16:42:36

When building a community it is important to design with your members in mind. However, even the best laid plans may not have the intended effects. Something we experience while building [GitHub’s Community Discussions](https://github.com/orgs/community/discussions/) is miscategorized posts. Miscategorized posts are like putting your kitchen gadgets in your neighbor’s garage—it makes it harder find the thing you need — plus someone has to clean it all up 🧹.  

**What is a miscategorized post?**

A post about a topic in a category that may not be relevant, nor the best fit for that topic (i.e. requesting a new profile achievement in the repositories category). 

**Why are they a problem?**

Hubbers—people who work at GitHub—subject matter experts, and community members may gravitate to their domain, and therefore completely miss a post that interests them if it goes into the wrong category. This leads to the original poster (OP) feeling ignored; they may not get help, or their feedback may be skipped, thus souring their experience. It is no picnic for the community manager or maintainer either. Someone has to move their post and their data may get skewed if there is a large influx of miscategorized posts 😡. 

This was a really big problem for the [Projects and Issues category](https://github.com/orgs/community/discussions/categories/projects-and-issues). This category once saw 78% of posts in one week be improperly categorized. Thanks to dedicated efforts, and the tools we had at our disposal, we were able to reduce that to an average of 19%. This average is still trending downwards 🎉. 

Do you have a category in your Discussions that is plagued by miscategorized posts? Read on to see how we cleaned up and made a better community for everyone 🙏. 

## Naming 
![Marge Simpson angrily saying “they want a name, not a vague description”](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vu899qp5jm9uz6xqvgnw.gif)

Shakespeare said “What's in a name? That which we call a rose by any other name would smell just as sweet.” The same does not apply to naming your community category. Naming is what helps us differentiate one thing from another. 

When deciding a name for the Projects and Issues category we originally chose `Issues`, but that led to folks reporting any type of issue, from console log errors, to their new TV not connecting. We thought things would get better with `Issues and Projects`, but that resulted in folks sharing their (albeit awesome) projects in the category. We sat down and thought further on how to solve this. We realized  we now had another problem: users wanted to share their projects, but didn’t have a dedicated space to do so. 

Luckily, this added a datapoint to usher in our [Programming Help category](https://github.com/orgs/community/discussions/), which gave users a space to share their projects and ask for help. A community is like a living organism, and should evolve to meet their members’ needs 🧬. 

With the new category added, we tried one more rename to clear up our category’s intention: `Projects and Issues`—the name you see today. In the month following we saw a 14% reduction in miscategorized posts. 

## Category Forms 

With category forms, you can make templates on a per category basis that can contain text, or several  features— such as an ‘agree to terms’ checkbox —while automatically applying labels 🏷️.

We took the approach of adding a warning to the top of the form of what topics should be discussed here. We also had the posting member select which feature they’re discussing, which then adds the appropriate label. Finally,  a checkbox which links to descriptions of Projects and Issues on our docs. The category form allowed us to display information upfront and in multiple places, plus helped us with our labeling 🤓.   
 
![alt text: This image is a screenshot of the category form for the Projects and Issues category in this community. From top to bottom, this form includes a text field where you can enter the title of your post, a warning message about what to post in the category, a dropdown menu where you can select a topic area, another dropdown menu where you can select a feature area, a large text field for the body of your discussion post and a checkbox confirming that the post is relevant to the Projects and Issues category.](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/xr8ov17ry7xduote508t.png)




Check out [how to create your own](https://docs.github.com/en/discussions/managing-discussions-for-your-community/creating-discussion-category-forms) or feel free to [borrow from Community Discussions’ templates](https://github.com/community/community/tree/main/.github/DISCUSSION_TEMPLATE). 

## Description 

A small, but overlooked area of Discussions, is a category’s description field. This field doesn’t just  display at the top of the category. You’ll also see it when selecting a category from the New Discussion button, and when creating a new Discussion in that category, thus propagating the information in several different places. 

However, don’t just create a description and think you’re set—be intentional and iterate as you see the community using the category. 

![Alt text: Screenshot of the Projects and Issues category description: 🛑 STOP: THIS CATEGORY IS SOLELY FOR CONVERSATIONS ABOUT THE GITHUB PRODUCTS ISSUES AND PROJECTS. UNRELATED CONVERSATIONS WILL BE DELETED.](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8v2xb8ex8d6sfdipsgor.png)

## Awareness 

A common theme among these measures is putting information in multiple places, or writing the same information in various ways in the same category. Here are some more examples of how we drive awareness of what the Projects and Issues category is around the community. 

On an individual level, when we move posts out of the category, we comment letting the member know their post was being moved and why. We use [saved replies](https://docs.github.com/en/get-started/writing-on-github/working-with-saved-replies/about-saved-replies) to easily disseminate the message and have a consistent approach. Most members are thankful that we let them know, and that we placed their post in a category more likely to get them a reply 🎉. 

![Alt text: Add a saved reply screenshot, saved reply title is Squirrel ship, and the body says This looks great :shipit: it! And a green button that says Add saved reply.](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/lrupf9j7uodcusml3uds.png)


When making changes to the category, we’ve made quite a few. We also made sure to post an announcement sharing the news. We usually tie this into existing content we’re posting like category updates to ensure it doesn’t get missed. Depending on your community, standalone posts that are [pinned](https://docs.github.com/en/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion) globally or in the category can be a great way to get eyes on changes to the community or category. 

![Alt text: Screenshot of the Projects and Issues category from top to bottom it includes the category description, four pinned category posts, and two unpinned Discussion posts](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/wr5uf8igi9u0gojnecfn.png)


By using Discussions tools and taking a multi-faceted approach we were able to turn the Projects and Issues category into a much more thriving space. 

Do you have a category or Discussions space you were able to transform?  Share your story below! 

_This was originally published on [GitHub Community Discussions](https://github.com/orgs/community/discussions/88425)._