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.
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).
5 Me gusta
How do I move the photo add button.
3 Me gusta
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
3 Me gusta
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
3 Me gusta
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.
5 Me gusta
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
5 Me gusta
Hello, will it support 3-rd party additional plugins-functions for standard editor like… ?
It will support ckeditor addons instead.
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:
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
0
voters
thaaanks
1 me gusta
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?
Do you have a monetization plan how to raise a sum of money?
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.
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.
4 Me gusta
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.
7 Me gusta
Siguiendo el enfoque de “renderizado de markdown justo a tiempo”, este parece ser un enfoque cada vez más popular. Roam Research y Obsidian (en la última actualización añadiendo WYSIWYG) hacen esto, y el ya mencionado Typora. Puedes ver algunos ejemplos de esto en la práctica en el sitio de Typora:
Este tipo de “WYSIWYG” con la barra de herramientas existente me parece lo mejor de todos los mundos. La mayoría de la gente realmente no necesita un formato más allá de lo que proporciona markdown. Lo que necesitan es una forma más intuitiva de generar y editar markdown.
8 Me gusta
Gran punto. Creo que tiptap.dev tiene el mejor enfoque hasta ahora: tienen atajos de teclado que hacen que parezca que estás editando markdown, pero en realidad es un editor WYSIWG adecuado. Empecé a reescribir el plugin con tiptap en lugar de ckeditor. Pero no lo he publicado, porque no pude encontrar financiación para esto (no me pagan en discourse).
Y no me importa lo suficiente como para trabajar en esto en mi tiempo libre.
Saludos cordiales,
Spirobel
4 Me gusta
Cada vez que un usuario debe usar (y recordar) atajos y comandos, el WYSIWYG no importa. La mayoría de la gente no usa ni entiende markdown o HTML. Aquellos que lo saben rara vez necesitan WYSIWYG y, en su mayoría, en escenarios donde uno no está totalmente seguro de cómo se formatea la salida, como las tablas.
Bastantes aquí viven en una burbuja muy cerrada. Hay una razón por la que WordPress es popular y Ghost vive en los márgenes.
¿Soy solo yo, pero odié Typora? Todo ese salto me da dolor de cabeza.
Y sí, sé que Discourse (casi) nunca tendrá un WYSIWYG real, incluso a la mayoría de los usuarios les encantaría.
Ciertamente se podría hacer. Estoy quizás al 80%. El problema es que no me importa lo suficiente como para terminarlo. Discourse es más un producto de empresa y no un proyecto de código abierto. La gente aquí son en su mayoría empleados de la empresa o quieren usar discourse para sus propios proyectos. Así que la energía simplemente no está ahí. Quizás algún día, cuando esté realmente aburrido, lo terminaré solo para demostrar un punto. 
De todos modos, que tengas un buen día,
Spirobel 
8 Me gusta
Para que los miembros de la comunidad realicen un gran esfuerzo en tales proyectos, debe haber un mayor esfuerzo por parte de la comunidad para patrocinar dichos proyectos.
La financiación colectiva dentro de Meta es un área un tanto complicada. Sin embargo, Pavilion está buscando formas de hacerlo más sencillo.
8 Me gusta
¿Sigue este sitio disponible para probar este complemento? Parece que todavía utiliza el editor integrado.
1 me gusta