Improve product scope, purpose, and vision

[joshbruce]

Over the years marked has expanded in its scope related to features, capabilities, and so on. In preparation for the 1.0 release of Marked, we would like to make it more clear what marked is, is not, and where it is going.

Features to add??

• Have lexer generate objects for parsing by extenders
• Add an option to not escape quotes
• Add direction property to syntax tree and generated HTML Add direction property to syntax tree and generated HTML? #694
• Improve support for scroll syncing by editor vendors about scroll sync #691
• Override the way that plain text is rendered Possible to override the text renderer? #581
• Consider the support of macros Consider the support of macros. #445 some macro support #466
• Allow json output instead of a string Add option to allow json output instead of a string #588
• Render only parts of the Markdown syntax Option to render only parts of the Markdown syntax #571
• Better support for UTF-8 and international characters German umlauts break conversion #561 UTF-8-BOM not supported #1133

Features to deprecate??

• Header IDs
• Drop support for the Daring Fireball Perl specification

See also:

• [Vision alignment]: Comparative benchmarking - high-speed #963
• [Vision alignment]: Comparative benchmarking - lightweight #964
• [Vision alignment]: Comparative benchmarking - low-level #965

[UziTech]

This has become out of date