The long road to building a static blog with pelican

In this post it is documented how this blog was constructed as a static site, meaning, the webpages are served from storage and not generated dynamically upon each visit using scripts (written for example in php) and databases (e. g., MySQL).


Why a static site?


The obvious and ubiquitous software choice for blogging is wordpress, a dynamic engine, which IMHO, is in several ways superior to other dynamic blogging services such as Google Blogger, Livejournal, Tumblr, etc., if nothing else for control of content.

It would have been natural to stop there and take that route. However in a more insidious manifestation of technophilia, a static blog was decided upon. There are many reasons, which all basically comes down to simplicity, control, cost savings, and, because I can do it.

The environment issue

In wordpress, everything is web-based, and the content storage, database and scripts are all intermixed. Editing must take place in the wordpress editor or in custom html/javascript/css/php. This is all too much detail for the writer to be bothered about, if s/he wants any degree of customization. Once the design is fixed, s/he should be able to focus on the content without any distractions, and if design is to be changed, it should be doable without disturbing the content files.
Read more ...


© 2015 George S. of www.notionsandnotes.org.