This repository was archived by the owner on Jun 18, 2024. It is now read-only.
Use kramdown as the markdown engine #120
Merged
Conversation
This file contains hidden or 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
Conflicts: schema.md
haleyvandyck
pushed a commit
that referenced
this pull request
Aug 16, 2013
Use kramdown as the markdown engine
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Maruku's the default Kramdown engine that 🚢s with Jekyll, but there are better ones out there that are much less error prone and can hopefully avoid headaches like the one @haleyvandyck experienced recently on #118.
This pull request asks GitHub to use Kramdown to process Markdown instead. Kramdown's about 5x faster than MaruKu, and is 500x times less finicky. Kramdown's interpretation of markdown is almost identical to MaruKu's which is why it's a good choice to move to over say something like RedCarpet.
There were a few slight syntax changes, but as far as I know, everything should look exactly as it did before. Can anyone confirm that?
Anyone have any strong opinions? @parkr?