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.
I am using Jinja2 as well. Lets see how this come up. Thanks for sharing them. On Thu, Dec 13, 2012 at 12:16 AM, Arun Ravindran <aru...@gmail.com> 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 have pictures stored inside the > blog subdirectory, it has to be moved out to a common place. Another common > place must be defined for blog posts. > 2. Template system was a tad too complex. > > Overall, pelican has some good ideas and is being actively developed. But > it is not really suitable for a power user. > > Regards, > Arun > > > On Tue, Dec 11, 2012 at 9:24 AM, Gopalakrishnan Subramani < > gopalakrishnan.subram...@gmail.com> wrote: > > > 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, search keywords, title, author etc) > > 4. Markdown, Textile for content. > > 5. Import a python file into blog post with path (without coping the > > content into post), render via pygments and raw view > > 6. Whoosh search (that is text too) > > 7. Ability to link internal posts easily [markdown already does this > > neatly, need to check textile] > > 8. Syncing with Mercurial and Git > > 9. Create/edit post dynamically through web app using web based markdown > > WYSWYG editors, later sync with git, hg > > 10. Basic minimal templates > > 11. Plug-ins in Jinja2, Python > > 12. Support multiple authors, from different gits, hg repositories or on > > site posts > > > > This is not static html generator, the app will be serving content > > dynamically, whatever WSGI based server. > > > > Anybody using pelican or other text based blogs share some insights here? > > This is a fun project, contributors welcome. > > > > Thank you. > > > > Gopalakrishnan > > _______________________________________________ > > BangPypers mailing list > > BangPypers@python.org > > http://mail.python.org/mailman/listinfo/bangpypers > > > _______________________________________________ > BangPypers mailing list > BangPypers@python.org > http://mail.python.org/mailman/listinfo/bangpypers > _______________________________________________ BangPypers mailing list BangPypers@python.org http://mail.python.org/mailman/listinfo/bangpypers
