Markdown vs HTML in CMS

I am working on a fairly large CMS application that includes a forum, wiki pages, etc. What did you choose between Markdown and HTML? I am concerned about the usability and the fact that non-technical people will use it.

  • Markdown has a very simple syntax, but few people know it.
  • with HTML you can use the WYSIWYG editor, but they are often scary.
+4
source share
5 answers

If usability is the problem and the target audience is non-geeks, WYSIWYG outperforms Markdown. People are used to toolbars with formatting buttons, but Markdown is a completely unknown markup language for most people (even the "markup language" is completely unknown!).

I had to explain the Markdown-lookalike Viking syntax for non-geeks at work, and they don't like them. When you want to write something, you want to write something, not look for the strange ASCII syntax. Try not to interrupt the flow of users.

I would find a good WYSIWYG editor, such as the one in WordPress ( TinyMCE ). It is working fine.

+8
source

I will vote for Markdown.

  • Markdown 5 , . , , , , .

  • Markdown , .

  • Markdown , , HTML. WYSIWYG. , no- script .

, , HTML Youtube .

+22

Markdown WYSIWYG-, - WMD Editor, ( 99%) StackOverflow.

- , , , WYSIWYG, Markdown, . , Markdown (, , ...)

WMD Editor ( StackOverflow), , Markdown .

+4

XHTML , XHTML. WYSIWYG ( , , ), ( , ..). , , . , XHTML .

+2

Markdown CMS, Grav .

It's easier to change styles, but not html content. And you take one killer function: use git for website content. You can even create branches with holiday content.

In fact, Markdown is easier for non-technical people.

0
source

Source: https://habr.com/ru/post/1725784/


All Articles