Adding and removing links from your blogroll by hand is a waste of time if you already have a ready-to-roll data source available — the blogs you’re subscribed to through Google Reader.

The following steps explain how to create a blogroll on your WordPress blog (or Blogger account), that will automatically synchronise with the blogs you’re following in Google Reader. Provided you’re happy to publicly list your Google Reader subscriptions (or, at least, a subset of them), this trick will save you a lot of hassle.

Note that the instructions that follow assume you’re using a self-hosted WordPress blog, or have a hosted Blogger account.

Grabbing code from Google Reader

1. Open Google Reader, and log in to your account.
2. Select Settings > Reader Settings, and then the Folders and Tags tab.

   Any folders you’ve already set up to hold your blog subscriptions are listed.

   

   If you aren’t already using folders in Google Reader, you’ll need to create at least one folder to hold the subscriptions that you want to link to your blogroll.

3. Select the check box next to the folder you want to use as a blogroll, then click the Change sharing drop down, and select public.

   A number of links will now be displayed to the right of the folder details.

4. Click add a blogroll to your site.

   A new window opens — the right-hand side shows a preview of how your blogroll may look when incorporated into your blog.

5. Change the Title of the blogroll if required.
6. Select a Color scheme from the drop down list.

   A preview of the scheme you’ve chosen is shown to the right.

   For maximum visual control, select None instead of a specific colour. You can then style the blogroll separately within your blog.

7. If you want to add the blogroll to a Blogger account, click the Add to Blogger button, and follow the instructions.

   If you are using a self-hosted WordPress blog, continue with the instructions below.

8. Select the HTML snippet shown in the text box, and copy it to the clipboard (CTRL+C to copy).

Adding the code to your self-hosted WordPress blog

9. Log in to your self-hosted WordPress blog, and open the Dashboard.
10. Select Widgets from the Appearance menu.
11. Find the Text widget in the Available Widgets list, and drag it into the Sidebar list on the right.
12. In the Text window that opens, paste the code that you copied from Google Reader into the large text box (CTRL+V to paste).

    You can leave the Title field blank if you already specified a title for the blogroll code in Google Reader.

13. Click Save, then Close.

That’s it! Your blogroll will now be automatically synchronised to the subscriptions in the folder you selected from Google Reader. As you add and remove subscriptions from the folder in Google Reader, these changes will appear immediately on your blogroll!

Of course, if you use multiple folders in Google Reader to organise your subscriptions, you can create a separate auto-synchronising blogroll from each folder. This is exactly what I’ve done here on WildVista, with separate blogrolls for each of the main subjects featured.

If you have some subscriptions that you don’t want to be shown on a blogroll, just keep them in a private folder (or don’t put these subscriptions in a folder at all).

Related articles by Zemanta

• How to Add Your Google Reader Feeds as a Blogroll on Your Site (anneonlife.com)

Mimbo is a free, magazine-style theme for WordPress.

I particularly like the ease with which Mimbo enables one to create graphically rich feature pages. The first photo in any post is automatically detected, resized to a thumbnail, and then inserted alongside excerpt text on the home page, and within category pages. It’s this greater use of images that’s led me to drop the original banner image (though I do miss it — might have to think of a way to work it back in…).

I’ve also tweaked the default theme a fair bit, making a number of CSS style adjustments to get things layed out as I want. This has also introduced me to a feature of WordPress that I was previously unaware of — child themes. The problem with installing a new theme, and then tweaking it to meet your needs, is that, when the theme is upgraded, all these changes will be lost.

You could simply not upgrade the theme, but this isn’t likely to be a sensible approach in the long term. As the WordPress platform itself is upgraded (often to fix security-related bugs, but also to introduce useful new features), the theme you’re using may also need upgrading if it is to continue to work correctly with the latest version of WordPress. By creating a child theme, you can make wide-ranging modifications, without having to worry about redoing this work when it’s time to upgrade the theme.

I’ve really just scratched the surface when it comes to WordPress theming, but am now happy that this approach will greatly reduce the pain of future upgrades. And with that, I’ve got a bunch of draft posts in the pipeline, ready to populate my newly streamlined categories. (Not convinced the “Atmospheric Optics” category is going to make the cut though — not unless I can create considerably more content!)

Related articles by Zemanta

• Designing WordPress Child Themes (domainmacher.com)
• WordPress Structure and Best Practices (slideshare.net)

Other changes I wanted to make fell outside the default features available from a self-hosted WordPress installation. Enter “plugins” — tools to extend the functionality of WordPress.

Two Plugins I’ve activated or added to WildVista.com are listed below, along with a link to a page where you can download the plugin, a basic explanation of what the plugin does, and why it’s useful.

• Akismet anti-spam service for comments. Pretty obvious why you’d want this really. Spam comments on blogs are rife — often disguised as ‘genuine’ comments (e.g. “Nice blog! I’ll be visiting again!”), their real purpose often being to build a network of back-links to the spammer’s site.

  Anything that can save my time by identifying spam comments automatically is worth a look. Rather than force users to complete a CAPTCHA, Aksimet attempts to automatically detect spam comments and places them in a spam folder.

  Plenty of spam has arrived already, and Aksimet has caught it all. No false-positives yet either. Askimet is a hosted service, so if you’re hosting your own WordPress blog (i.e., not on WordPress.com), you’ll need to apply for an API key (free). Even better, Aksimet is automatically installed with the main WordPress software, so you won’t need to download it separately.



The Aksimet dashboard.

• Floatbox Plus is a very well written Plugin that adds support for inline enlargement of images (at least, that’s what I’m using it for — its capabilities extend beyond this). So much nicer than jumping to a blank window with a sorry looking image jammed up in the top left corner — the default unless you do something about it.

  Floatbox Plus is smart too. If the enlarged image is bigger than the screen real-estate available to display it, a single click enlarges the image such that it just fits the screen. A further click then expands it to full size, if that happens to be bigger. Clearly, a lot of thought and effort has gone into this.

  Floatbox Plus is free to use for non-commercial sites, but still requires a license key to prevent an occasional nag message. I requested a key a while ago, but have yet to receive one. I should probably chase that up.

I’ll post again over the next few weeks, with more information about the Plugins I’m finding useful.

Related articles by Zemanta

• Top WordPress Plugins You Should be Using Right Now (socialmediatoday.com)
• What, Why, How – WordPress Plugins (blogmistress.com)

One early decision was to change WordPress’s default behaviour for displaying posts on the front page. I’ve never really got on with the enormously long lists of full posts that make up the front page of many blogs. The pages can take an age to load, and it’s hard for a new reader to get a feeling for a particular blog when they have to scroll through masses of detailed content, rather than scan a list of post titles and excerpts.

Martin (over at Postcard from Timperley) commented that he’s not keen on having to click to ‘Read more’, and this got me thinking. The result is what you’re now seeing on the front page — a hybrid approach, displaying only the most recent post in full, and then the five most recent posts as excerpts with ‘Read more’ links. I achieved this with the Homepage Excerpts plugin for WordPress, available for download from the Daily Blog Tips site. However, I think the design decision is more interesting (and more important) than the mechanics of the implementation.

You can download the Homepage Excerpts plugin from www.dailyblogtips.com

Of utmost importance with any such design decision, is to keep in mind who you’re designing for — that is, the end user (visitors to your blog); not yourself! Given that blogs and blogging entered the mainstream some 10 years ago (blogger.com went live in August 1999), the medium has developed a number of tried and trusted design patterns, most of which will become obvious to anyone that’s a regular web user with even a passing interest in blogs.

As such, the question I needed to answer, was why so many blogs have extremely long front pages consisting of full posts, and whether this common design pattern is appropriate for my own blog.

As a quick piece of research, I took a quick look at each blog on Martin’s blogroll. Of the forty or so blogs listed, only two use excerpts on the front page, with all the rest favouring full posts, and consequently have very long front pages in many cases.

Most of these fit the ‘personal journal’ style of blog, and I can see how such a chronological diary is reasonably well presented as an extended page of full posts. I remained unconvinced that a blog consisting of often unrelated posts or mini-articles on a selection of subjects (the way WildVista is likely to go), without an implicit chronology, is well served by this approach.

The next step was to review others’ thoughts on this. Googling for “blog full posts vs excerpts” did the job. Once I’d sifted out all the hits that were about how to implement excerpted posts as opposed to why one might choose to do this, I could get a better understanding of the merits of each approach.

The following are links to relevant articles or posts, most of which have associated comments that are helpful. I’d recommend you take a look at these if you’re also wrestling with the ‘full posts or excerpts on my front page’ decision:

• Full Posts vs Partial Posts, on the Homepage (at Pro Blog Design)
• Full Posts or Excerpts on your Blog homepage? (at BlogCatalog)
• Full posts or excerpts? (at Upstart Blogger)
• Post excerpts on the Homepage? (at Daily Blog Tips)
• Daily Blog Tips Now Features Post Excerpts on the Homepage (also at Daily Blog Tips)
• Excellent Uses of Excerpts in Blog Design (Vandelay Design Blog)

It’s worth pointing out that I’m not at this point considering the benefits or otherwise of excerpting posts in RSS feeds, rather than on the front page of a blog. What commentary I’ve seen on this seems to come down pretty solidly on the side of not excerpting feeds, so I’ll double check what’s going on with my own RSS feeds later.

Reviewing the links I’ve presented, I guess I could be guilty of a degree of confirmation bias. Nonetheless, there are a number of points made in the linked articles and comments that have helped me decide on the hybrid approach I’ve taken for now:

• Length of posts — time will tell, but I’m not expecting to be posting any very short posts (500 words per post is what I’m aiming for currently as a minimum), nor posts that consist just of a photo or two. Such posts certainly have their place on personal ‘journal’ type blogs, but that’s not where I want to take WildVista. I’m not considering mobile blogging from ‘the road’ either. So, excerpting most posts on the front page feels like the right thing to do. If I feel the need to post smaller items at a higher frequency, there’s always Twitter…
• User expectations — blogs are ’supposed’ to consist of a front page of un-excerpted posts that users scroll through. The more I read, the more I’m convinced that this applies specifically to journal-type blogs that have a strong chronological thread, and probably a loyal and relatively small readership. For blogs presenting more in the way of standalone articles or featurettes (that probably don’t have a much of a chronological flow to them), excerpts will provide the scanability (and can offer ‘teasers’) that is much harder to achieve with a lengthy page of full posts.
• Clear signposting — if using excerpts, the signposting to ‘Read more’ needs to be very clear. As things currently stand on WildVista, I think this particular navigation item is too subtle, so I’ll be looking into restyling this.
• Scope for use of images/magazine-style excerpts — I really like the idea of producing graphically interesting excerpts, and perhaps even laying things out more like the contents page of a magazine-style site. I couldn’t consider doing this without excerpting.

There were a few other points that kept coming up, specifically, advantages of excerpts with search engine optimization (SEO), and increased click rates. Neither of these are a driving factor for me at the moment. As I stated earlier, I want to get the user experience right, and I think posting the latest post in full, with excerpts for the next five posts, will be an improvement.

What do you think? Full posts, excerpts, or a combination of both? And how strongly should this decision be based on the type of content on a blog?

Time to dig a bit deeper then. With the edit and post functionality already taken care of, and having explored the various settings and options to make sure everything looks sensible, I reckon theming is the first thing to take a look at.

Now, as you’d probably expect, WordPress comes with a powerful and easy-to-use theming system. What this means is that, given an extensive directory of free themes, it’s the work of just a few mouse clicks within the WordPress dashboard to apply any of these themes to the entire site.

WordPress themes are easy to install: simply download the theme’s component files, and dump them in the wp-content/themes/ directory. The newly installed theme then automatically appears in the Themes section of the Appearance panel in the WordPress Dashboard.

So, what does changing the theme do? Here’s an example comparison of the front page rendered using the standard (and currently applied) “default” theme, and using the “Fusion” theme:

WildVista blog with Default WordPress theme

WildVista blog with Fusion WordPress theme

It’s not clear from the above screengrabs, but “default” is a fixed-width theme, whereas “fusion” (for this basic test at least) is a flexible-width theme. So, themes aren’t limited to controlling discrete elements such as the typeface or background images and colours, but also the dynamic layout characteristics.

It’s one thing downloading free themes and applying them to your WordPress site, but to achieve a specific look for your pages, it’ll be necessary to modify an existing theme, or create your own from scratch.

For the WildVista blog, I certainly want to move away from the default theme I’ve started with. There’s nothing wrong with it per se — indeed, it’s a very clean and clear design — but it’s not personal, and it’s used by myriad other blogs.

Before getting into the technicalities of creating a bespoke theme, it’s worth taking a step back, and thinking about how best to approach the job. The basic steps are:

1. Design
2. Implement
3. Test

For the design step, it’s best to step away from the computer. Pen and paper are all that’s needed to start sketching out various layouts. There’s no need at all to be getting bogged down in HTML or CSS at this stage; the technical implementation can take a back seat for now. Sure, there may be some aspects of a given design that turn out to be very difficult to implement in a WordPress theme, but right now, I don’t want my designs hampered by unnecessary restrictions.

Now, I’d better go find that pencil sharpener…