I am curious about a blog application (currently rolling out 0.0.1, I will
put on github soon), like pelican but little differences.
1. Pages are dynamic
2. Flask, Jinja2 as development platform
3. Yaml, Json and Pelican style headers for the meta information (that
covers category, tags etc, sea
I was checking out Pelican and seriously started converting my Jekyll based
site but disliked many aspects of it:
1. Too much magic - The site structure is completely changed by Pelican in
the generated output. For example if you have pictures stored inside the
blog subdirectory, it has to be move
On Thu, Dec 13, 2012 at 12:16 AM, Arun Ravindran wrote:
> I was checking out Pelican and seriously started converting my Jekyll based
> site but disliked many aspects of it:
>
> 1. Too much magic - The site structure is completely changed by Pelican in
> the generated output. For example if you h
On Thu, Dec 13, 2012 at 12:22 AM, kracekumar ramaraju <
kracethekingma...@gmail.com> wrote:
> On Thu, Dec 13, 2012 at 12:16 AM, Arun Ravindran wrote:
>
> > I was checking out Pelican and seriously started converting my Jekyll
> based
> > site but disliked many aspects of it:
> >
> > 1. Too much m
Jinja2 is much easier than mako template. pelican is kind of opinionated
and conventional engine as said by Kracekumar that assume you do the things
on its own way. I will see how I can overcome with image attributes as per
me, it will be served from url, could be relative to server or absolute url
