Skip to content
This repository has been archived by the owner on Apr 17, 2020. It is now read-only.

Look at different ways of fenced blocks #21

Open
kizu opened this issue Apr 18, 2013 · 4 comments
Open

Look at different ways of fenced blocks #21

kizu opened this issue Apr 18, 2013 · 4 comments

Comments

@kizu
Copy link
Member

kizu commented Apr 18, 2013

Could I convert blocks that are not supported right now to proper code?

Right now the version at Pages don't understand ~~~ sql type of fenced blocks :(

And kramdown don't know about ``` also.

@audreyt
Copy link

audreyt commented Apr 30, 2013

+1 for this; compare http://www.audreyt.org/newdict/jekyller/_public/ vs http://audreyt.github.io/jekyller/ for a real-world example.

I wonder if it's easiest to allow the ``` syntax, and pre-process it into ~~~ if the engine is kramdown?

BTW, the presentation above was very well received, and thx so much for Jekyller -- it cured my Keynote.app habit since 2006. :-)

@kizu
Copy link
Member Author

kizu commented May 1, 2013

Yep, I think I'll try to render the kramdown right from the jekyll, however I'm now sure if the pygments would work in this case.

@kizu
Copy link
Member Author

kizu commented May 1, 2013

Also, good to see Jekyller to be used for an actual presentation! :)

@audreyt
Copy link

audreyt commented May 1, 2013

I'm very happy with it so far. :-)

I think it's fine to make pygments optional, as GitHub Pages may not have CodeRay installed (very happy to be corrected if it does). A locally-rendered Jekyller can receive syntax highlighting, while a github.io one at least gets the formatting correct.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants