The original poster, Stéfan_van_der_Walt, is seeking a solution to avoid topic creation when blog posts are loaded. Currently, an associated topic is created on Discourse whenever someone loads a blog post, but the desired behavior is to create the topic only when a reader clicks “start conversation.”
itsbhanusharma and merefield suggested that an acceptable compromise already exists, which allows the topic to stay unlisted until the first comment is posted. merefield demonstrated that when a Ghost post is linked to Discourse, the topic is indeed created but remains unlisted.
However, Stéfan_van_der_Walt expressed that this solution does not suffice, as it still creates a bunch of empty topics. jericson proposed an alternative solution to hide unlisted posts for staff, but Stéfan_van_der_Walt emphasized that the original proposal is to stop post creation until a button is clicked.
Eventually, Stéfan_van_der_Walt announced that they have found a workaround to implement the desired behavior and thanked everyone for their interest.
We have a blog (https://blog.scientific-python.org) that embed discourse comments.
Currently, whenever someone loads a blog post, an associated topic is created on discourse.
Instead, we want to wait until a reader clicks “start conversation” before doing so.
Don’t want to discourage anyone from taking this as a project but I believe an acceptable compromise already exists which allows the topic to stay unlisted until first comment has been posted. A lot of users choose to do that instead of deferring topic creation so I thought it might be of your interest.
I also find this annoying. I wonder if this could be solved by an option to hide unlisted posts for staff. Probably not globally, but maybe in specific categories. And, of course, there’d need to be a way to turn off the option temporarily. I think that’d be less work than changing the way the system currently works.
I appreciate all the suggestions for alternative options, but this proposal is for stopping post creation until a button is clicked.
Are there any fundamental objections to that idea being implemented as proposed?