hi ! is there any way to mark a post with more than one author ? In blog-style Discourses might happen that one post/topic is written by several people.
Thanks !
The discussion addresses the lack of native support for co-authored topics in Discourse. edgarriba asks if multiple authors can be credited on a single post, particularly for migrating a blog to Discourse. Thomas_G confirms that currently only the original poster is listed as the author, though wiki editing allows other users to modify the content without changing the primary attribution. edgarriba expresses concern that this does not meet their needs for proper authorship credit and asks about posting as a group user.
Justin clarifies that Discourse is not designed as blog software and suggests alternatives like Ghost, or embedding Discourse comments into external blogs. edgarriba finds the embedding option appealing for their Jekyll-based GitHub Pages site. Falco provides a link to Discourse’s Embedding Comments via Javascript guide, confirming it works with Jekyll.
Alternative workarounds are shared by other users. Marcello_Iaia suggests using Staff Notices to list additional authors, a solution praised by codinghorror. literarymachine requests a feature where wiki editors appear as authors in topic lists, latest posts, and within the post itself. Heliosurge points to the edit history view as a partial solution. Finally, satonotdead shares a new Theme Component, discourse-wiki-coeditors, designed specifically to address the co-author use case by properly attributing edits.
hi ! is there any way to mark a post with more than one author ? In blog-style Discourses might happen that one post/topic is written by several people.
Thanks !
Currently, no. The original poster is the only one who appears as author. However, if you make your post a wiki, then another user with wiki editing abilities will be able to edit it as well.
@Thomas_G thanks for the quick answer, however, I don’t think this fits to the use case I had in mind. We are thinking to migrate our blog inside discourse, and authorship can be a problem for us.
A related question I have is if it’s also possible to post a topic as a group user. That would be great for admins of a group to make announcements or for instance create collective messages.
While Discourse offers some publishing features, we’re not a blog software. If you need specific blog tools, maybe have a look at Ghost? You can always embed a Discourse discussion on a blog if that’s what you’re after.
This is splendid, I didn’t know about this feature to embed the discussions in an external blog post - that could be an option for us. I’ve seen in @codinghorror blog that the whole blog post is created as topic, am I right ?
We have a blog hosted in GitHub pages to promote open reviews and code reproducibility. We use Jekyll under the hood and if we could synchronize the discussion somehow with the forum that would be amazing.
Please, share any good resource so that I can check it out. I leave here the link to the prototype of our blog and forum. Feedback is welcomed too ![]()
You can use Embedding Discourse Comments via Javascript to sync the blog with Discourse. It works just fine with Jekyll.
@Falco thanks for the suggestion - we’ll take a look at it !
We have a similar problem. Mentioning the authors in a staff notice is the closest solution I’ve found:

That is a very clever workaround with the staff notice on the post! ![]()
We are using discourse for a social intranet in a big public institution and are quite fond of it. One increasingly important use case that we have, is providing information in form of wiki pages. I know that this is not the main focus of discourse, but let me explain how we would love the wiki content to be represented anyhow. In essence, we would like an edit to a wiki page to have a similar effect as if the author replied to a post. I see three places for this effect:
Any finally, when viewing a post, it would be great if the last editor, not the initial author, would be shown:
Any thoughts on this, and perhaps any advice on how to implement this as a theme component?
This might work in part but think have to hit the upper right pencil to view edit history.
Might be able to modify component or make a feature request/PR
I ran into the same limitation and just published a Theme Component to cover exactly this use case: