3 ms·
I can see the use case you're going for. As others have mentioned though, this value is not coming as an alternative to markdown but rather an enhancement to HT
by ukulele 9y ago
I can see the use case you're going for. As others have mentioned though, this value is not coming as an alternative to markdown but rather an enhancement to HTML in a different use case.
Feels kind of like Sundown:HTML::SCSS:CSS. If you can communicate this (vs being an improvement on markdown), you'll probably get people to take a closer look.
- ne01 9y agoYou are right. Thank you for the insight! How about this: Sundown and Markdown are both HTML preprocessors with different goals.
- roywiggins 9y agoNot all markdown processors implement inline HTML, which I learned to my detriment recently (the "markdown" package on npm doesn't).
- ne01 9y agoExactly. Most Markdown processors don't implement this feature because it is very unpredictable and has too many contradictory edge cases.
- pyre 9y ago... which makes Markdown even _less_ like your software. Also less relevant to marketing efforts as people up-thread are saying. Some of the use-cases that you're covering with your software were never covered by Markdown, nor were they ever intended to be use-cases for Markdown. So you're not going to find people that are currently using Markdown that will need Sundown for those use-cases.
- ukulele 9y agoHonestly I see no reason to even mention markdown. Sundown really has nothing to do with it. Just state why it's an improvement over HTML in various scenarios.