Do you foresee hive.blog in the future being handed off to another front end team in some way?
We're not the core dev for condenser now. Hive.blog is just one site that uses the condenser code base.
Several developers contribute to the condenser code base, but @quochuy is probably the most prolific contributor right now, and you can find his contributions in his blog feed.
On our of devs, jsalyers on gitlab , also makes contributions to condenser. Generally his changes are to support and test new core features of Hive, like the recently added decentralized lists. Further back in time, we also used condenser to test the changes to the core API libraries to allow for swapping between API nodes when an API node is experiencing problems.
Other devs make changes to support their own dapps (@jpphotography recently made a contribution to support truvvl posts).
I did ask our devs to look at vision (the open-source code base for ecency), and we do expect to contribute to that code base as well in the future, once some more of my frontend devs free up from their current projects. Vision has a better and more modern design framework than condenser.
At one point, I was considering dropping all work on condenser and porting hive.blog to use vision'scode base instead of condenser's code base, but I've come to believe that condenser has one feature that is both a blessing and a curse: it supports server side rendering, which makes maintaining the code a pain, but is apparently very beneficial for organic search ranking. Because of this, I don't see us replacing condenser on hive.blog until this is no longer such a big issue. I think it's important that Hive has at one site that does well in organic search ranking.
Clicked on the two bottom devs, but the links are apparently broken.
Yep, sorry, missed a p in jpphotography, and the other was a gitlab handle, not a hive handle.