Category: Code

For several years I’ve used Paul Irish’s technique for avoiding the FOUC caused by JavaScript kicking in. I’ve recently changed to a slightly improved version.

It’s time to update Dan Cederholm’s faux columns to take advantage of CSS3 gradients and reduce http requests.

Imagine you’re playing the latest hash-tag game on Twitter when you see this friendly tweet: You might want to check your #WP site. It includes two copies of jQuery. Nothing’s broken, but loading time will be slower. Continue reading at Smashing Magazine.

When producing a theme, we try not to limit the website owner’s options within the WordPress Dashboard. The owner may wish to enable an option down the track and be disappointed to find they can’t.

We’ve recently changed the way we do IE hacks at Soupgiant. For years we were using conditional comments to load separate CSS files.

Anyone who has attempted to navigate a web page using the keyboard will have experienced sites that remove the default a:focus style without adding in a replacement.

The !important declaration has really bad reputation, and deservedly so. As is often the way, this reputation results from abuse rather an inherent problem with the property itself.

We’ve updated the base WordPress theme we use at Soupgiant for WordPress 3.1+ and to make more use of the WordPress API. Along with the standard features you would expect in a WordPress framework, it includes templates for the Theme My Login plugin, custom default code for Formidable / Formidable Pro plugins, custom html output […]

I found it difficult to use pure and semantic HTML5 when dealing with current versions of Internet Explorer. I really tried to adopt the commonly advocated view that it’s okay to require website visitors have JavaScript enabled but settled on a different option I could actually live with.