work blog home
-
People often ask me to summarize the dangers and pitfalls of a css project. If you've been writing css for some time you'll know there are quite a few, many of which are difficult to explain to people not familiar with actual css code. Composing textual summaries is simply too boring and technical for most people to really care about. So I'm gonna try something different today.
-
Some issues appear too simple, too obvious and even too common to notice. These are the issues that are often essential to determine the strength of a language. These are also the issues that need investigating to improve a certain language from the base up. I've written about a similar css nesting issue before, a couple of weeks ago I ran into a new one.
-
Last week Jens Meiert launched an article on the the reinstitution of px. Google is officially pulling the plug from IE6, which means the last browser to fail scaling px-defined fonts is yet another step closer to its death. A good time to re-evaluate the difference between px and em designs, keeping a strong focus on why they aren't as different as people usually believe.
-
Front-end development has come a long way ever since we've switched from tables to divs. In 10 years time our job shifted from after hours tweaking to becoming truly professional occupation. Still, when taking a moment to look around there is still lots of room for improvement. A little too much maybe, so here are some important pointers that will help you to become better at what you do.
-
With the release of FireFox 3.6 it is now possible to do css gradients across the most commonly used browsers. This is cause for celebration no doubt, but looking at all the different implementations and workarounds this requires, we're still a long way from where we need to be. Add to that some unexpected troubles and there's enough substance for a short article.