(Warning: thought-leadery post)
Problems with CSS are not a result of flaws in CSS. The problem is how we write CSS.
There is a borderline overwhelming amount of documentation to be written, but gotta start somewhere! Here's a kinda random first addition to Larva's Naming Guidelines wiki page.
I spent a while debugging a font-face issue. Can you spot the problem?
I thought I encountered a browser bug, but I didn't. I learned some things, and now you can read this and learn them, too!
.u-glue is a CSS utility class (or what I would call an algorithm) that provides an API for positioning an element absolutely over another element. We are using it at PMC, and it's proven a useful model!
Over the past year, I've been giving a talk called The Algorithms of CSS, originally created for CSSConf EU. This post covers the first part of my presentation, and breaks down how CSS fits into the categories of programming languages.
This is the second in a potentially ongoing series about my work at PMC as a Design Engineer. This month was full of lessons learned about working at a big company, building out a pattern library, and an exciting foray into Node.
I've been somewhat checked out of Twitter, etc. for the past week and returned to a fresh round of CSS drama. Here's my take: it's noise.
This post is a summary of what I've been working on at PMC as a "Design Engineer". Note that it is written in haste (WiH)!
I've been researching design systems lately, and this is an evolving list of the resources I've found particularly resonant for my purposes. Have anything to add?
This is the first in a potentially long series about browser mechanics, in my own words. Read on to learn about one of the first steps a browser takes: decoding bytes to Unicode code points.
Is CSS a programming language? What is a "CSS algorithm"? Read on to answer these questions, and to learn how CSS fits into the world of programming and computer science.
This post is a response to a tweet critiquing the "code export" capability of design tools, and a talk called "Stop Drawing Dead Fish" that calls for better tools to allow artists to create visual art without code. Should designers code? Should artists code? It's a nuanced, interesting topic and I had some thoughts.
I always think I will remember more than I do. This is the first in an attempt to create a habit of writing "Things to Remember" round-up posts when I feel inspired to do so.
Adjusting to life in LA has taken a lot longer and a lot more work than I anticipated. I find myself re-discovering my work and learning habits, but I'm finally starting to feel back in the game after my break earlier this year. Here are a few things I'm particularly excited about.
I’ve made a few websites over the past year or so, and I finally feel like I’ve nailed down the process. Of course there’s a lot more to it, but potentially the most useful, simple, and adorably named part has been a […]
CSS layouts are tough...I don't care who you are!
Floats and clearfixing are just hard concepts to grasp, and building layouts in CSS the proper way is no small feat. Come to this evening workshop and learn to create your own responsive layouts. Where and when, you ask?
August 21, 7-9pm at New Work City
Use the code "salmon" for $25 off.
\It’s not too hard! I was writing up a demo and figured I might as well share it with the world. You can do it in CSS or jQuery, definitely useful for galleries.