Ever since dev.to went open source, we've had people interested in working with this codebase to build dev.to for music, dev.to for book clubs, dev.to for entrepreneurship etc.
We have a large community already contributing back to the project, so we're excited about the potential to make the underlying platform reusable. This goal is not necessarily part of our own business, but it is a use case we want to support for the broader community. However, it will take some work before we get to this point.
Here is a post I made a several months ago, well before we actually went open source, which muses on this general idea:
Work to be done
The phrase "dev.to" is currently mentioned in 172 different files throughout the codebase. Obviously, a generalized version of the app can't have "dev.to" hardcoded. This is just one example of a step that stands in the way of generalized re-use. The "about" page is also currently hardcoded, as are lots of other elements.
We believe that we can work together to generalize these features little-by-little so that we eventually have a very robust social platform that solo developers can make use of and configure for their needs.
This is not something we can put front-and-center on our own roadmap, but we can actively work with contributors that are excited to push ahead on this goal.
This thread is for any questions you might have. Basically, it is my open inbox on the subject. I'll try to respond to anyone with questions along the way about what work can be done and how. Any pull requests that improve the code and also move us towards this goal have a good chance of being merged.