合作作者话题

[edgarriba]

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 !

[Thomas_G]

@edgarriba

is there any way to mark a post with more than one author

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.

[edgarriba]

@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.

[justin (Justin DiRose)]

@edgarriba

We are thinking to migrate our blog inside discourse, and authorship can be a problem for us.

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.

[edgarriba]

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

LibreCV

Kornia - an Open Source Differentiable Computer Vision Library for PyTorch

[Falco]

You can use Embedding Discourse Comments via Javascript to sync the blog with Discourse. It works just fine with Jekyll.

[edgarriba]

@Falco thanks for the suggestion - we’ll take a look at it !

[Marcello_Iaia]

We have a similar problem. Mentioning the authors in a staff notice is the closest solution I’ve found:

Post notices (staff notices)

In Discourse 2.3.0.beta4 we added a special call-out notice for new/returning users. Staff can now add custom call-outs above posts, which appear similar to the new user first post call-out. In latest Discourse, we made it so you can also use Markdown. [49] This notes can be added from the button (post admin actions) and Add Staff Notice.

[codinghorror (Jeff Atwood)]

这个方法很巧妙，利用了帖子上的员工通知！

[literarymachine]

我们在一个大型公共机构中将 Discourse 用作社交内联网，并且非常喜欢它。一个日益重要的用例是提供维基页面形式的信息。我知道这不是 Discourse 的主要关注点，但请允许我解释一下我们希望如何表示维基内容。本质上，我们希望编辑维基页面能产生类似作者回复帖子的效果。我看到了三个可以实现这种效果的地方：

• 在主题列表中，如果维基编辑者能以与帖子作者相同的方式列出，那将是极好的：

• 在最新帖子列表中，应显示最后编辑的作者而不是初始作者：

• 最后，在查看帖子时，最好显示最后编辑者而不是初始作者：

对此有什么想法，也许在如何作为主题组件实现这一点上有什么建议？

[Heliosurge (Dan DeMontmorency)]

这可能部分奏效，但您可能需要点击右上角的铅笔图标才能查看编辑历史记录。

Require Edit Reason

The purpose of this component is to encourage users to add edit reasons when they edit a post. Edit reasons are displayed at the top of a post’s edit history modal and are a great way to understand why something within a post was changed. This might be especially useful for users that are able to edit other users’ posts as it will help to avoid any “why did you edit my post?!” responses. How it Works When someone opens the composer to edit, the edit reason field is exposed and marked required.…

也许可以修改组件或提出功能请求/拉取请求。