The categories here have grown organically over time. There seems to me to be a lot of overlap in their purposes. This adds friction when adding new posts and makes it harder for interested parties to focus on areas that are relevant to them.
My thoughts come out of our discussion about the role of slack. If we want this place to be our long term memory, I think the information architecture is one critical aspect to supporting that goal. I’m trying to strike a balance between:
- Clear, big buckets so it’s obvious where your post can go
- Buckets that can be tuned with subcategories when they get noisy at the top level
- Trying not to over structure in a way that would lead to ghost towns for certain categories
Here is my first pass proposal for restructuring them (ordered by my best guess at where they will fall in post frequency).
- Think #announcements in slack
- Official Blog posts and their comments would live here as well
- (any other big addon), the rest can be add in the root
- (This area can grow to how to’s, links to blog posts, etc)
- Core Teams
- Learning Team
- (This area can grow to meeting notes, other team discussions)
- Show & Tell
With this, I’m also proposing the removal of Search, Design, Performance (which can easily fall into the Help section) and Proposals (Which our RFC repo takes care of and announcements will serve as notification for).
I’m sure this hierarchy isn’t completely sufficient, but I wanted to take a stab at it. Is there anything that’s missing? Thoughts and objections welcome!