Set Jinja layout & block-to-extend in config.yaml (support plain markdown pages)

colinta / StrangeCase

It's yet another static site generator. Have you seen jekyll? hyde? Yup. Like those.

http://colinta.com/projects/StrangeCase.html

Other

49 stars 7 forks source link

Set Jinja layout & block-to-extend in config.yaml (support plain markdown pages) #49

Closed edbrannin closed 5 years ago

edbrannin commented 11 years ago

It would be nice if I could have a folder of Markdown files that all get parsed with the same layout, like some blog-style SSGs.

Perhaps this is a thing I should make a plugin for on my site?

colinta commented 11 years ago

I've looked into this myself, but got held up at the part where I would hand Jinja some block content... they have excellent documentation on using jinja, but not much on the internals... :-/

edbrannin commented 11 years ago

The alternative would be to have a special kind of process where a single page's rendered contents could be slurped wholesale into a template variable, then render that template and replace the original page. I'm guessing that's not possible?

Maybe I'll look into how Blogofile does this.

edbrannin commented 11 years ago

Yes, "populate jinja context with numerous values" does seem to be how Blogofile handles this. Any way we could make page contents available in a limited scope without risking circular dependencies?