The New WPLover Redesign (and the Thoughts Behind it)

Hey there! WPLover is now sporting a brand new theme (for the RSS subscriber folks, come take a look!) Aesthetically I do not have a problem with the previous theme, and it’s foolish to redesign just for the sake of having a new look, but there are various things I want to improve and it turns out the best way is to build a new theme. Here are some thoughts and notes that come with this redesign.

Branding and Refocusing Efforts

For the last few months I have wanted to move the focus of this blog, from a WordPress news link blog to a more article-oriented, design and development related one (but still with interesting link posts from time to time). The previous theme felt like a half-hearted effort to bridge between the two, and I think it’s high time to straighten the focus immediately and make a theme that imply such change.

From the start I didn’t have a set rule whether I should call this place “WPLover”, “WP Lover”, “wplover”, or what have you. That was an oversight that I want to fix along with this redesign, and I have decided to use “WPLover” and added a logo for it:

WPLover logo

A heart symbol is admittedly the most predictable choice for something called WPLover, but I believe the shape is unique enough to stand out on its own. Also, to my eyes the shape represents a quill, for learning and development, and a butterfly wing, for the beauty aspect of a design. I did this logo myself, and as my own client I say I’m pretty happy with it.

The tagline, not so much (so generic!), but I figure I can change that when I come up with something more interesting. For now, it does it job pretty well (that is to better explain the site’s focus), and I’d rather launch the new design quickly than wait for the perfect tagline.

A Better Layout

Layout-wise, the previous theme already tried to reflect the site’s focus by having a large, main articles area while putting the links on the sidebar. In practice, though, I found that a three columns layout was ineffective.

WPLover theme Damage Control screenshot

Ineffective how? Google Analytics showed that the contents on both sidebars didn’t get a lot of clicks. This was especially true for the rightmost sidebar where the latest link posts were. I concluded that the area wasn’t needed, and the space could be better used to aid readability for the two other columns. Also, I didn’t have that many contents that needed to be put on a sidebar anyway, so having two dedicated sidebars was an overkill.

That’s why I opt to go with 2-columns instead. With a much bigger main content area, I can give better focus and readability for the articles.

Lastly I still wanted to showcase a list of latest link posts on the layout, and I decided to put it on the footer area. That way it becomes it a sort of bonus content for those interested enough to read to the bottom. According to my stats these links get read the most by RSS subscribers anyway, so a change of position in the new layout should not have a negative effect.

WPLover theme Sweet Spot links list area.

An Opportunity to Learn New Things

I’ve been wanting to try the jQuery Masonry layout plugin, and the links list area is good match for it. WooThemes also has a theme called Mortar that’s build with this plugin as the backbone, and I did learn a lot from the theme demo.

Another neat jQuery trick I learn is setting a hover class for everything. The latest links area, while neat, can be a bit confusing to read due the way Masonry stack things. I want to give visitors a visual aid to help them read that area, and changing a link box’s background color when hovered is the solution I came up with. The small jQuery tips on the article above helped me achieve that.

Constraints for the New Design

To keep the redesign effort focused and not waste time, I came up with a bunch of constraints for it:

  • Not start everything from scratch. I reused the majority of the PHP codes from the previous theme (only a few tweaks for some HTML), and in practice the development was akin to a CSS Zen Garden experience: the HTML layout is the same with the previous theme layout, but it looks totally different thanks to the magic of CSS.
  • Keep the 960px total layout width. This is because I already have a specifically-designed Page from the previous theme (the Pico theme landing page). By using the same width, I didn’t have to worry about changing that Page’s design.
  • Ignore IE6. The constraint I’m so happy with. The design should look correct on all modern browsers, and that’s all I wish for.

Thanks to those constraints, this theme could be finished in under a week, from design to implementation and testing.

A Work in Progress

I like to see this blog’s design as a continuous experiment, so while the current theme is already complete as it is, I’m keeping it open for more tweaks and realigns in the future. I’m releasing it immediately so I can see how it works in reality, and will learn and make changes from there.

Those are the thoughts that come with this current design. Now I sit back and see whether it works as expected. Thanks for reading this far, and I’d love to hear what you guys think about it!

Latest Links More →

The Week in WordPress: 2nd Week of November, 2012

Ghost, Rethinking WordPress. Also don’t miss the discussion over at Hacker News.

For The Aspiring Professional WordPress Developer is a collection of good advices for those wanting to be a WordPress pro.

Recently I had the task of cloning a WordPress site both to my local server and to another development server that I host. The Duplicator plugin has been a massive help for me, makes cloning really simple and fast. Highly recommended.

Classy Plugins

Eric Mann uses classes in his non object-oriented WordPress code. Here’s why.

Playing Nice with the “the_content” Filter

This great article could be useful if for some reason you have a need to filter the_content in your theme.

Google Goes After Links In WordPress Themes

New post from the Search Engine Roundtable: Someone “…received a response from Google to a reconsideration request that the only way his site will be reincluded in Google is if he removes all or most of the links in those WordPress themes.” The problem is that those links are in the form of sponsored links on footer (a practice I saw a lot in the past, not so much in the present).

I don’t think it will be easy, or even possible, to do what Google requested. If a theme contains an upgrade notification feature it might be possible to do, but even then the users might choose not to upgrade.

Secondly, if this is true, I wonder whether Google differentiates between credit links (“Designed by…”) and sponsored links. I would say they should, but then again I’m not a SEO guy.

Theme Options Gallery

New favorite blog: Theme Options Gallery by Konstantin Kovshenin, discussing “the best (and the worst) theme options screens around”. Loving the in-depth article and discussions already available there.

Dive into Responsive Prototyping with Foundation

Pretty safe to say that if it shows up on A List Apart, it’s going to be the de facto standard. Time to learn some Foundation.

Google HTML/CSS Style Guide

Couple of days ago we got Starbucks’ style guide, and now here’s another by Google. I think the interesting thing is the rule to “\[o\]mit the protocol from embedded resources“. So instead of typing <script src="http://www.google.com/js/gweb/analytics/autotrack.js"></script>, they recommend to type <script src="//www.google.com/js/gweb/analytics/autotrack.js"></script> instead (without the http part). Never heard of that before.

“I Woke Up but My Server Wasn’t There”

Robb Shecter’s WordPress site got popular overnight thanks to Reddit and went down immediately. The interesting aspect is that the site was new and it’s on a relatively high-powered server. The author then found that the theme he used in particular was doing too many (47!) server requests at a time, and the site ran along very well after switching back to Twenty Eleven.

I think it’s an important read for any theme developers out there.

Read the story here

Modern Web Development – Part I: The Webkit Inspector

A superbly detailed article, part one of a series about web development toolchain.

Crayon Syntax Highlighter plugin

I’ve always been on the hunt for that perfect syntax highlighter plugin. Currently I’m using WP-Syntax, which does its job very well. However I’ve just found this plugin called Crayon Syntax Highlighter, which could be a good contender for the best WordPress syntax highlighter plugin out there.

It looks good, and I like the little toolbar on top of the code box, with the small icons. Additionally, it also offers a lot of customization options. Lastly, it seems to support the same pre tags to wrap the code, similar WP-Syntax, so if I do make the switch, my old codes will still be highlighted correctly.

Starbucks Style Guide

The Starbuck website has its own style guide, accessible for public. I think its a neat idea, wouldn’t it be cool if themes have their own style guide? Pretty sure it will be helpful both to users or developers alike, if time consuming to write.

Also, I wonder what they use for the various toggles panel on the top right corner like on this page. It shows background, baseline, boxes, can be used to change windows size as well. Looks like it’s custom coded, imagine how super useful it can be if it’s a jQuery plugin.

NHP Theme Options Framework

I love theme options frameworks. And I want you guys to check this new framework called NHP. It passes my “does its UI look like the rest of WordPress enough?” test (screenshots here), it has tons of field types, and even offer validations, too.

Can’t wait to test and probably use it too in my to-be-released theme hint hint

What Dev4Press thinks WordPress needs…

This post at Dev4Press outlines what MillaN, its author, thinks would be a necessary addition to WordPress.

Based on the comments, it appears that a lot of people agree with this list. Some of the items mentioned can be achieved with plugins (e.g Tax Meta Class to add meta data to taxonomy items, Custom Post Types Relationships for, well, creating custom post type relationships), so expect there to be a bunch of debates about what should and shouldn’t go to the core.

I like his list, but I disagree with his assessment that we don’t need new core themes. We do, especially to bring about the standard for how a theme options should be designed. This is the aspect that desperately needs to be standardized. Different theme companies and individual theme designers have their own idea of how the theme option UI should look, and it’s hurting the users.

Upgrading from WordPress 1.5

I recently spotted this interesting Ask Metafilter thread where user gd779 tries to find a way to upgrade his old, WordPress 1.5 install. One of the answer is pretty detailed:

I think the right approach is going to be:

  1. Do a full backup of your WordPress files
  2. Do a full database backup (mysql dump using phpMyAdmin or similar)

Then, from your 1.5.2 install:

  1. Upgrade to 2.0
  2. Upgrade to 2.5.1
  3. Upgrade to 3.0
  4. Upgrade to 3.3.1

It is quite fascinating thinking about the solution to this. There’s an official Codex page called Updating WordPress, but it doesn’t seem to go that far back in time.

Smashing Special: What’s Going On In The WordPress Economy?

Siobhan McKeown wrote this awesome, birds-eye view of the whole WordPress economy. Make sure to read this two-part article so you know what’s up with WordPress and identify what opportunity lies ahead.

I agree with Matt’s prediction on that article:

I think the next big opportunity is around agencies and consulting—there will be five to six companies as large as Automattic, just providing high-end consulting and services to the large customers who are adopting WordPress en masse.

Start with Part I of the article.

Automatic responsive images for WordPress

The one issue with creating responsive web design is in displaying images, especially getting the most appropriate size in a particular screen size. One solution for it is the Responsive-Enhance jQuery plugin. It works by loading small-sized images by default, then checks the screen size and loads the bigger version if necessary.

According to its creator, Josh Emerson:

This results in a faster perceived page load speed, but a slower actual speed. I’m happy with this solution as I care more about perceived speed than actual speed.

This tutorial by Keir Whitaker takes the whole thing further by teaching us how to apply Responsive-Enhance in WordPress.