Another good static site generator is http://webby.rubyforge.org
It features support for LaTex, markdown, textile filters, autobuild, publishing only changed pages etc. Very small and clean.
'gem install webby' is all needed to get you started.
It features support for LaTex, markdown, textile filters, autobuild, publishing only changed pages etc. Very small and clean.
'gem install webby' is all needed to get you started.
I'm all for people scratching an itch and rolling their own, but I'm curious why Webby wasn't suitable for the task.
In fact, this:
http://github.com/mojombo/tpw/tree/master/index.html
looks exactly like what Webby does.
When I see people sort-of reinvent a wheel or two I wonder what the reason was.
Out of curiosity, did you consider forking Webby, or offering to add in the parts you wanted back to the Webby project? Is it easier to grab the ideas you like and start fresh on your own than to try to hack on someone else's existing code?
For myself, when I find myself writing something similar to an existing project, it tends to be because a) I wasn't quite aware of what the other project offered, b) (more often) the 80/80 rule kicks in: The existing code gives me 80% of what I want, but I'll be spending 80% of my development time trying to get the rest of what I need, and writing my own version looks to be more efficient in the long run. This is more so if I expect to be reusing that code for many projects, so I can readily see the motivation in creating your own blogging software if you plan on using the hell out of it, regardless of what existing tools do.