It would be nice to use Discourse for discussions of jenkins.io blogposts, books about Jenkins and other similar content. It would allow having live discussions and a great feedback channel for our content. LinkedIn and Reddit have been already successful as a discussion venue, we could do the same in our default channel.
For jenkins.io we could even automate creation of threads later. For now it could be a pre-publishing step and a “discussionsTo” metadata
So I am +1 for having discourse embedded into blog posts like Community Highlights: 25th edition - Home Assistant does. Looks like its just a simple javascript embed which is easy. The problem is that you need the post created before you can embed comments for it. Which is a bit chicken and egg thing. I was originally thinking we could make each new jenkins.io auto create a post using rss feeds, but I don’t know how we could link them up though.
As for blogs/book discussions. I’m certainly not against it, I think its a bit premature. Maybe its something we put it into “uncategorized” or “using jenkins” or something and see how often it comes up. I still am not sure how we should setup categorization yet.
The problem is that you need the post created before you can embed comments for it. Which is a bit chicken and egg thing.
Why Chicken&Egg?
Expect authors start a Discourse discussion BEFORE the blogpost is published, as a part of the PR checklist. It might be a natural way to facilitate initial feedback for a draft, actually
Expect authors to add a discussion ID in the blogpost YAML metadata when they submit issues
I guess its cool that way, I was thinking that the discussion wasn’t a good plan until the post was approved, but there’s no reason that limitation has to be approved, nor that it has to be in some sort of “blogpost” category or anything.