# Adding a Design category **URL:** \ **Category:** Using this forum\ **Created:** [June 14, 2023, 3:04pm UTC](https://forum.openrefine.org/t/adding-a-design-category/813 "2023-06-14T15:04:39Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![Martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/martin/32/7_2.png) [@Martin](https://forum.openrefine.org/u/Martin)\ **Post date:** [June 20, 2023, 1:58am UTC](https://forum.openrefine.org/t/adding-a-design-category/813/10 "2023-06-20T01:58:33Z")
@ostephen I support the idea of a simplification of the category structure. - `using this forum` get a lot of post that may be more relevant in `support` - I agree to merge `using this forum` and `community feedback` - `Day-to-day project operation` and `News and Announcements` also have a lot of overlap. I think a `Community` category will better represent them (with potential sub-category). The cool things about tags is that they are not specific to a category; for example, the tag [reconciliation](https://forum.openrefine.org/tag/reconciliation) is used in the `Support` and `Using this forum` category For the **internship** , I agree to have one sub-category. We can create one tag per cohort. When we announce the internship program, we can reference the discourse tag for the cohort. This way, conversations can also happen across categories. In summary, here is a tentative new structure (happy to move this to a separate thread if needed). - **Support** (do we need a sub-categories?) - **Development & Design** - with a ‘design chat’ and ‘design proposal’ tag - Contributor Meetup - Internship (with a tag for each cohort). - Documentation (move the category as sub-category since Documentation is part of the software) - **Community** - News and Annoucement - Day to Day - Community Feedback (Do we need that subcategory or message can be posted in the top category?) - Teaching OpenRefine --- _[View the full topic](https://forum.openrefine.org/t/adding-a-design-category/813)._