2 ms·
To me, the overriding advantage of the static blog is that it forces simplicity upon you...it distills the site to the simplest form of "web log": if you are on
by danso 12y ago
To me, the overriding advantage of the static blog is that it forces simplicity upon you...it distills the site to the simplest form of "web log": if you are one person, wanting to write a series of chronologically ordered posts, then you don't need a database (hence, something like WordPress).
I've rarely found this kind of simplicity to be stifling. For the first 1,000 posts, you can compose and edit in plaintext with minimal difficulty in "envisioning" the post, as you might in a rich text editor. Even better, you don't have to deal with the eccentricities and inefficiencies of RTEs...and if your blog is on a focused topic, where you find yourself re-wording terminology and grepping frequently...it's a simple Ctrl-F in Sublime Text.
Even the HTML and CSS parts are simplified, since you only have to worry about the elements needed to keep a post in single layout (and maybe a sidebar column)...and editing CSS in your editor of choice is far less cumbersome than the out-of-the-box way of WordPress.
The static blog generator (at least Jekyll and Middleman on the Ruby side) then does all the clunk that would be tedious if you were to just upload plaintext to the web: namely, the ordering, timestamping, and internal-linking of the posts, as well as categories/tags, and things such as SASS compilation...and then it's just a CLI-task to update the site on S3.
Sure, after a 1000 posts...you'll see the need for a CMS to better organize and package things (not to mention the ability to update a post without regenerating the entire site)...but that's a long ways off for most would-be bloggers. And if you need to convert to non-static, well, all the metadata that was used in static-generation is easy to parse and import into any blog system.
On a day to day, or week-to-week basis, though, I find that it's the small things that can make a difference...the thought of logging into my old WordPress blog, waiting for my Dreamhost shared hosting to take 1-2min to load up the post-editor page, and then copy-pasting from where I wrote my drafts into the rich-text-editor and hoping nothing got kludged...that's enough to make me not blog...which means I might only blog when I really, really care...and if you only write when you "really, really care", you're just not going to be writing enough to be someone who can do it consistently well.