Thoughts about web design and web development from the field
The best place for conversation about a blog post? Its comments.
Different ways of looking at a problem can produce quite different solutions.
Continuing the a-z series with the bane of my working life: Content Management Systems.
Back in the day, we fastidiously kept track of list of interesting URLs, and grouped them in a menu list in our browsers. Whatever happened to that?
And so we begin with the first of twenty-six posts dedicated to all things web-related. First up: accessibility.
Announcing serious intentions to damn well start blogging again.
Just testing …
In which two popular browsers confound all expectations.
Margins often behave in frustrating ways when combined with floated elements. Here’s a quick solution to one such problem.
A port of Remy Sharp’s excellent ‘ify’ code.
Even the most basic styling can reveal differences in user agent styles
This tutorial explains, step-by-step, how to use CSS and jQuery animations to build a simple ‘auto-scrolling’ vertical list.
Or ‘Adding functionality to the CSS progress bar’
More fun playing with semantics.
Something not about web-design for a change.
‘Maths games’ may have an useful function to fulfil, but don’t overestimate their importance.
After almost a year of fairly sporadic blogging, an argument has finally arisen.
Specificity rules are simple and robust. Despite this, they sometimes ‘break’ in weird and wonderful ways.
Has the Typekit bubble burst? A cute CMS is launched. And Cameron courts controversy.
Presenting a greasemonkey script to fix the sidebar menu on boagworld.com.
Take a look at the wonderful world of ‘universal IE6’.
Terms such as ‘liquid’ and ‘fluid’ may be common amongst web designers, but they’re needlessly confusing for learners.
IE6 Update is a tempting prospect but, on balance, it’s just not the route I wish to take.
Article previews: whatever next?
Simple accessibility enhancements keep on coming: well done, Mozilla.
A lot of discussion is taking place about digg, twitter, URL shortening and page-framing. In twitter’s case, the solution seems obvious to me.
A brief response to a 456 Berea Street post.
Microsoft Windows still leads the way in flouting principles of usability.
Recent changes to the fma homepage have, hopefully, created a ‘best of all worlds’ layout.
A very early analysis of Safari 4 (it is, after all, only a beta).
Continuing (and probably rounding off) yesterday’s font size theme, a quick look at that immortal troublemaker: the pixel sized font. With a twist.
Two browser features are available for those who find small text difficult to read: text zooming, and setting a minimum font size.
Or ‘why would you want to?’
We’re all twits now
Another day, another set of broken behaviour
It’s time for Google to step up to the plate and rescue the web, for the benefit of us all.
Sometimes I feel like the CSS spec is just a little bit like the C++ language: too big for any mere mortal to hold in their head.
It seems that even the humble non-breaking space is beyond IE’s capabilities.
On the correct use of inheritance.
How to add a splash of colour to your bullet points.
Introducing a new ‘dynamic tutorial’ series
Another simple method to encourage in-bound linking.
Break your addiction to
!important and make the web a better world.
If you’ve ever dealt with logging or debugging your software, you’ve probably had to deal with the issue of whitespace. But how best to display this in HTML?
Time and time again, I see advice along the lines of ‘Add/drop support for a specific browser when your web site stats back up that decision’. Although this is, generally, sound advice, I want to make it clear that there’s a big caveat to that statement.
Early thoughts on Google’s latest Beta