it sounds a lot like you're reinventing what Beaker Browser had built on top of DAT, except that it could do more. For example, they made a distributed Twitter clone as a proof of concept, but folks actually started using it. Definitely included blogging stuff.
Really cool stuff around taking sites and things other folks had built and using them as a basis for your new thing.
https://github.com/beakerbrowser/beaker/ If you're not familiar i'd recommend starting with some of the YouTube videos giving an overview. It was pretty cool.
Alas, the main dev was hired by BlueSky and is now working there... but wonders if maybe you couldn't take that idea or its tools, and mush it together with yours.
I'm one of the creators of the Beaker browser[1] and the reason we use Dat is that as a p2p protocol, it offers a lot of neat properties, including making datasets more resilient. As long as one peer on the network is hosting a dataset, it will be reachable, even if the original author has stopped hosting it.
I won't speak authoritatively on behalf of the Dat team, but I believe one of their goals is to make it difficult for public scientific datasets to be lost, and data living on a centralized server is particularly vulnerable to that.
Also, because Paul has awesome projects, and deserves some attention when a project of his makes it to the top of HN but doesn't even mention him, he is working on a browser for the distributed web called Beaker (I am using it to write this now), and it is awesome.