-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
Default Markdown template parser for new sites to RedCarpet #1245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ig.yml. Related: #1236.
@mattr- 😄 |
Now I rule all the blogs!. 💥 😉 |
Hey @parkr before we merge this can I also suggest that we update the documentation to mention the fact that the default for new is now RedCarpet? |
Default Markdown template parser for new sites to RedCarpet
Annnnddddddd it's merged LOL |
@mattr-'s on a plane. He might not have gotten that :) The default for all Jekyll sites will still be MaRuKu. |
Uno momento, por favor On Thu, Jun 27, 2013 at 12:28 PM, Parker Moore notifications@github.comwrote:
|
Right, but shouldn't we explain that the site template when you use jekyll new will use a completely different pre-processor? Seems like we could just mention it in the quick-start as one of our nice info boxes :) |
We should probably also install redcarpet by default since new sites won't On Thu, Jun 27, 2013 at 12:32 PM, Zach notifications@github.com wrote:
|
Should Jekyll’s official site not be a role model and use Redcarpet as default markdown engine? Dogfooding is convincing. |
We need to maintain header links, e.g. |
correct. it won't support that until 3.1. On Thu, Aug 15, 2013 at 5:26 PM, Parker Moore notifications@github.comwrote:
|
Hi friends! On http://jekyllrb.com/docs/configuration/#default_configuration, it says: Just confirming this should be Thanks! |
Nope, the programmatic default is still |
Understood! Thanks @parkr. 👍 |
Done via generated _config.yml.
Related to #1236.