Why not use composer-redactor as default editor?
-
Why not use composer as composer-redactor as default editor?
User forums are mostly lay people and they do not want to know the markdown syntax. WYSIWYG editor for lay people is who they like and make them more comfortable.
Because it seems the plugin-composer-redactor is the best thing to be the default editor in NodeBB.
And also if there is a post created using a plugin-composer-redactor, then the post will seem chaotic when we switch to plugin-markdown. I guess this is a big problem in NodeBB. Is NodeBB created so that we could choose the plugin that we love easily?
But if we use plugin-markdown and we switch to plugin-composer-redactor then the post seems OK.
So for now I can not use the plugin-composer-redactor because when NodeBB v1 released and NodeBB team still choose plugin-markdown as the default editor, then I had to switch to plugin-markdown (Because it will be supported by NodeBB team). And all posts in my forum will seem chaotic.
For that for a while I had to use a plugin-markdown in my forum since many plugins that work with plugin-markdown and appear chaotic if I use a plugin-composer-redactor.
And I hope when NodeBB have stable plugin-composer / editor, so I can switch to the plugin and my forum's posts will not appear chaotic. -
As a forum owner, I can say that redactor does have some notable standing issues for people running active communities, ranging from sterilization to backwards compatibility with formatting, to lack of compatibility with plugins and general confusion for the community. It's a great plugin, but far from ready to be a default.
-
OK, if redactor is not stable or else, but don't use markdown as default. Users mostly lay people and they DON'T want to learn markdown, specially in my country Indonesia
If redactor is not stable or have drawbacks NodeBB team might continue to developed it until stable, or please develop other editors, not markdown.
WYSIWYG editor or BBCode editor is easier for the users.
-
@agusputra The simple fact is everyone's use case is different, which is the point of the plugin system. You don't have to use the default at all, because plugins like redactor exist.
I dont see what advantages there would be to switching the default markup of NodeBB,
-
@Arc OK. I tried to not use the default editor (plugin-markdown), there is redactor, but it's not from NodeBB team.
I install redactor and it seems it clashed with other plugins.
Because might be the other plugin authors just test their plugin with just NodeBB default editor not redactor.Editor is crucial for forum software.
And I think mostly forum users don't want to learn markdown, they just want to type the text.And one another problem with markdown, how can I resize the image ? (I dont want to enable html for my markdown plugin).
OK if composer-redactor has many drawbacks, may NodeBB team had another solution to be the default editor.
I just hope that do not use plugin-markdown as the default editor.
-
@Arc said:
As a forum owner, I can say that redactor does have some notable standing issues for people running active communities, ranging from msterilization to backwards compatibility with formatting, to lack of compatibility with plugins and general confusion for the community. It's a great plugin, but far from ready to be a default.
I dont see formatting redactor as a big problem, its just html and you can make any plugin to work with it
If devs chose to develop redactor could be compatible with all in a week.
I didnt have much problems with plugins while using redactor. Wich you guys had problems with?
Anyways i prefer a new composer layout that work on mobile before having to worry about redactor or markdown -
@agusputra said:
I just hope that do not use plugin-markdown as the default editor.
It's fine as the default editor, just because you don't like it, and it's not popular in your country, doesn't mean everyone else should think the same way. The whole point of the composer being a plugin is you can change it yourself. Redactor was a paid for system donated by another user, which is still in active development.
And I think mostly forum users don't want to learn markdown, they just want to type the text.
Then how is BBCode a better alternative, I'd much rather do
> this is some quoted textthan[quote]this is some quoted text[/quote].The whole point of Markdown is you just type the text. BBCode is clunky and old, WYSIWYG looks good on the surface, but the code that gets spewed out behind it is usually absolutely disgusting to look at.
-
@agusputra said:
@a_5mith but for BBCode the users just need to remember element name
[b], [img] etc. And for markdown they need to remember various marks :*, **, ![](), #, etc
One could argue that BBCode is more obtuse and hard to learn, and that the only reason it is preferred is because it's simply been around longer.
I personally find
*italicised text*easier to understand vs[i]italicised text[/i].Also typing
[and/make my right hand all contorted. I've always hated that. -
Markdown is excellent for bloggers since they type a lot. Redactor is excellent for occasional posting for non-bloggers. I like Markdown but it is not for everyone since there is a learning curve.
I say give the user an option to choose either Markdown or Redactor in the user settings or as a cookie when replying to a post. It will not be for the admin to make the choice. It is for the end user.
-
I've always wondered why BBCode
[b][img][strong]is considered easier to learn than HTML<b><img><string>? -
Just to note here.
2 most reasons why I have migrated to NodeBB:
- Markdown
- NodeJs
-
Wonder why the thread went to markdown vs bbcode...
Redactor is WYSIWYG so better to focus on Markdown vs WYSIWYG
-
@agusputra The whole point of markdown is so you don't have to worry about resizing images. The CSS handles image size via the max-width attribute so it doesn't overspill the container. There's nothing to say you couldn't change that value to make images smaller though.
-
@henrywright It's not really. BBCode came about because forums didn't want people posting plain HTML (risky) so a separate language (Bulletin Board Code) was created to work like HTML but with the ability to sanitise all the input.
Logical at the time to replace <b>Text </b> with [b]Text [/b].
-
It would not be hard to add a plugin that could handle setting the size of an image manually, if it is really needed. I'd think it would be bad to manually size images inside of posts though, as it might break the responsiveness of it. The software should auto resize any images that are too big based on screen size.
-
So, what do you want? Do you want BBcode? Do you want Wysiwyg? Do you want more helper buttons?
