Archive for the ‘wordpress’ Category


Baseline Theme Version 1.0.1

Tuesday, February 16th, 2010

There is a new version of the Baseline Theme. In the last few days of tinkering with it and modifying it for use with this website, I noticed a small bug. The Blueprint IE reset was acting funny in conjunction with the IE8 JavaScript. I chose to make IE8.js the default with the option of including Blueprint’s reset instead. (more…)

Blueprint Optional Fancy-Type Plugin

Monday, February 15th, 2010

The Baseline Development Wordpress Theme has Blueprint plugged in already. There are some optional Blueprint plugins you can take advantage of. We’ll take a look at the fancy-type plug-in. (more…)

Why Use Blueprint and the 960 Grid System in the Baseline Theme?

Sunday, February 14th, 2010

An Inventory of Blueprint’s Style Resets and Useful Classes

A friend contacted me about using the Baseline Wordpress theme, but asked why I included both Blueprint and the 960 Grid System. The short answer is that Blueprint has a number of browser resets that I like to take advantage of and 960 GS offers greater flexibility in terms of the width of columns and their gutter widths. Especially if you want to adhere to the Golden Ratio for design. 960 pixels divides very neatly into 3.

Let’s take a look at what Blueprint does to reset some things to establish a cross-browser baseline. (more…)

Introducing the Baseline Development Wordpress Theme

Monday, February 8th, 2010

I’ve come up with some habits that I’ve developed from building themes for Wordpress over the years. One, is to start with a nearly blank style sheet. I also like to hook in several JavaScript libraries and CSS frameworks from the start to take advantage of things like JQuery, Blueprint’s CSS reset and Superfish menus. (more…)

Wordpress’ Auto Update Is OK, But The Command Line Is Faster

Tuesday, November 25th, 2008

I recently found a great article about upgrading Wordpress from the command line. If you’re familiar with a command line interface at all, it’s by far the simplest way to upgrade your Wordpress install.

You can apply the same method to upgrading your Wordpress plugins.

  1. Log in to your web server and cd to the Wordpress plugins directory:
    cd httpdocs/wp-content/plugins

    Your syntax may vary depending on your server.
  2. Download the new version of the plugin. In my case I’m upgrading the Social Homes plug in.
    wget http://downloads.wordpress.org/plugin/social-homes.2.3.zip
  3. Back up your current plugin directory
    tar -zcvf social-homes.tar.gz social-homes
  4. Unzip the zip file of the new version
    unzip social-homes.2.3.zip

    • You’ll be prompted to confirm you want to overwrite the files in the social-homes directory
      replace social-homes/COPYING.txt? [y]es, [n]o, [A]ll, [N]one, [r]ename:
    • Type ‘A’ and hit return to overwrite the old files with the new ones.
  5. Log into Wordpress to make sure the upgrade worked by going to the “Plugins” panel in the admin area.
  6. Clean up your mess
    rm social-homes.2.3.zip
    rm social-homes.tar.gz

You’re done. You’ve successfully upgraded your plugin. This process can be much faster than downloading the plugin to your local directory, deactivating it in Wordpress and uploading the new one. Especially if the plugin is a large one.

Incorporating Blueprint CSS Into Your New Wordpress Theme

Sunday, November 23rd, 2008

If you’re familiar with the Blueprint CSS framework, you already know it can make your life a lot easier. So how do you get it into your Wordpress theme? Luckily, Wordpress is designed to make your life easier too.

I’m assuming your know the basics of Wordpress Theme Development. That is, at the very least you need:

  • header.php
  • footer.php
  • index.php
  • style.css

Put those files in a folder named after your theme. And put that folder in /wordpressroot/wp-content/themes/.

Once you’ve gotten that far, download the Blueprint CSS Framework and drop the “blueprint” folder from that download into your theme’s directory.

Finally, to include the new CSS files into your theme, just add this code to your header:

<link rel="stylesheet" href="<?php bloginfo('stylesheet_directory'); ?>/blueprint/screen.css" type="text/css" media="screen, projection">
<link rel="stylesheet" href="<?php bloginfo('stylesheet_directory'); ?>/blueprint/print.css" type="text/css" media="print">
<!--[if IE]>
<link rel="stylesheet" href="<?php bloginfo('stylesheet_directory'); ?>/blueprint/ie.css" type="text/css" media="screen, projection">
<![endif]-->
<link rel="stylesheet" href="<?php bloginfo('stylesheet_url'); ?>" type="text/css" media="screen" />

Pay attention to the order. You want to make sure that href="<?php bloginfo('stylesheet_url'); ?>" appears last in the list of style sheets. That’s your style.css where you can tailor the CSS for your specific design.

That’s it.

My Private Summer of Coding

Tuesday, May 13th, 2008

A couple of weeks ago I met with Garrick VanBuren to talk about cullect.com. I came away from the lunch excited about two things: Trying out some of the features in cullect that I hadn’t quite understood before and giving Ruby on Rails another shot.

I went to lunch with Garrick to offer him some feedback about why I hadn’t adopted cullect yet. (I’ve had an account for about 7 months.) A few colleagues were raving about it. I knew I had to be missing something. I was.

While I think cullect has a way to go before widespread adoption (it runs a little slow on my PowerBook), I see what everyone else likes about it and more importantly, I see lots of potential. So, nice work Garrick. I drank the Kool-Aid. I now curate a small batch of feeds about music and “recommend” posts so the best rise to the top in my “Important” list. This way I can also repurpose those same articles to Minneapoliscast. In other words, I can repurpose content so that relevant reading is included with what I publish. It’s fun and it’s cool.

I’m not even going to talk about how you can pay cullect so that part of your monthly subscription goes to publishers you read. I can’t even tell you how cool I think that is.

What I really wanted to write about is how I came away from our conversation inspired to try Ruby on Rails. I’ve been toying with RoR for about a year now. As I started working my way through Agile Web Development on Rails last year, the realization gradually dawned on me that I was going to have to sit down and learn Ruby. So I bought a pdf version of Programming Ruby, but I didn’t really get very far before other duties called. I just didn’t have time to learn a new language.

After talking with Garrick I was determined to give it another shot. Then I thought, there has to be a Rails-like set of tools for PHP–a language I’ve been working in for years. That thought and a quick Google search led me to CakePHP.

Two weeks later and I’m near completion of the first module to manage clinic and lab data here at work. Once I got my head wrapped around MVC and the built-in helpers in CakePHP, the development got faster and faster. (Disclosure: The database was already fully envisioned and built beforehand. An important first step.) I can’t tell you how gratifying it is to quickly code something in a few lines, test it and have it work. I have a whole summer of coding ahead of me. I’m very excited to deploy this application by fall.

On a final note, I was feeling a little cocky, so I coded my first Wordpress plugin yesterday too. Again, easy. It’s not quite ready for public release yet but with a little tweaking, I might just release it. Basically it just pulls in PodPress data and lists the ten most popular podcasts on Minneapoliscast.

I was a little worried that with our research slowing down over the summer I was going to be bored. Now I’m really looking forward to the coming months. Fun stuff.