That’s a great idea. It’s also similar to the setup I had when I was testing Discourse comment functionality. Discourse topics were published to a lightweight Remix/React site via Discourse webhooks. Comments created on the website appeared both on the website and on Discourse.
Having both services be powered directly by Discourse would take care of most of the issues I was running into.
If I was designing this, I’d stress having a super fast loading blog in front of the traditional Discourse application. That approach would also deal with the ongoing issue of slow load times for the full Discourse application.
There are a bunch of reasons why something along these lines would be useful. I’ll add a couple more:
-
It’s socially a lot less awkward to start a blog than it is to start an online community. If you’ve got no users, starting an online community feels weird. It would be great to be able to get a community off the ground by just publishing a bunch of blog posts.
-
In the age of LLMs, note taking applications are very popular. There’s a natural drive to want to publish notes to the internet. I think there’s also a need for it, or we’re going to end up with less shared knowledge. Publishing notes directly to Discourse is doable, but it would feel more natural to publish them to a blog-type site that had Discourse as its back end.