Re: let's talk about pyblosxom's future

> Hi!
>
> I've taken a 6 month hiatus. Two things have happened in that time:
>
> 1. I picked up other projects.
> 2. I didn't really miss working on pyblosxom.

Hi Will,

1) it's sad to see pyblsoxom go
2) I can understand you quite well.


I have toyed quite intensively with pyblsoxom for a while and while I like
the coding style and it's workings, it's age shows. There are very nice
templating engines out there, which make many things easier and it was not
easy to make use of those engines without basically breaking all plugins
and rewriting much...


Shameless plug for a project that is not mine:
I have to say that I defected from pyblosxom, and use "volt" now, which is
a very you project using a nice templating engine, and is plugin based
too.

It takes plaintext, markdown, rst (or whatever you write a parser for),
and creates static html pages using the jinja2 engine. It ncludes atom
feed and monthly/yearly archives and tag-based index pages. It's extremly
configurable and it was not too hard to convert my pyblosxom posts into
the format that volt needed. I am not involved with the project, but it's
a cool one. If you want to see volt output in action, have a look at my
blog at http://sspaeth.de

Sebastian


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/