Instead of adding markdown support to the editor, which seems to be what the problem is, why not just make a new widget - MarkdownEditor, based on the normal editor code?

So has there been any update on this? It's been under review for almost 2 years now.

Hey, I have spent some time trying to implement this but to be honest I've not had the time to devote to it, as I have to work on my actual work projects. I do however want to pitch more compelling reasons for including Markdown in the Kendo Editor.

First, one of your major competitors, ComponentOne (producers of Wijmo) don't have Markdown in their Editor. That's simple business logic there. I'm not saying that every feature they don't have is one you absolutely have to have, but it sure doesn't lessen the appeal.

Second, Markdown is a beautifully verbose way of storing text. And right now, the web is pretty abuzz with things that strive to be lightweight and extremely low-footprint. I've never seen a situation in which WYSIWYG HTML is easy to store. It always requires extra work, extra validation, extra processing, and no matter how good the implementation ... it is still WYSIWYG HTML. I think every one of us that has actually touched the internet in the last 20 years knows how that inevitably ends up, no matter how well it is done. (I will be the first to admit, however, that the kendoEditor is the VERY BEST I have ever seen it done. I used to be a customer of ComponentArt, and I thought they had a beautiful editor, but it was mostly just visual eye-candy and well thought out CSS, the functionality was very poor)

Kendo, with its ability to store raw JSON and interpret it - both client and server side, is a very good choice for Document Database Management Systems, such as RavenDB, CouchDB, MongoDB, and others. For database systems like this, Markdown is absolutely, marvelously ideal because it fits right into the entire notion of simple objects that match your models. Presently, the most work I have to do with the Kendo Editor is making sure that it stores into RavenDB without error. How much more amazing would it be if this wasn't a barrier for these new kinds of systems.

Markdown is extremely self explanatory, and as such it is pretty much almost impossible to render incorrectly. Unlike WYSIWYG HTML, Markdown's syntax is not prone to browser interpretation in the same way. It still relies on the HTML elements that it translates into, but that is an afterthought. To try and explain (which I'm sure you guys already understand, I'm just elaborating on) ... 

If you store a block of text in WYSIWYG HTML, it is stored as the HTML was parsed and recorded. The markdown is saved along with it, and if this markdown has an error, then it will always be an error until something goes in and fixes it on the actual storage side.

Inversely, Markdown is not prone to this. If Markdown is interpreted incorrectly, then it is pretty much usually just a matter of changing/fixing either the CSS, or whatever engine is interpreting Markdown as it comes down from the server. This has an added benefit of more client customization, more client control, less server overhead, less security risk, and higher rate of consistency between browsers. It is the primary reason I've switched to Markdown exclusively in most of my projects.

There are features of the Editor that are not compatible with Markdown as it stands (font colors, for one. And fonts in general) but that is part of what makes it so incredible for Kendo. It's a great beacon of how robust the whole model is, because it's so simple to only include the editor features that ARE compatible in naught but a line of code, it's a really good presentation model for end users to see.

I will continue to try and see if I can create a working implementation, but I don't have a lot of free time between my other work.

Hey, I'm just following up again. You said that you would be evaluating this in Q3, but I was wondering if you can list anything that we, as your customers, can do to help out. Would you be more amicable to the idea if we were to show you some demos of ad-hoc implementation using more hacky methods, and how cool it would look if done? Would you be more satisfied by some finicky forking of the kendo core github that tries to implement it? I'm not sure if I can do the latter, but I can offer you some data..

markdown is presently taking the entire world by a storm because, to a programmer, it is one of the most friendly ways of holding and storing data. It is true that markdown sacrifices certain amount of formatting in exchange for its simplicity, but if this is truly an option the developer makes, that is okay.

New database systems like Raven, that use NoSQL storage, are becoming very popular. And then RDBMS ORMs like Entity Framework are cropping up everywhere. With that comes increasing pressure to store large amounts of text. Storing HTML works, as we've seen for years, but storing markdown works much, much better. 

markdown removes a lot of the security implications that HTML storage has. It is also much slimmer and is not prone to as much misinterpretation or browser-error. Because all of the information is plain text, it is literally next to impossible for markdown to be misinterpreted unless the developer specifically tries to intervene with its conversion.

I will definitely work on an ad-hoc implementation. But I'm not good enough to really do it, or I would just do it myself in the first place.

Just chiming in on this again, has there been any update on the opinion of this? We just got a new kendo release, so I know it won't be soon. Is there anything the community can do to try and motivate this? Would a demonstration of an ad-hoc implementation be helpful? I would be willing to try it if it would mean the prospect was looked at a bit more. This is literally the __only__ feature kendo doesn't have that I desperately want. It is the only thing I have to keep using third party libraries for.

I am really hoping this gets more consideration soon. This is literally the ONLY feature Kendo is missing to be COMPLETELY full featured and absolutely dominate every other competition on the market. The entire suite is just so masterful in every single way ... the lack of Markdown support is just like, the only thing I want anymore. We're storing data in RavenDB, so we like to keep strings as simple as possible, and Markdown is very lending to that. Wish I could upvote this more!!!!

Wow, that would be great. The HTML editor is good, but HTML is so cumbersome to serialize and store in an efficient way. Markdown syntax would make this complete, as the editor is about the only component on my site I still have to use a non-kendo variant of. Thanks for listening!

This has changed to "Under Review"; does this mean that there is a (slim) chance we'll actually be seeing this feature?

Would really like this too! 

I agree, this would be a nice add, and presumably not very difficult.