Minimum Page, A CSS Base
We decided to release Soupgiant‘s CSS base to the world at large, you’ll find it at minimumpage.com.
Category: Blog
Euthenasing Internet Explorer 6
Much of the time website owners & developers decide to drop IE6 support and they forget a key tenet of customer service: it has to be focused on the customer!
Putting the “distributed” in CDN
I wrote yesterday that Google appeared to have taken the distributed out of their public CDN hosting a variety of JavaScript libraries. I even provided some trace routes comparing their CDN to Microsoft’s. I was wrong.
Taking the “distributed” out of CDN
Over on Twitter @bobearth prompted me to do run some trace routes against the Google CDN and compare it to the Microsoft CDN. It appears Google have taken the distributed network out of their CDN.
!important is Important
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.
Big Red Framework
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 […]
Guest Post on Digging into WordPress
Jeff and Chris have been kind enough to publish Hosting Client Sites on a WordPress Network as a guest post on Digging into WordPress.
Caching Google’s WebFont Loader
As with Google’s other hosted libraries, providing a more specific version number of webfont.js will effect browser caching.
Soupgiant WordPress themes on Github
The Soupgiant base WordPress themes are now available on GitHub. There’s no documentation at this stage, I’ll write up a blog post with details in the coming week.
HTML5: I couldn’t (quite) do it
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.