I’ll tell you. I am a Community Manager at a software vendor and am responsible for the platforms the community (at least most of it’s members) wants to use, keeping these platforms viral, cross-linked and functioning as HUBs (entry points).
On the one hand, there’s a WP installation including a blog (kind of a planet) that is stuffed by several members as well as core devs with tutorials and similar stuff. Before using WP-Discourse, I always had to announce the presence of a new blog post/tutorial manually in the boards. This is done “electrically” with WP-Discourse now - so one step less work for me in announcements. Of course, this WP installation keeps main and so called static content like a “Getting started”, a download area etc. as well.
Before using WP-Discourse, community members somehow found the WP post and started commenting on it. In WP, at least by default, only the author of this blog post and the admin get to know about this comment and had to answer it (although they might have been busy with totally different topics at this time). The other community members didn’t even notice that there’s a comment as they might have visited the post before or someat. An example:
- Blog post about a new software version (to spread the news)
Comment: "I cannot install it… " or "I cannot update… " because of this and that error message.
Actually, you want to have this discussion in your boards, right? Additionally, these kind of discussions appear in the boards. When using WP-Discourse, all active members of the boards not only get informed about the new blog post, they also see a new comment on it and can react, most likely in a much shorter time than author or admin of the WP blog post could have ever done.
Thanks to the seven gods and @Simon_Cossar, these reactions in the boards can appear as comments on the original blog post within WP.
From my point of view, this is gold as it is possible to create quick reactions, broadly scattered, involve different peeps into platforms, that they mightn’t have know before and (SEO-wise) generate user generated content.
And here it comes to the point you see:
You’re 100% right! And with WP-Discourse options it is possible to sort that out using Max Visible Comments, Min Trust Level or Only Import Moderator-Liked. And yes, activating these options it is absolutely possible to break the communication flow - so heads up when using it!
In doubt - or when this DC issue comes up in Google Search Console - you might set the canonical tag in WP onto the Discourse discussion. On the other hand you want to have the original focused on your blog entry.
I’m not really sure about it: is this mayhap worth a feature request @Simon_Cossar:
[Story] As a WP-Discourse user I want to have an option whether I want to set a canonical tag to the original WP blog post or not.