# Category Intersections

**URL:** https://meta.discourse.org/t/category-intersections/79932
**Category:** Feature
**Created:** [September 14, 2017, 3:11pm UTC](https://meta.discourse.org/t/category-intersections/79932 "2017-09-14T15:11:06Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [September 14, 2017, 3:11pm UTC](https://meta.discourse.org/t/category-intersections/79932/1 "2017-09-14T15:11:06Z")

</div>

A simpler way of describing [what’s being asked for here](https://meta.discourse.org/t/category-bundles-aka-category-intersections/35278/) is that this would essentially mean supporting intersection pages for categories, same as we already do for tags:

> [@Tag intersections page](https://meta.discourse.org/t/tag-intersections-page/47952):
>
> I’m currently working with @bedhed in the preliminary stages of working on the bidirectional nav / Table of Contents features described [here](https://meta.discourse.org/t/paid-fullstack-dev-for-bidimensionnal-navigation/45388/5). One slightly large piece missing from this work is a page which could display an ‘intersection’ of tags, (ie, topics which have both the ‘pr-welcome’ and ‘votes-friendly’ tags). A mockup is here: Two questions: Is this a change that would be welcome / tolerated in core, if it were true that it didn’t change any existing functionality? (This s…

So just like we’re currently able to do this with tags:

```
https://meta.discourse.org/tags/intersection/docker/email

```

This feature request asks for the ability to do something like this with categories:

```
https://meta.discourse.org/categories/intersection/support/howto

```

although ideally the category intersection wouldn’t need to be defined by a series of categories listed in the URL, but rather a single identifier:

```
https://meta.discourse.org/categories/{custom-name}

```

* * *

There’s not a strong use case for it here on Meta, but [discourse.codecombat.com](http://discourse.codecombat.com) could really use this for their [“Other Languages” category](https://discourse.codecombat.com/c/other-languages). That’d allow them to use sub-categories for each of their language categories, while still being able to bundle those language-specific categories together.

The Rust community could possibly merge their users and internals forums, which would be a big win.

Doing this properly does involve more UX work than the tags equivalent though.

---

<div class="post-metadata">

### Author: ![mcwumbly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mcwumbly/32/103861_2.png) [@mcwumbly](https://meta.discourse.org/u/mcwumbly)
#### Post date: [February 7, 2018, 3:05am UTC](https://meta.discourse.org/t/category-intersections/79932/2 "2018-02-07T03:05:25Z")

</div>

Isn’t what you’re describing a category _union_ rather than _intersection_?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [February 7, 2018, 3:25am UTC](https://meta.discourse.org/t/category-intersections/79932/3 "2018-02-07T03:25:17Z")

</div>

Categories are not intersectional like tags are though. Strong walls versus flexible, can apply to multiple things simultaneously, tags.
