Bookmarks on dev.to

twitter logo github logo ・1 min read

I would really like to have bookmarking functionality embedded into https://dev.to engine so that we could bookmark interesting articles for future use.

I am aware of both browser bookmarks and 3rd party bookmarking services, but the real advantages to having this on-site are: sharing the bookmarks with other community members (maybe even implicitly, when I choose to show my bookmarks to strangers,) and/or maintain a list of interesting posts right here.

What do you think? /cc @thepracticaldev

twitter logo DISCUSS (20)
markdown guide

Hey @mudasobwa , on-site bookmarking is definitely something we've considered. Last time we had tossed this idea around internally I believe we got stalled up in trying to imagine what the UI would look like both on the article itself, and in your individual "saved articles" area.

I could see us tackling this in Q1 of 2018; but, it would be way more awesome to work directly with the community build the feature once we open-source.

Do you have initial ideas on where the "bookmark" button would live on the article?


Hey, thanks for the quick response and the interest in listening to users’ input.

it would be way more awesome to work directly with the community build the feature once we open-source

Is it node? Well, I am maybe a good developer, but I am an awful UX designer. I could help with backend (unless it’s node which I hate :),) but for UX please ask the community, I wash my hands here.


It's a Rails app but there'll be something for anyone to do 😁

On the note of this feature, we've also talked about "subscribing" to posts/threads. Like if you see something that has no comments yet you can listen for the comments, like if I wanted to keep track of this post. This may be the same abstract concept as bookmarking or it might be two distinct features. That's something we have to work out.

Rails? I am in.


This may be the same abstract concept as bookmarking or it might be two distinct features.

I vote for the same concept: posts I commented, posts I want to track and posts I bookmarked are all posts I am interested in. They all could’ve been placed together (e.g. with different color bars on the left) and the appearing green icons denoting “there were updates there since you’ve seen it for the last time.”) Or, in different tabs.

I should be able to remove them from this “track page,” but IMHO they should appear there by default in all three aforementioned cases.

I maybe way off here but IMHO, subscribing (that includes posts where I commented) and bookmarking are two separate features.

I would bookmark/save a post only if I want to refer to it in future. When I have bookmarked a post doesn't necessarily mean I want to be notified of each and every action in that post. One thing which I would like as a user of bookmarking feature, would be to able to categorize the bookmarks. Since we're already using tags in the posts, we can factor in that prebuilt categorization (it would be awesome if I could add my own private tags while bookmarking, but mostly that would be too much to ask for in the short run).

Subscribing/tracking a page only have limited shelf time, once the discussion have died down in the post, you may no longer be interested in it. Explicit subscription (as opposed to posts where you get notifications just because you participated) to a post could go as a separate feature (a separate page where you can see all your subscriptions)

This is mostly a reply to @sharajeev since the thread did not allow me to answer directly.

In the development process, I always tend to use the Occam’s razor to shave off all the good-to-have and release must-have in the first place. People differ, hence the pattern of using the feature differ. Less amount of entities is always great. I wish all the interfaces in the world would derive from DWIM but until we are there, let’s help the users to get accustomed to new features quickly.

One page having default sort order, stored in settings, is fine. You go there, you sort by bookmarks-first and you are all set. You just don’t give a piece of cake to what is blinking there in the bottom.

I go there and I see everything interesting.

The diversity of people’s habits literally enforces us to build as simple interfaces as possible. In my very humble opinion, of course :)

let’s help the users to get accustomed to new features quickly.

True. Agree completely.

Was just pitching in with my thoughts since the discussion was open ended.

Me either :)

I am not sure what approach is better; but since mine is simpler and involves fewer entities, I advocate it. The discussion is surely open-ended and I appreciate your participation.

Ideas are the value, aren’t they?

Ideas are the value, aren’t they?

They're. :-)

I am not sure what approach is better

Not about better or superior. One is a time tested approach (the normal bookmarks), the other one (combining subscription and bookmark) is a new approach and there will always be discussions until it's the norm.

Subscribed posts can be captured in your normal feed (augmented with notifications), and then you just need a page to see all your subscribed posts, be it the bookmark page with a color coding, or a separate tab in your dashboard itself. Doesn't matter.

combining subscription and bookmark is a new approach

Not exactly. I have the idea stolen from Russian online community habrahabr.ru that served the “interesting for me” content that way from the day one (10 years already approx.)

Habrahabr interface

Didn't know about it. :-)

Certainly new or less prevalent ideas can be brought mainstream, that's how we move forward.


It's a Rails backend :)

We have some great UX designers in the community who might be willing to lend a hand — check out yesterday's article by @jovansavic !

I will be happy to contribute with UI/UX and with HTML, CSS, JS when it's time. :)

When will dev go open-source?

I don't want to jump the gun with an "official" timeline, but I think Q1-2018 (if not hopefully a bit sooner) is pretty realistic.


Agreed. I can save an article sometimes, but so often I'm reading something and want to come back to it. How do you do that?


Hi, I think is is a great idea! Is this already implemented? Like Robin I recently liked a post but I couldn't find it. Unfortunately, I can't remember the post's title nor its author. I'd also like to help but I'm not a Rails developer. Maybe I could help with the testing? :)


Yeah great idea, actually I was looking for something right now, because I had "liked" some post recently and wanted to check it to share with someone but now I can't find it back unless I use the search functionality :)

Also pretty cool idea to do this with open source contributions, looking forward to see how it turns out!


Hellooo guys come on implement this already is mid 2019!!!

Classic DEV Post from Jun 1 '19

What the heck is a Developer Advocate?

TL;DR: A developer advocate is a developer’s best friend! For the past three years or so, I have bee...

Aleksei Matiushkin profile image
NB! I am _not_ a member of #DEVCommunity. → I like: Elixir, Erlang, Ruby, R, C, COBOL. → I hate: Apple, JS, Rails, haters. → I am more functional, than object oriented.

👋 Hey dev.to reader.

Do you prefer sans serif over serif?

You can change your font preferences in the "misc" section of your settings. ❤️