You can do that via CSS already:
// hides the tags section of the sidebar
div.sidebar-section-wrapper.sidebar-section-tags {
display: none;
}
5개의 좋아요
Is this intentional? I see that the small description only shows to non-logged in users. Example …
Not Logged In:
Logged In:
4개의 좋아요
I think the theory is that if someone has an account, they know what the community is about already.
7개의 좋아요
There are a lot of posts in this topic, so apologies if I’m repeating something that’s already been said…
Regarding the new notification structure, I have a few comments:
- Someone earlier suggested removing the “all” section. I strongly oppose this. It would be a huge step backwards if I had to go through several subsections to see all my notifications.
- I also oppose the suggestion to make the “all” section sort/group by notification type. The subsections already exist for that purpose… the “all” section should always show in recency order.
- Related to that, I think the notifications in the “all” section get reordered after you read a notification if you read a more recent one first? I don’t get notifications here frequently enough to double check, but I think that’s what I saw yesterday. That seems to imply the highest priority sort criteria is being unread, but I still don’t know if I like that. I feel like the “all” section specifically should always sort by recency. Maybe an “unread” section would make sense for people that get a ton of notifications.
- I don’t have a strong preference on the subsection ordering (I don’t get so many notifications that I’d need to use them anyway), but I do find it a bit odd that quotes appear in the “other” section. Maybe it’s just me, but I consider quotes identical to replies. (Mentions are quite nearly replies as well.) If someone quotes me, 99% of the time they are replying to me, but the default Discourse settings remove the reply if that same user was quoted. Given that setting, it feels weird to consider quotes to be “other”.
- I think it might be beneficial to simplify the sections by combining replies, quotes, and mentions. Not sure if that makes sense for all communities, but if they were grouped I’d be more likely to use that subsection.
- I would make one ordering change. Bookmarks aren’t really notifications (when they are just listed, as they currently are), so I feel like it doesn’t belong with the other notifications. For that reason, I’d move that section below the profile section, and just handle bookmark notifications separately if needed. Alternatively, I’d move bookmarks, PMs, and the profile icons first (after “all” notifications), then show the hr, then show the notification filters. That would mimic what was shown in the old version, with the filters just being an added feature at the end.
- The notification subsection list should be scrollable. On mobile while writing this reply, I couldn’t see the whole menu without completely hiding the editor. It should be changed so that if I tap and drag my finger up/down, the menu slides.
6개의 좋아요
My first impression is that I was kind of overwhelmed and confused. The front page suddenly has a lot going on. And it took my brain a few minutes to wrap around the idea that oh, it’s really the same hamburger menu just expanded by default, moved to the left, and given more functionality.
So I think I can get used to it. 
I do find the design kind of jarring — different sizes, and the ALL CAPS headers in strong contrast to the main design, while the color scheme doesn’t seem to set it off enough. But alll of that can be worked through.
My sites are using the “Categories and Latest” view for the front page by default, which I quite like — but which is kind of redundent with the sidebar menu. I’ll have to figure out how to reconcile that.
10개의 좋아요
I want to second this. It does two things: simplify the confusing interface and make idea of watched/tracked categories and tags more discoverable. On Fedora Discussion, I’m trying to get people into the idea of thinking of a tag[1] as a drop-in replacement for a traditional mailing list. This is actually a pretty good mapping, but people aren’t used to thinking of tags that way as used on social media or in traditional forums[2]. I think having this there would really help.
As a bonus, this makes “Tracked” really make sense for tags and categories.[3].
6개의 좋아요
Maybe we combine all three, but as a starting point, I think it makes sense to include quotes in the replies submenu.
5개의 좋아요
Originally, things worked this way – you had to track or watch things to add them to your sidebar.
We found that there were several cases where folks wanted to have easy access to things from their sidebar but did not want all the extra notifications. This caused people to either get much more notificaton noise – or – to just opt not to put things in the sidebar that they would have liked to.
So, we decided to decouple them.
I think we’re now in an in-between state in our design though.
I like not having to track things to put them in my sidebar, but I agree that it probably makes sense to put things in my sidebar if I do track them. I think it’s likely that we’ll make a change in that direction at some point.
5개의 좋아요
COMMUNITY 외에 다른 표현을 고려해 본 적이 있나요? 이 단어에 대해 좀 더 민감한 편이라, 비유하자면 풍차에 맞서 싸우거나 자전거 창고의 페인트 색을 정하는 일처럼 사소한 문제일 수 있지만… 다른 표현을 사용하는 것이 더 나을 것 같습니다. 해당 섹션이 "커뮤니티"라면, 왜 _메시지_는 "커뮤니티"가 아닌가요? 그리고 여기에는 이름이 #community-building인 카테고리가 있어 더 이상합니다. 또한 _Docs_와 _FAQ_도 "커뮤니티"인가요?
사이트 메뉴는 어떨까요? 아니면 Everything, Tracked, _My Posts_를 **주제(TOPICS)**로 나누고 나머지는 내비게이션(NAVIGATION) 또는 … 무엇으로 넣는 것이 좋을까요?
5개의 좋아요
But “tracked” doesn’t cause notifications right? It just makes it show unread or not. In fact, as I just tried it, the separation causes a behavior that I think will surprise people: if you add a category to the sidebar which is not watched or tracked, it is shown with nothing — just like something you are tracking which actually is all caught up.
I might be missing some way of using this that hasn’t occurred to me, but isn’t that mostly just confusing? There’s not even any indicator of which is which.
On a completely different note: I hope there are theme options to change “5 unread” to just a number (styled in a circle or whatever). Because as I’m looking at this, I think that’s part of what’s contributing to my sense of overload. Fewer words might help.
4개의 좋아요
A different style demands a theme component, but the copy change is doable by customizing the string and replacing “%{count} something” to “%{count}” in:
js.sidebar.unread_count.one
js.sidebar.unread_count.other
js.sidebar.new_count.one
js.sidebar.new_count.other
Some way to differentiate between unread and new when doing this is probably a good idea.
On a different matter, when testing this I’ve noticed that I need to open the Messages Inbox section to be able to see that I have an unread or a new message – it would be nice to have some indicator on the “Inbox” row.
5개의 좋아요
We tried this out at one point, but overall it wasn’t a hit because folks got confused with the numbers changing for new topics vs. unread topics. We are likely to revisit it, but have decided to wait until we can do some experiments around combining new and unread so the number alone would be meaningful.
Yeah, we’re also considering ways to roll things up into the section headers for other sections. So could possibly be an indicator on Messages itself.
5개의 좋아요
Oh, speaking of headers: I found it completely perplexing that the 
by COMMUNITY starts a new message.
5개의 좋아요
This is a good point, earlier on that section was called “Topics” (as you suggested) so it was more intuitive then. We moved on from that because we were getting to the point where we had maybe too many different sections, so we consolidated admin/groups/users/etc into the newly named “Community” section.
5개의 좋아요
This is really nice. It looks clean and feels “inviting” - I enabled and won’t go back to the old hamburger menu.
I see many suggestions and comments but to be honest I really like it.
Im sure it’ll get polished over time but for everyone who runs a discourse instance, and especially for self hosted ( and managed ) ones like myself, we just got a brand new menu that would have cost real money otherwise.
Absolutely fantastic work.
9개의 좋아요
And users think similar way? Because… forums aren’t for admins, self hosting or not, but for users after all 
4개의 좋아요
Sorry for quoting myself, but I’ve been thinking about this. It really would be an improvement.
Alternatively, it could be as it is (maybe a bit narrower) but remain on screen until you click an “X” button, just like the chat window.
2개의 좋아요
It disappears beautifully if you hit the hamburger (a little un-intuitive admittedly). Not sure why my screen recording is yellow / orange sorry!
I would like to have the option of having it minimised by default (with a per-user default too).
2개의 좋아요
Thanks, but I think we are at cross purposes here. I know about the sidebar and how it disappears when you click the hamburger button (I think I suggested here that the sidebar should be hidden by default, so that people can work out the hamburger action intuitively without being surprised). In the post above I was meaning that the notification pane/menu should not disappear as soon as you click one of its links – ideally it would be a right sidebar
2개의 좋아요
Oops - good point! I didn’t read too carefully it seems 
.
I’m not sure I agree. It is a whole lot of stuff to have visible all the time. And if I want the content open for longer I can simply double click on any of the icons to get it in the main container.
2개의 좋아요