Added ts-markdown to readme #81
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t it in alphabetical order.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Project URL
https://github.com/kgar/ts-markdown
Category
Tools > Converters
Description
An extensible TypeScript markdown generator that takes JSON and creates a markdown document. It's brand new!
Why it should be included to
awesome-markdown(optional)ts-markdown fills a niche for markdown generation that helps with those who are taking JSON data and generating markdown documents. It takes away the headache of trying to make a good markdown document and only requires someone to make JSON objects. Also, because it's written in TypeScript and provides typings directly in the npm package, it boosts the productivity of any TypeScript application that needs to generate markdown from data.
I am the author of ts-markdown, and I made it so that I could focus on making markdown files for my Obsidian vaults in another project, but I didn't want to deal with the added complexity of trying to render nested, complex markdown on the fly.
Checklist