Discourse 基本エディタ

[Heliosurge (Dan DeMontmorency)]

I can see where you want to go. If I understand correctly you want to create a kind of full Editor with much more advanced functionality using html to give a much more complete experience.

[oshyan (Oshyan Greene)]

I for one would love to see a WYSIWYG editor that preserves the markdown output. I am less concerned about being able to type in and have it interpret markdown; normal shortcuts like e.g. Ctrl-B (bold) are fine, or the toolbar. But I do want to preserve later editability, interpretation outside of a rendering context, and exportability. And HTML in my experience is problematic for at least some of it not all of that.

I am curious what specifically you are wanting the editor to do that is not compatible with markdown output?

Also I’ll point out that Typora does a pretty good job of handling rendering of markdown in-line as well as shortcuts, and I don’t see why a formatting bar couldn’t also work (though it doesn’t seem to have one).

[ozkn (Mathx)]

How do I move the photo add button.

[feabila (Felipe)]

Hey @ozkn!

I’m working in a way which just imageUpload will be necessary! So, you could follow the same lead. In your initializer you could modifyClass of component:b-editor changing setubBasicEditor function.

api.modifyClass("component:b-editor", {
   setupBasicEditor(){
       loadScript("/plugins/DiscourseBasicEditor/ckeditor.js").then(() => {
           ClassicEditor.create( document.querySelector( '#editor' ), {
                toolbar: [xxx],
                ...
           })
   }
});

Checkout this Configuration - CKEditor 5 Documentation for toolbar reference, in my case I’m justing using toolbar: [“imageUpload”]

Best regards

[feabila (Felipe)]

Hey guys! Maybe I could use a little help from you!

I’m working in a project which I use more than one composer, like this (in the beginning of the initial page, for users create topics by there, just like a main composer facebook-like).

According to this, I have been getting some issues when opening composer (maybe 'cause I’m already using in main page).

So, when I want to update a topic, I use composer controller to open model, but getting b-editor message.

Have you guys getting same problem in working with multiple composers ?

Best Regards,
Felipe

[spirobel]

maybe you can deactivate the plugin for now. As I said, this is still work in progress. I will probably work more on it next month. I focus on learning mandarin at the moment lol. If you want you can link me to your github or send me your code so I can try and understand what you are trying to do.

[neo (R.Zhang)]

Reporting a bug, it seems after activating the plugin, the management section was covered.

• Test version: Discourse 2.7.4 stable
• Test browser: chrome, firefox on both computer and mobile phone

[GVG]

Hello, will it support 3-rd party additional plugins-functions for standard editor like… ?

Discourse Mark Plugin

discourse-mark Repository: GitHub - sirideain/discourse-mark: Adds highlighting to Discourse [2018-07-24_22-01-29] Features Adds an editor option to highlight text. Usage You can wrap text with == to highlight it. ==Highlighted Text== Installation Known Issues None Future Update icon to highlighter once Font Awesome 5 is available

[spirobel]

@GVG

Hello, will it support 3-rd party additional plugins-functions for standard editor like… ?

It will support ckeditor addons instead.

@neo

Reporting a bug, it seems after activating the plugin, the management section was covered.

This is an ui simplification experiment of mine that will probably be put into a separate plugin. Feature creep is bad haha

I want to say something: without a source of monetization it does not make sense for me to write this code. I also tried to do closed source plugins:

Sync your Discord roles with your Discourse groups!

But the the issue is that code gets shared among buyers, which means there would be a need for a constant stream of new clients that dont come through word of mouth which is hardly sustainable.

So I would be interested if you would be willing to pay for this and if you have any suggestions on how we can solve the code sharing among buyers problem.
If yes please tell me how much in the comments below.

Would you be willing to pay for this?

• yes
• no

thaaanks

[GVG]

@spirobel

It will support ckeditor addons instead.

Does this your new WYSIWYG editor change the posts structure over standard Discourse? By another words if your editor will be disabled - does posts created with your editor will have any issues with editing by the standard editor?

[neo (R.Zhang)]

Do you have a monetization plan how to raise a sum of money?

[spirobel]

@GVG

By another words if your editor will be disabled - does posts created with your editor will have any issues with editing by the standard editor?

at the moment the editor generates markdown so we can use both editors next to each other without any issue. But the experience is not perfect and it always will be if we stick to markdown. Thats why the final solution will produce html. If this is a deal breaker for someone because they dont want to be locked in, there is an easy fix for this: just convert the html back to markdown.

@neo

Do you have a monetization plan how to raise a sum of money?

I think there is no need to raise money up front. If I know there is a bunch of people that would be willing to pay for it and how much I will just finish the code. You can also reach out to me in private if you feel uncomfortable sharing budget related discussions in public.

[GVG]

@spirobel

at the moment the editor generates markdown so we can use both editors next to each other without any issue. But the experience is not perfect and it always will be if we stick to markdown.

Have you try to discuss this nuance with Discourse Team? Maybe they also want to add some new WYSIWYG editor?

[spirobel]

@GVG

Have you try to discuss this nuance with Discourse Team? Maybe they also want to add some new WYSIWYG editor?

they opted against it on philosophical grounds. You can search the forum if you are interested in the details. Their arguments are totally valid and I respect them. Thats why I am working on this.

[oshyan (Oshyan Greene)]

「ジャストインタイムレンダリング」というアプローチを踏襲すると、これはますます人気のあるアプローチのようです。Roam ResearchやObsidian（最新アップデートでWYSIWYGを追加）はどちらもこれを行っており、前述のTyporaも同様です。Typoraサイトで実践されている例をいくつか見ることができます。

Typora — simple yet powerful Markdown reader.

この種の「WYSIWYG」と既存のツールバーの組み合わせは、私にとって最良の選択肢のように思えます。ほとんどの人は、Markdownが提供するもの以上の書式設定を必要としません。彼らが必要としているのは、Markdownを生成および編集するための、より直感的な方法です。

[spirobel]

@oshyan

ほとんどのユーザーは、Markdownが提供するもの以上の書式設定を必要としません。

素晴らしい点ですね。tiptap.dev がこれまでのところ最善のアプローチだと思います。Markdownのように編集できるキーボードショートカットを備えていますが、実際には適切なWYSIWGエディターです。tiptap を使用してプラグインを書き直しましたが、ckeditor の代わりに使っています。しかし、資金が見つからなかったため、公開していません（Discourse から報酬は得ていません）。
そして、自由な時間を使ってこれに取り組むほど気にかけていません。
敬具、
Spirobel

[Jagster (Jakke Lehtonen)]

ユーザーがショートカットやコマンドを毎回使用（および記憶）する必要がある場合、WYSIWYG は関係ありません。ほとんどの人は、Markdown や HTML を使用せず、理解もしていません。知っている人は WYSIWYG をめったに使用せず、主にテーブルのような出力のフォーマットが完全に確実でないシナリオで使用します。

ここのかなりの人々は非常に狭い世界に生きています。WordPress が人気があり、Ghost が周縁化されているのには理由があります。

私だけかもしれませんが、Typora は嫌いです。あの飛び跳ねるような動きは頭痛を引き起こします。

そして、はい、Discourse が実際の WYSIWYG を（ほとんど）決して取得しないことはわかっています。ほとんどのユーザーはそれを望んでいるでしょうが。

[spirobel]

@Jagster

そして、Discourse が実際の WYSIWYG を（ほぼ）決して得られないことはわかっています。ほとんどのユーザーがそれを望んでいるでしょう。

確かにそれは可能です。私はおそらく 80% 完了しています。問題は、完成させるほど気にしていないことです。Discourse はオープンソース プロジェクトというよりは、会社の製品に近いです。ここの人々はほとんどが会社の従業員か、独自のプロジェクトで Discourse を使用したいと考えています。そのため、エネルギーがありません。いつか本当に退屈したら、証明するために完成させるかもしれません。
とにかく、良い一日を、
Spirobel

[merefield (Robert)]

コミュニティメンバーがこのようなプロジェクトに多大な努力を注ぐためには、コミュニティ側もそのようなプロジェクトを支援するより良い努力をする必要があります。

しかし、Meta内でのクラウドファンディングは少し厄介な分野です。Pavilionはこれをより簡単にできる方法を模索しています。

[th21]

このサイトは、このプラグインのテストでまだ利用可能ですか？ビルトインエディターを使用しているように見えます。