I think in addition to the "Reading List" section, a "Tools/Resources" section would be useful on dev.to, what say?
For further actions, you may consider blocking this person and/or reporting abuse
I think in addition to the "Reading List" section, a "Tools/Resources" section would be useful on dev.to, what say?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (7)
I agree with the idea, though what I did for myself was keep GitLab snippets of interesting things, which eventually morphed into a list of articles and notes on them
Notated and organized personal bookmarks, open sourced
Table of Contents
About
Why?
I have a habit of accumulating things to read which never actually get read.
To combat this, I went through and actually read everything that I wanted to at some point in time with the goal to open-source the knowledge gained from it.
Usage
Build Process
This is built using GitHub Pages and Jekyll, though the original lists are in my GitLab Snippets.
It's a tad heavy-handed of a solution for the average use case, but I had almost 200 items on my Reading List, so I needed to manage it better.
This way, I got my Reading List down to 0 with knowing I had somewhere to reference neat things later. Now it's back up to 40 things. but it's nice having my Reading List back to being purely "to read".
Consider opening a feature request in the dev.to repository.
yes thanks
how do you imagine it? What content will it have?
I suppose something similar to the "Reading List" section for the UI part, with stuff that can be used or you plan to use later on, for example this article here " dev.to/aershov24/8-steps-to-increa...".
Of course you could always just place it on a mental shelf inside your brain and reach out for it from the "Reading List"section later on... this is just further organization of resources.
I definitely agree with the general idea here, but it might need to be fleshed out a bit. Always a matter of finding the right generalized on-site tools. But the whole readinglist or "saved posts" area in general hasn't gotten love in a while. As @nickytonline mentioned, you're more than welcome to open an issue about this.
I think a better approach would be to create your own lists, rather than just a new section.
cool feature, post it in their github repo's issues