We have implemented Discourse for our company’s forums, and I just received the Previous/Next topic functionality as a feature request. I am curious to hear what’s become of this request for the official Discourse project.
1개의 좋아요
Generally use keyboard shortcuts (press the ? key on your keyboard) or use Suggested Topics at the bottom of every topic, which is a de-facto “next”.
1개의 좋아요
Both “solutions” will not work for people who got used to this functionality from other forum software.
Howerver, if the team does not see the necessity for this feature, I guess it should be pretty much plugin material we’re talking about here. “Previous” and “next” topics should be the same as in the category list. So starting from the current topic, we should fetch the two neighboring topics, insert the URLs into two buttons, add them in the footer section above the suggested topics, and would be ready to go. However, I wonder how big the request volume for this feature is: I’ve heard this complaint exactly once on my board; and we have 7k users…
1개의 좋아요
I also will chime in here for a previous/next unread navigation element.
Our community follows a sports team. Just about everything posted decays quickly. Over the weekend, a bunch of threads will be started or added to about the last game, the next game, the performance of league teams, latest recruiting news (it’s a college team). Our members like to check in and read up all the new threads, or new additions to threads, and know they’re caught up. It’s like browsing a sports section that is only about your team.
Right now that requires a lot of pogo-sticking to the top of the categories’ lists.
The suggested posts is a good idea when the community topics are not so ephemeral. Right now, when the team we follow is playing, say, Michigan, the suggested topics might be the last Michigan game, or another IGT (in-game thread) for another team (presumably because we use the same abbreviation in the topic title).
There’s very little call for contextualizing our posts/topics beyond recency.
I can see where many (most) communities would benefit from this kind of thing. I once managed a staff of information architects who worked on ways to provide contextual links on 50,000-page Web sites; it’s hard to do, but has a huge payoff when done well.
Ours is not one that benefits. Discourse is superb for us in so many other ways that not being able to quickly go to “next unread” it is a minor annoyance. But it would be a nice addition.
1개의 좋아요
Some of this may be solvable quite easily with a few switches
-
Should you consider tagging here, so there is some way to glue team games together? Eg: tag Michigan games with #michigan
-
Perhaps we could enable a mode were last N topics where there is tag and category overlap always show up in suggested.
We’re actually not interested in last year’s Michigan game - that was an example of the kind of algorithm-driven suggested link that makes no sense for us.
We’re just looking for a way to read through all new posts without having to return the the “latest” list to do it.
1개의 좋아요
But suggested already does that, can you explain how it is failing.
If there are unread posts in topics you are tracking we will show them in suggested first.
If there are new topics suggested shows them second
Otherwise … random
1개의 좋아요
If I have understood correctly, I think it is related to this:
For example, today I read through my unreads here on Meta. Then I read through new topics in a couple of categories I’m watching. Having read the last of these in Features, I’m presented with this:
However, visiting the “New” page shows there are still at least two new threads in UX, a category I’m watching, but these are not shown to me as suggested topics. Instead, I see Support and Dev, which I’m not watching.
As I said in the other thread, my expectation would be that “Suggested” prioritises categories I’m watching, but this is not the case for new topics.
2개의 좋아요
I may be misunderstanding, or in a weird situation that is not bringing out the best.
We migrated our forum from an existing SMF install. Many thousands of messages. Users are not that psyched, so new posts have been low.
It may be that without new posts, the suggested posts is over-represented with what it believes are the best possible but are actually of little-to-no relevance.
As all users are wont to do, I have begun ignoring the suggested posts when my first experience with it was not helpful. I’ll pay better attention.
We are also suffering from being used to the features we had that don’t have an immediately obvious parallel on Discourse. In most (maybe all) cases, there is a parallel that we just have too stumble upon.
SMF had its own problems (UI and everything else), But getting to the bottom of new posts on a thread and simply hitting “Next” was kind of nice. 
You may want to go into site settings and turn down the suggested time interval, which defaults to 1 year, to something like 3 months so it is only suggesting more recent topics (when it can’t fill from new and unread).
This is where I am struggling big time. If there are no new posts, nothing is going to really help you.
If there are new posts in tracked topics OR new topics… they will always be on top of suggested before anything else.
Maybe the issue is that you have a huge number of OLD topics that nobody is tracking?
3개의 좋아요
Thanks for all the feedback on this … Reduced the time frame on related to 30 days and at least the related are now somewhat relevant due to recency.
We’ll see how it plays out.
1개의 좋아요
@codinghorror 사이드바를 많이 사용하게 되면서 이 주제를 다시 꺼내게 되었습니다.
보통 이런 상황이 생깁니다. 특정 주제의 "부분 집합"을 보고 있는데, 추천(suggested) 목록이 제 입장에선 잘못된 우선순위를 갖는 경향이 있습니다.
구체적으로 “ux” 태그의 새로운 주제라는 특정 부분 집합을 처리하고 있는데, 추천 목록에 랜덤한 “읽지 않은” 글들이 끼어들어 방해가 됩니다. “추적(tracking)” 같은 고급 필터를 사용하면 이 문제는 더 커질 것입니다.
“다음/이전” 주제 이동에 대해 키보드 단축키만 사용하는 것부터 시작하는 건 어떨까 생각했습니다.
동작 방식은 다음과 같습니다.
- 어떤 주제 목록(태그의 상단/읽지 않은 글 등)을 방문하면, 이를 메모리에 필터로 추적합니다. (전체 페이지 검색에도 작동해야 합니다.)
- t n을 입력하면 "최근 목록"의 다음 주제로 이동합니다.
- t p를 입력하면 "최근 목록"의 이전 주제로 이동합니다.
전반적으로, 저는 수년간 이 기능에 대해 반대해 왔지만, 이제 특정 워크플로우에서 얼마나 유용할 수 있는지 깨닫게 되었습니다.
이것을 핵심 기능(키보드 단축키 전용)으로 만드는 것에 대해 어떻게 생각하시나요?
3개의 좋아요
키보드 단축키로 사용하는 데는 괜찮다고 생각합니다.
1개의 좋아요
GMail에서 선행 사례로 j k를 사용하고 있는데, 이미 사용 중이므로 우리는 이 키를 사용할 수 없습니다. 다만, 목록에서 사용하는 것과 동일한 단축키를 선택한 점이 매우 흥미롭습니다.
현재 사용 중인 단축키를 살펴보고, 직관적인 단일 문자를 사용할 수 있는지 확인해 보고 있습니다. 오른쪽 화살표와 왼쪽 화살표는 직관적이지만, 일부 키보드에 해당 키가 없거나 실수로 누르기 쉽습니다. 특별한 아이디어가 떠오르지 않는 한, 일단 2자 단축키로 시작해 보겠습니다.
2개의 좋아요
최상위 내비게이션, 태그 및 카테고리에 대한 구현은 다음 커밋 기준으로 완료되었습니다:
개인 메시지, 검색 및 북마크에도 추가할 수 있을지 확인해 보겠습니다. 기본적인 기능은 모두 여기에 포함되어 있습니다.
5개의 좋아요