Over the past few weeks, we have spent some quality time with discussions on how we can set a high, yet achievable benchmark on the quality of the content that is shared on Hashnode.
One effort in this direction was to launch an experimental feature called Hashtrends, for all off-topic developer discussions. In the coming days we will work more on Hashtrends based on the feedback we’ve received so far.
Another aspect in this regard was nodes. Nodes, as sub communities, each catering content to a specific technology, or framework, or programming language; are central to Hashnode.
With Nodes, we have observed the following significant problems.
The past system had us creating new nodes, whenever a post was tagged with a node not already present in the database; this led to a lot of redundant nodes cropping up in the system (for instance: React, and ReactJS).
Over the past few months, we have observed an unprecedented increase in the amount of content shared across Hashnode. While being gleeful about it, we couldn’t help but notice content getting shared across wrong nodes.
This in turn was diluting the quality of individual node pages; and we strongly felt that these pages were not fully serving the value proposition of being awesome communities.
To fix these issues, and then some; we have come up with the following changes.
A brand new Nodes gallery
We’ve done some spring cleaning, and removed all the irrelevant, and redundant nodes.
- No more React, and ReactJS
You can check out all the nodes currently available on Hashnode, in this shiny new gallery.
We’ve come up with a category system to organise all the nodes in place.
- Instead of the old “Databases” node, you will now find a new category in which you can find all the specific nodes (MongoDB, MySQL)
If you think your favourite programming language is missing a community on Hashnode; you are welcome to give us a suggestion from the new Nodes gallery.
You are still free to tag content with a node that is not already present in the system. The “absent” nodes will appear disabled; and when tagged with such a node, we would automatically get a new node suggestion for the same.
Feed filters for all the Node pages
- Want just the stories published in the React node. Now you can, with the new node based filter interface, available on all node pages.
Introducing Node Admins, and Managers — Power to the Community
Being an admin or a moderator of a Node, grants you certain abilities, from changing the appearance of certain elements in your Node to removing irrelevant content from your Node’s feed
The only difference between an admin and a manager: an admin of a node has the power to add/remove managers from that node.
Introducing Node Leaderboards
- Leaderboards are generated individually for each node every month, based on the total number of appreciations, and upvotes you receive in that specific month.
With improved nodes, and putting the decisional power for filtering the content in the hands of community; we are sure that these changes will aid in setting a high bar on the quality of the content. Let us know what you think, and do write to us with your feedback, to firstname.lastname@example.org