Dev.to is awesome indeed, it's just a few features short from perfection. Here's the 3 features I wish it had:
1. Ability to archive posts straight from the share menu
I tend to archive the best post I come by, but in order to do so I must bookmark them first, then go to my reading list and only there I can find the Archive button. I wish it was a one-click experience instead
2. Hide or grey out the posts I have seen/opened already
I wish I doomscrolled Dev.to as often as I do Facebook... but I can't even if I want to. An ability to skip the items you have already seen would be very helpful here, since subsequent attempts to scroll through Dev.to often comes to spending too much energy to identify what you have already read or worse -- decided not to read earlier. I wish the feed would automatically filter out (or at least grey out) the items I have already opened and let me mark items seen myself.
3. Tips
The feed has evolved a lot during this year, but I don't feel like I am fully aware of its nuts and bolts, so I am not making the most out of it. I wish there was a link to some wiki page (or at least some tooltips) right on top of the feed explaining it all.
That's all I have -- not a big ask, I assume. I wonder if you feel the same way or what features would make Dev.to perfect for you instead.
Top comments (4)
@tinkermakar
I loved your points especially the second one.
I would recommend adding a label of:
#discussbecause it is targeted to whole community thus leading to a better discussion.many thanks! Guess what, my PR that partially addresses #2 has just been merged, I am super thirlled 🥳
If you have over 600 bookmarks in your reading list and you want to knock out one tag at a time, you can do that now -- opening an article and then going back persists the tag that you had selected
These are awesome ideas, Makar! Appreciate ya sharing with us. Good stuff. 🙌
1 - I had never noticed there was an archive feature before you mentioned this...
and I have no idea what it does so I'm scared to click it.
2 - this would be possible using the CSS
:has()superpower, except the blocks used in the feed page are kinda weird. They use multipleatags and some script to make clicking the entire card work as if you clicked the anchor. If they used normal semantic HTML it'd be possible, but the way it stands I don't think it can be done, as I don't think you can access:visitedfrom a DOM query (it's a security feature). Maybe someone could rework the feed HTML though.