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
That’s what I do, almost always.
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 サイドバーを頻繁に使うようになった今、このトピックに戻ってきました。
よくあるのは、特定のトピックの「サブセット」を見ていて、推奨機能が私にとって優先すべきものを誤って優先してしまうことです。
具体的には、「ux」タグ内の新しいトピックなど、特定のサブセットを順に追っているのですが、推奨欄には無関係な「未読」のものが混ざって邪魔になります。これは、「追跡」などの高度なフィルターを併用するようになると、さらに大きな問題になるでしょう。
そこで、まずは「次のトピック」「前のトピック」へ移動するためのキーボードショートカットのみで実装するのはどうでしょうか。
仕組みは以下の通りです。
- 任意のトピック一覧（タグ内の最新や未読など）を開いた際、そのフィルターをメモリ上で保持します（ページ全体の検索でも同様に動作します）。
- t n と入力すると、「最も最近のリスト」内の次のトピックに移動します。
- t p と入力すると、「最も最近のリスト」内の前のトピックに移動します。
全体的に、この機能には長年反対してきましたが、特定のワークフローにおいて非常に有用であることが今では理解できます。
これを（キーボードショートカット限定で）コア機能として実装することに、あなたはどうお考えですか？
「いいね！」 3
キーボードショートカットとしては問題ないと思います。
「いいね！」 1
Gmail の先行事例では、この操作に j k が使われていますが、これらは既に割り当てられているため使用できません。しかし、リスト表示で使っているショートカットと同じものを採用している点は非常に興味深いです。
既存のショートカットを精査し、直感的な単一文字の割り当てが可能か検討しています。右矢印と左矢印は直感的ですが、一部のキーボードには存在しない場合があり、誤入力しやすいという欠点もあります。そのため、ひらめきが得られない限り、まずは 2 文字のショートカットから始めようと思います。
「いいね！」 2
トップレベルのナビゲーション、タグ、カテゴリについては、以下のコミットにより完全に実装されました：
PM、検索、ブックマークへの追加も検討しますが、基本的な機能はすべてここに含まれています。
「いいね！」 5