[BangPypers] Dynamic Markdown & Textile Blog/content app
kracethekingmaker at gmail.com
Wed Dec 12 19:52:10 CET 2012
On Thu, Dec 13, 2012 at 12:16 AM, Arun Ravindran <arunvr at 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.
This is based on convention. under theme directory place static/*.js,
*.css, *.jpg, *.png, and templates/*.html .
It is some much similar to Flask.
> 2. Template system was a tad too complex.
> Pelican doesn't have own templating system, it uses Jinja2.
> Overall, pelican has some good ideas and is being actively developed. But
> it is not really suitable for a power user.
> On Tue, Dec 11, 2012 at 9:24 AM, Gopalakrishnan Subramani <
> gopalakrishnan.subramani at gmail.com> wrote:
> > I am curious about a blog application (currently rolling out 0.0.1, I
> > 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 at python.org
> > http://mail.python.org/mailman/listinfo/bangpypers
> BangPypers mailing list
> BangPypers at python.org
Thanks & Regards
"Talk is cheap, show me the code" -- Linus Torvalds
More information about the BangPypers