@Sandeep and @fazlerocks have already provided great answers explaining the story of Hashnode. I would like to touch upon the development and execution workflows. A brief discussion of our tech stack took place here.
Hashnode is an isomorphic app built with Mongo, Express, React, Node(MERN). Isomorphism was a big deal for us because our site is content-driven and we needed top-notch SEO but at the same time we didn't want to miss the advantages of client-side rendering. Considering how important isomorphism is for us, we wanted to make it easy for other developers to get started with isomorphic apps, soon we are going to release an open-source project in this field.
In terms of our development process, we have an internal list of features that we think are helpful for developers and steadily we are introducing them to our system. User feedbacks have a great say in our development process, a lot of user feedbacks have been incorporated as features in our current site. If you have any feature request that you think will help developers get better, please send it to us asap.
We are a growing community and we want to make it super easy for developers of all level to be able to express themselves here. Our design team tries hard to communicate this particular message to developers, our why-join page is one such example.
We have a closely knit team with diverse skill and common goal, all of us are driven about helping other developers get better (including ourselves 😉 ) and we like to stay ahead of curve in adapting newer technologies. We believe in experimenting and shipping features quickly.