![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Links to other posts with the same tag
Title:
Links to other posts with the same tag
Area:
tags, entries, content discovery
Summary:
Add links for previous and next entries using a given tag, when you've gone to a post via the tag list
Description:
If I want to look through someone's entries with a particular tag, which are scattered among other entries, the only way I know of at the moment is to keep going back to the list of posts that you get when you click on the tag. It would be smoother if there were prev/next links between the entries.
Drawback: because an entry can have a lot of tags on, it would be unwieldy to have 2 extra links per tag, so you need a way to decide which tag to provide sequential links for. If a specific tag was defined as the active one, because you came to the post by clicking on it, perhaps the links could be dynamically allocated?
In cases such as reading a work that's being published in chapters, or reviews of episodes of a specific show, the author could provide links, but that would involve going back to the previous chapter or episode and editing in a link, so it's extra work for the author. If there was a way of doing it under reader control using the existing tags, it would be easier and also cover situations where the journal author didn't know it would be wanted.
This suggestion:
Should be implemented as-is.
11 (47.8%)
Should be implemented with changes. (please comment)
4 (17.4%)
Shouldn't be implemented.
3 (13.0%)
(I have no opinion)
5 (21.7%)
(Other: please comment)
0 (0.0%)
no subject
Otherwise, as someone who puts five, six, seven tags on my own posts, that dynamic post-tag-forward-back element could get very very messy on the post, very fast. I'd think.
no subject
no subject
I'd vote for this part, because of the drawbacks you mentioned, though I'm still not entirely sure how implementing it would work.
no subject
no subject
Oh, though I guess that wouldn't work in sitescheme pages.