Olá, estou trabalhando atualmente em um plugin que substitui o editor padrão por um editor WYSIWYG. Acho que é mais fácil para usuários iniciantes como eu e outros. Aqui está um vídeo curto sobre como funciona até agora e quais são meus planos:
Acho que será concluído nos próximos meses (dependendo da minha motivação ). Gostaria de saber se outras pessoas também têm interesse em usá-lo.
Muito obrigado
PS: após concluir isso, reescreverei todos os outros plugins que fiz até agora para que sejam baseados neste editor. Há algumas funcionalidades que planejo, as quais permitirão que outros plugins utilizem este plugin como uma espécie de API para substituir o compositor e o processo de pós-edição por algo personalizado. Para um projeto em que estou trabalhando, isso já funciona bastante bem. O problema é que, atualmente, alguns plugins que modificam o compositor são mutuamente exclusivos. Se ambos forem ativados, haverá problemas. Acredito que este plugin pode ajudar a resolver essa questão. Aqui está o repositório: GitHub - spirobel/discourse-basic-editor: An attempt to make discourse more user friendly. · GitHub
Well done! An incredible initiative and we are already testing it in our discourse composition!
Will be glad to help with Russian translation and bug reports.
Neat idea! Even on my forum, not everyone is comfortable with using the Markdown Editor directly.
The beginners (non-tech guys and elderly ones) probably feel the MD syntax alienish, and sometimes mess up their post formatting. (IDK how tho)
It would be great if the plugin eventually becomes an official plugin.
Or even part of Discourse as a setting which the admin can enable for WYSIWYG editor.
I guess its fixed now. btw… if someone does not have a test instance but wants to take a look: https://cidian.social/
you can create an account there and make test posts
Its my dev instance so it might break sometimes or I will install other things but at the moment the basic editor is installed there.
haha nice sadly it will disappear once I switched over to html only posts. @Cam_Logical I will do this once I switched over to html. maybe not color, but probably alignment.
Would you consider an option for touchscreen users in the design?
The context menus for selection on touchscreens are displayed ABOVE the selection & obscure the button bar when the selection is in the top couple lines of the text box.
This means short messages never gain access to the button bar functionalities.
Could there be an option to have the formatting buttons at the BOTTOM of the text box?
Once oneboxing and the other Discourse related things are implemented we will for sure switch to this true WYSIWYG composer based on CKEDITOR as we used the same one our current website. Great work so far.
Everything works like it would work with the normal editor. The UX is just not perfect at the moment.(if you want you can click on “show preview” and just do this like you are used to) But my assumption is that these features are not that relevant for beginner users anyway, so my urgency to work on this is not super high. The discourse specific additions to markdown (quotes of specific posts, mentions, oneboxes) will not be displayed in the wysiwg part.(but they are still visible in the preview and you can also switch back and forth to the advanced editor. just look at my video) My plan is to add a small button to every link so users can select to make them a onebox. All of this will be done by switching to html only posts. the conversion to and from markdown is just too much of a hassle. It wont be too hard to implement all of this. I read the relevant code in the discourse code base already. But my personal project ( a mandarin, english, german dictionary based on discourse) is higher on my priority list. Please keep in mind that I dont get paid to do any of this.
). Gostaria de saber se outras pessoas também têm interesse em usá-lo.
sadly it will disappear once I switched over to html only posts.
