I will show you what you need to do by way of an example.  Let us suppose we need the site URL in our JavaScript code.

It is a two step process, the first step is in your PHP;

wp_enqueue_script('my_script');
$data = array('site_url' => __(site_url()));
wp_localize_script('my_script', 'php_data', $data);

So what we have done there is enqueued our script (named here, my_script) and once we have done that we set up our data array. In our case the property is site_url and it’s contents are going to be the result of site_url(). Once we have that we can call wp_localize_script, into it we pass the name of our script, the name we want to give our JavaScript object and the data we want to pass in.

Next we want to be able to access the data, so in your JavaScript file you can simply call the following (if you wanted to alert out the site URL!)

alert(php_data.site_url);

Really, really easy and really, really handy!

For more information please see the official reference.

Normally the way these things go down is I view the demos and have every intention of trying it myself but there are usually just a couple too many steps involved for the time I have allotted to dicking around the interwebs but this was so quick and so straight forward that I have eliminated cufon from this site in about 5 minutes.

Here are the steps I used;

1. Follow the link above.
2. Click on the font you want.
3. Click get the code.
4. Copy and paste the link into the head of your page.
5. Update your CSS with a copy/paste.
6. Done! (well, I also had to jump onto WordPress and turn off Cufon in a settings page, but that is specific to my template.)

I am not a designer so I don’t really know if those fonts are any good or not from a design point of view, but the potential for breaking away from the standard websafe fonts is huge!

In order to do that I had to make some changes to my theme, which I figured I should document.

I went into my theme directory and created /js/themename.js

I edited the header (themename/header.php) to include jQuery and /js/themename.js…

<script src=”<?php bloginfo(‘stylesheet_directory’); ?>/js/jquery-1.3.2.min.js” type=”text/javascript” ></script>
<script src=”<?php bloginfo(‘stylesheet_directory’); ?>/js/lightword.js” type=”text/javascript” ></script>

Inside of themename.js I created my $(document).ready() call and gave it the code it required.

I uploaded /themename/header.php, /themename/js/themename.js and themename/js/jquery-1.3.2.min.js to the site.

That is it!

Download the cheat sheet from Ekin Ertac.

How to do A/B Testing with WordPress from Carsonified on Vimeo.

The importance of A/B testing really can’t be overstated enough, it is one of those things that you really don’t think has the type of effects that other people talk about until you try it yourself. And with tools like this making it stupidly easy to do this kind of testing there is really no excuse.

1. Create a style from scratch
2. Use a free theme and heavily modify it
3. Just use a free theme

I thought I would take some time put my thought process on paper and share it with you.

• Create a style from scratch

Creating a style from scratch is easily the hardest one to complete, however potentially the most rewarding.  You could really get your teeth into the code that WordPress uses and you could really push the boat out with bells and whistles.  At the very start I thought this was the road I wanted to go down.  I have been under the hood of WordPress many times making both small cosmetic and functional changes, but I have never had to sit down with any part of it from scratch and work my way up, and I thought this would be an excellent challenge.

The main thing that stopped me from doing this was creative ability and the need to get something up and running quickly.  I am not a graphics designer, it is something I am trying to improve upon but at the moment I only have the most basic knowledge of what makes a good design.  I didn’t think it would be fair on my 3 readers to have them endure endless changes to the layout whilst my technique improved.

• Use a free theme and heavily modify it

I have seen this being done a lot and with very mixed results.  I dismissed this out of hand because I think in the time it takes to heavily modify a theme (by which I mean change it enough so as to make it your own) then I think you may as well of started from scratch, it seems fairly lazy in my opinion to take the foundations of what someone has made then chop and change it to suit yourself.

• Just use a free theme

This is most definitely the laziest option, however it is also the one I went for and the one I am going to defend (not that I feel I really need to!) here.

Using a free theme has many advantages; you can install it and have it set up in literally a couple of minutes, all the browser testing as (hopefully) already been completed, you can get all the benefits of have a good designer work on your site but without any associated costs.

It also has a couple of disadvantages; You learn nothing, you end up with a site that is bound to look like at least 100 others.

I am going to sidestep the learning nothing issue by promising myself that I will be making my own design from scratch someday.

I am going to do a couple of things regarding the fact my site will look the same as others, the first is that I plan to make minor changes, whilst overall I am happy with the theme there are a couple of small things I want to change.  I don’t think this counts in any way as heavily modifying the site and it will stay true to what the original designer had in mind for it.  The second thing I am going to do about this disadvantage is point out that this is a lovely theme and there are at least 100 other blogs that look damn fine!

Did I make the right choice? Let me know in the comments!

Well the short answer is because I can, with the wonders of wordpress and a decent hosting company I had the space made, the domain bought and paid for and the blog installed in literally 30 minutes (and that included checking my emails, other general internetting and changing a record on my eld vinyl player).

The slightly longer answer is that I have wanted to create something like this for a very long time, I love what I do and I have found that I like to write about things I love to do.  The main issue I have is that I love to do a lot of things, which means I love to write about a lot of things, which means I have my fingers in many pies, which means I often waste evenings doing things on no consequence on some of my smaller sites.  This all changed however when somehow I managed to convince the directors in my work that allowing me to write a web development blog would be an excellent objective for the year – which gave me an excellent incentive to actually do it.