Technology Tales

On Blogrolling.com

I was ambling around the web and came across a website that, while it appeared to be a blog, isn't one in the vein of that to which we are accustomed. It does, however, have a blogroll and that is where Blogrolling.com comes into this piece. Blogrolls are very much a feature of the blogging (WordPress calls them that anyway) world and act as a repository of useful links relevant to the subject of the blog. I also use them as a bookmarking station for myself and a way to return the favour when someone links to my blog. For a blogroll, you generally need a database sitting behind in the background, or you end up creating a list of links in (X)HTML.

Blogrolling.com offers another option: placing your links at an external website and including them on your webpages, using a piece of code to pull in the information. RSS, JavaScript and PHP are among the methods on offer from Blogrolling.com; I used PHP when I gave the service a whirl on one of my offline blogs and that really does give you a lot of customising power over and above using CSS. That's not to say that there aren't customisation functions on offer from Blogrolling.com, I found a few of these distinctly useful: ordering of links in a blogroll is just one. When it comes to categorising your links, you don't get the category option, but you do get to create as many blogrolls as you want, so there is a workaround; moving links from one blogroll to another is mouse intensive but straightforward. Also, because you are reading each blogroll in turn, you can order the categories as you want them. With WordPress' category approach, ordering categories involves widgets and plugins or getting your hands dirty with some code cutting. All in all, Blogrolling.com seems to offer an intriguing and useful service.

Twelve months of WordPress

It was on this date several months ago that I moved my hillwalking blog into the world of WordPress. It's a self-hosted WordPress instance and has been for all that time. Because of the move, I was taken into the world of MySQL, one that intrudes still to this day. Most of the time for the migration was spent setting up a theme to fit in with the rest of the website, of which it forms an essential part. The matter of importing all the old posts took up time too, especially when it came to fixing glitches with the XML import. Still, it was all done within a weekend, and my website hasn't looked back since. More people now have a reason to visit, and the blog may even have surpassed the photo gallery as the site's main attraction. I kept up the old blog for a while but have dispensed with that by now; I was keeping both blogs synchronised and that became a tiring manoeuvre. Another upshot of the whole experience is that I have become more aware of the UK outdoor scene and learnt a thing or two too. It might even have encouraged me to go from day tripping to multi-day backpacking, a real-world change that is well removed from the world of technology.

Another side to hardening WordPress

A little while back, I took to using the wonders of .htaccess directives to make my WordPress deployments more secure. It does work but has the disadvantage that desktop blog editors like Windows Live Writer, Word 2007 and w.bloggar cannot be used to update your blog. Though I must have a look at getting around this, I am sticking with using WordPress itself to do the editing for now (Dean Lee's port of FckEditor for WordPress is working out very well, spurious codes notwithstanding).

My type of blogging

A recent article by Lorelle VanFossen on The Blog Herald got me thinking about my blogging journey and what I have learned about myself. My brush with reactive blogging has taught a number of lessons. The first of these is that I just cannot keep up with others; someone always gets there first. Another lesson is that taking on a topic of the day takes up loads of time when it lies outside my area of expertise, and I spend a lot of that time researching the topic. What follows from this is that if the post doesn't flow from me, it either takes up a lot of time or it doesn't happen at all. Yes, I have been known to bin stillborn posts due to loss of interest or where things just wouldn't come together at all.

Following all of this, I have come to the conclusion that I am a proactive blogger. That said, I still need to get some bursts of inspiration from somewhere. For instance, my hillwalking blog always experiences a burst of activity after I have been trekking in the outdoors; such encounters never fail to produce something that is worth sharing. In the same vein, anything you find here is likely to influenced by what I have encountered in the technology world. Yes, news items do provide ideas for posts, but it is in a more leisurely way rather than the frenzied approach of some. And like the hillwalking world, such inspiration does have its peaks and troughs.

A feast of plugins

Themed Login

Here's a useful idea: get your blog login page to look like it's part of your blog. It does work well on my hillwalking blog, but you do have to watch how it behaves with whatever theme you are using. Strangely, I couldn't make it work on my offline blog, the development mirror of what you see online. The ability to set what page is displayed after logging in or logging out is an especially useful inclusion.

My Category Order

My Link Order

My Page Order

These sound like wonderful ideas: being able to control the running order of things on your blog sidebar is a good thing. What scuppered my using them is that you need widgets turned on for the effect to work, and I have seen issues with how ID's have been set when things are widgetised.

A penchant for strange decisions?

WordPress.com has retired its Feed Stats feature. While there might have been problems with it for some, I do find it a strange decision not to spend some time on it. After all, given the existence of Google Reader and its kind, I wouldn't be surprised to learn that more people read blogs with RSS readers than by going to the sites themselves. In fact, I peruse blogs more often with Google Reader than by visiting the websites themselves. It's enough to make me wonder if I could use Feedburner with this blog.

To follow on from this, I am beginning to wonder if that Automattic, the people behind WordPress.com, seems to be a quirky company that makes decisions that are questioned by its customers. After all, they did remove the post preview functionality from blog post editing screens, and that has generated numerous comments. On self-hosted WordPress, you can add a plug-in to correct this, but that option is not open to WordPress.com users. The answer that I got to a theme change request earlier this year adds to the impression, as does seeing a company having staff apparently work from home all over the world.

Automattic seems an unconventional beast alright; could that lead to their undoing? Though it is king of the hill with blogging world for now, there is nothing to say that will last forever.

A case of cross-fertilisation

Having two blogs allows me to stream my content; I doubt that many visitors to my hillwalking blog would appreciate seeing posts on, for example, the minutiae of UNIX shell scripting. However, as disparate as these worlds are, there is something shared between them, and it has started to cause some cross-fertilisation between them: blogging itself. Rather than being too self-referential on my hillwalking blog and preaching to the choir, I have taken the decision to muse about blogging and its progress right here. There is also some escape in the opposite direction too: technology does get used on the hill too. Examples include GPS receivers and digital mapping, and my hillwalking blog is definitely the place for them. It is all very much audience-driven; this consideration of content is the sort of thing on which a posting on The Blog Herald has been musing.

Do we surf the web less at the weekend?

Are developers and designers overcomplicating their CSS?

When I have been tweaking the widgets in this blog, the thought crossed my mind that purveyors of open source blogging and CMS's may be overcomplicating matters with the CSS that they are writing. Using inheritance without much thought as to others having to pick it up is one irritation, but bunching styles together can confuse too. For instance, you can draw from two different styles for the same HTML element (it's what's going when you see class="class1 class2" in a tag definition), which is OK if done simply but can confuse matters when customisation is attempted later. Drupal particularly suffers from this bugbear, but it's there on WordPress too, though not to the same extent. Using a hierarchy to define and attach your styles (#id1 .class2 tag1 {style definition...} is the kind of thing that I have in mind), can also confound, even if I admit to finding the approach very useful for myself. I think that I know what's driving this: the need to cut down the bulk of CSS files but using the advanced features that I mentioned above without clear commenting and other documentation hampers later efforts. It would be nice if every developer of a theme to use in blogging or CMS software was forced to document their work extensively and share that documentation with interested users. After all, sharing is the whole purpose of their endeavours...

Outdoors enthuasiasts blogging in the U.K.