When comparing Markdown vs enduro.js, the Slant community recommends enduro.js for most people. In the question“What is the best Node.js-based CMS?” enduro.js is ranked 6th while Markdown is ranked 10th. The most important reason people chose enduro.js is:
No clutter and useless features.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Human-readable
Designed to be easy for a human to enter with a simple text editor, and easy to read in its raw form.
Pro Widely used
Markdown is quickly becoming the writing standard for academics, scientists, writers, and many more. Websites like GitHub and reddit use Markdown to style their comments.
Pro De facto standard
Markdown is ubiquitous. It's supported by nearly everything. The markup available in the common subset of all the many dialects isn't that rich, but it's usually enough to get the job done.
Pro Multi-directional
You can convert HTML to Markdown or Markdown to HTML. You can use tools like pandoc to convert to other formats as well.
Pro Revision friendly
It is easy to track changes for markdown documents as compared to other formats like doc, html, etc. You only need to place your markdown documents under some version control system.
Pro Minimalistic
No clutter and useless features.
Pro Beautiful admin panel
Clients are always amazed how smooth and good looking the admin interface is.
Pro Productive
Currently, probably the most productive CMS around. There is almost no setup, admin is auto generated, 100% development in code editing, shared backend/front end templates, and shared javascript code.
Cons
Con Lacks a coherent standard
Lacks a coherent standard, just many semi-compatible dialects (MultiMarkdown, etc). This inconsistency can cause problems if the person writing the Markdown is using a different dialect from the one that will be used to render it.
Con Bad support for table
It has poor support for table, while table is an important part of article.
Con Bad support for larger documents
Works good for single file documents like READMEs.
Lack support for cross-references, TOCs, document index etc.
Con It doesn't support semantic markup
It's unstructured.
Con Hardly any github commits since fall '16
Con No support for databases
Con Community size
The community around the project looks quite small. Anyone to confirm my thought ?
