As an open source “Plone guy”, I’m always prepared to defend and explain my choice to not use Plone for blogging.
As an open source “Plone guy”, I’m always prepared to defend and explain my choice to not use Plone for blogging. A couple years ago, I started using Wordpress in order to learn its feature set. I enjoyed my time with it, but after moving to wordpress.com for “trouble free” hosting, I found I couldn’t control my category feeds the way I wanted; the honeymoon was over.
This was a giant let down, because I was hoping to avoid putting any time in to my blogging infrastructure. For weeks I did nothing. I poked at various options: Pelican, Plone, Tumblr, others. Eventually, I found my way back to Pelican and now I’m happy again.
Pelican is a static blog generator, as you may have heard. So one big advantage is:
If you are curious about my setup, here are the details.
Getting started with Pelican was easy, basically:
$ virtualenv . $ bin/pip install pelican BeautifulSoup Markdown $ bin/pelican-quickstart
At this point, after I answer the quickstart questions I:
$ source bin/activate $ make html
Now the content is ready to host (which for me just involves a git push).
A few things were tricky.
Now I write articles in restructured text in the content/ directory and publish them like so:
$ make publish; git commit -a -m "Publish"; git push
All the details are here if you’d like to take a look:
Comments from more knowledgable Pelican users welcome. Like this article? Tip me on Gittip!
|||This is actually my first “test” post with Pelican so I will get a chance to see how the feeds perform. But they looked good in testing.|
|||I think I broke “make html”, actually. Primarily I just needed to make it not “clean” the entire repo.|