共著トピック

[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を使用しており、その点に非常に満足しています。ますます重要になっているユースケースの1つは、Wikiページという形式で情報を提供することです。これがDiscourseの主な焦点ではないことは承知していますが、Wikiコンテンツをどのように表現したいかを説明させてください。本質的に、Wikiページの編集が、著者が投稿に返信するのと同じような効果を持つことを望んでいます。この効果には3つの場所があると考えています。

• トピックリストでは、投稿の著者と同じようにWiki編集者がリストされると素晴らしいでしょう。

• 最新の投稿リストでは、最初の著者ではなく、最後の編集者の著者が表示されるべきです。

• そして最後に、投稿を表示する際に、最初の著者ではなく、最後の編集者が表示されると素晴らしいでしょう。

これについての考えや、テーマコンポーネントとして実装する方法についてのヒントがあれば教えてください。

[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.…

コンポーネントを変更するか、機能リクエスト/プルリクエストを作成できるかもしれません。