Search results

Experimenting with a shorter post style

by Tom Johnson on Sep 26, 2015
categories: blogging

I'm going to focus on writing more pages than posts. Given how few people use RSS, the distinction between pages and posts is becoming trivial. It makes more sense to focus my efforts on a more substantial format.

I’m thinking about leaning toward a shorter style for blog posts. Lately I’ve been focusing a lot of energy on developing an API documentation course, so although it may not appear as if I’m posting as much, I’m actually writing quite a bit here.

The difference between posts and pages on a blog is becoming less important. Posts appear in an RSS feed and are intended as diary-like entries that live on the homepage a few weeks before sliding into oblivion. In contrast, pages are intended to be more permanent.

However, almost no one gets their news via RSS anymore. If I don’t send out links to new posts via Twitter, Linkedin, and my email newsletter, the number of reads plummets. So what’s really the benefit of writing posts instead of pages, if you can promote both the same way?

In other words, what’s really the difference between writing a page and promoting it via these channels, versus writing a post and promoting through the same channels? It’s not as if the content’s absence from RSS feeds affects the readership in a significant way.

Instead of writing one-off posts, I’d like to build something bigger and more cohesive. My goal is to create a course in API documentation and publish it on an online learning platform. It’s going to take me a few more months to finish it, but I like the idea of building something larger rather than just writing standalone blog posts.

The half-life of blog posts keeps getting shorter the more real-time news dominates the web landscape, so it only makes sense to put energy into more substantial formats.

About Tom Johnson

Tom Johnson

I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.

If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.