weblog.masukomi.org - blogging

Static vs. Dynamic Blogging

2015-10-18T00:00:00+00:00

You’ve got a lot of software options when setting up a blog. Over the years. I’ve used or tried most of the options including, but not limited to: WordPress, Jekyll, Octopress, and at least 3 custom built systems.

What follows is my thinking on the pros and cons of each option, and why I’m switching back to a static blog system (Hugo this time).

Dynamic Blogs (WordPress, etc.)

Dynamic blogs, like WP, have a lot going for them:

Easy to use
Lots of plugins
Great media handling
Usable from any internet connected device with a browser.
Great selection of themes
Instant publishing
Scheduled posts
Multiple Authors

So, what’s the downside? It seems like every few months one of our WordPress blogs gets hacked and Google starts warning folks it has malware. You have to constantly log in to update it, and every time you do you run the risk of hosing your database (admittedly a rare occurrence), or breaking compatibility with one of your plugins (happened a few times to us).

Another big downside is when you do happen to write something popular, and thousands of people try hitting your site at once. Many a WordPress (and similar) blog has gone down under the strain of success.

Squarespace would be an excellent option except for the $8+ per month, per site price tag. $24 if you want to be able to actually modify the HTML, CSS, or JavaScript. Maybe, if you only have one, but I manage 11+.

Static Blogs

There are notably good things about static blogs:

The fastest possible page loads.
Can withstand crazy high request loads
Zero maintenance or security worries.
Minimal hosting requirements
Markdown support
- you may not care, but I demand it of a blogging platform.

There are a number of downsides though:

Can only blog from home computer (without bullshit hoop jumping)
- Prose is the only decent exception I know of. Tinypress may be an option too, but they’re too new to say.
Multistep publishing
- run build script
- sync files over scp / rsync / ftp / whatever.
Generally weak media support
- no auto-resizing
- no media players
- have to think about where the images live
- very limited selection of plugins (if any)
Typically poor selection of themes
Limited layout capabilities
- they all use markdown, and Markdown can only produce a restricted subset of HTML.
Slow site generation
- Hugo is the only exception I’ve seen to this rule.
Metadata gets mixed in with posts instead of stored in a separate database
- All static blogs seem to use Jekyll idea of Front Matter embeded at the top of your post.
Multi-author sites require either human organization or hacking. It’s not really supported well out of the box.
Geeky
- Very few of the static blog options seem particularly usable by the non-geeks out there.

Note

Being a geek, I’ve got some advantages. When I used Jekyll I wrote JekyllMail which lets you create blog posts via email. It even handles attached images. I could do that for any other platform too. That addresses what’s probably the biggest downside to static blogs. Again, using Prose would too, but that’d tie me to Jekyll on the back end, and I just wasn’t thrilled with it.

Why’d I Choose Static?

With so few upsides, and so many downsides, a dynamic blog would seem the obvious choice. So why would I switch back to a static blog?

At this point I require any dynamic system to also be a managed system (like Squarespace) that doesn’t cost a boatload of money to run a bunch of sites on. Also, I need to actually like the software. Ghost is a decent, and relatively affordable option but I’ve had problems with their import, and I’m not thrilled with the software.

Medium and Svbtle both have their proponents, but posting there doesn’t contribute to your success or credentials. It contributes to their’s.

Static blogs give me a few big things:

The ability to stop compensating for or worrying about hackers
The confidence my site will stay up when I post something popular
The ability to customize the look and feel
Unlimited blog sites for zero additional dollars.
- I just pay a monthly fee for hosting space with as many domains as I want.
- Or do it totally free by using GitHub pages…

Also, and I realize this is totally illogical, building a site with a static blog gives me a feeling of having actually been a part of it’s creation.

So, for now I’m using Hugo. I’m going to have to start converting my other blogs over because they’ve been hacked again. I just need to find a way to enable my wife to easily post to our shared blog at CorporateRunaways.

Want to debate this? Think I missed something? Hit me up on Twitter.

Blog post dates: Precision, or freshness. What's important?

2012-08-24T00:00:00+00:00

Not too long ago I sent out a question. I asked people when, and why, dates were important to them on blog posts. The responses were revealing, both for what they did, and did not contain.

There are some situations where having a date on your blog posts is obviously needed. If you write about anything techy you absolutely need them. I come across tons of sites with perfectly good code examples, that have been obsolete for years. Ditto for how-to’s related to software and operating systems. The other place where dates are critical is anything related to news or politics.

Basically, if you’ve written something that will be used as research material later on, you need a date. Everyone seems to agree on that. But, what about pieces where the passage of time really doesn’t have much of an effect. For example, I wrote a post about a paper-based task management system. Read it today, read it two years from today… it doesn’t impact the usefulness or relevancy of the content at all. And that was the basis of my questioning. If you had a blog filled with posts like that, would there be any real value in including dates on the post?

The responses were overwhelmingly “YES”, but not for the reasons I’d expected.

Freshness and Precision

While they used different words, everyone was in agreement that an indication of freshness was very important to them. Sometimes, it was just to help them know if the blog had been abandoned or not. More often, it was simply to know if the information in the posts was still relevant or not.

What was interesting, was that when pressed for details, almost everyone claimed that a simple freshness indicator (e.g. “three months ago”) wasn’t sufficient. They claimed that they needed to-the-day precision. They claimed that having this level of precision allowed them to compare it to what was happening in their lives at the time; they could look compare the date to their calendar, and see what they were doing then.

These claims seemed… suspect to me. They felt like the type of answers people give when they’re trying to explain something they’ve accepted as true, or necessary, but have never actually thought about. Like, the idea that going out in the cold will lead to catching a cold.* So, I pressed for details. I wanted someone to give me a real world situation when they would look at a date on a blog post and actually do what they claimed. When would they ever compare the date of one to what was going on in their lives at that time, or to what was going on in the world at large at that point. The response, was a resounding silence.

Conclusions

As far as I can tell, if you exclude the types of posts where dates are obviously required (news, politics, content that will become obsolete) no-one actually needs dates with any real specificity, but because everyone believes they need them, their absence makes them uncomfortable, or at the very least, slightly annoyed.

I believe that relative dates are a much closer match to what people need, and much easier to actually use. “Three months ago” translates quickly to “recent, but not too recent”, whereas 5/24/12 requires you to figure out what month 5 is (“let’s see that’s…May”), compare the day of that month (24) to the day of the current month (“Are they the same? Is that one earlier in the month than this one? Does that make it more time or less, and is that enough to bother worrying about?”) before you can actually leverage the information in a meaningful way. But, what we need, and what makes sense logically, isn’t always what we want.

I believe that Kirk’s proposal of “mid-June 2011” is probably the best compromise between usability and need. It’s easier for a human to parse than 6/15/11. It feels much more useful than “over a year ago” or “15 months ago”, even though once you get that far from a dates post your true need for even to-the-month specificity is doubtful.

With that said, the more recent something is, the more precision seems to matter to people. So, you could probably improve on Kirk’s suggestion by a building a system where dates are written with to-the-day specificity for one month, and then switching to “early May 2012” style dates after that.

Closing Thoughts

When pondering dates in blogging, context is everything, and many, if not most, blogs have posts from multiple contexts. Hardly anyone writes a blog where the value of each post is unaffected by time. With that in mind, a blog’s posts should be dated using a method that supplies the maximum level of precision required. If you write a blog of fictional stories, but occasionally comment on news that affects writers you need to-the-day precision, either that, or use a different level of precision on every post, but really, no-one wants to go through that much trouble.

* As it so happens, it’s probable that being exposed to the cold for a while will increase your odds of catching one. Some scientists did an experiment where they had some college students stand in buckets of cold water for a while, and compared which of them got colds soon afterwards. The kids who stood in the cold water got more colds than the kids who didn’t. I just wish I could find the research again…