css
What do I need to read to be great at CSS?
100 Bytes of CSS to look great everywhere
Changing Our Development Mindset
So many little design helper sites!
Whostyles
A Definition by Kicks CondorThe 'whostyle' is a way of styling syndicated hypertext from other writers. This could be a quoted excerpt or a complete article. A feed reader could use a 'whostyle' to show a post without stripping all of its layout.
This page is a truly naked, brutalist html quine
An Article by Leon BambrickI decided to make a truly naked, brutalist html page, that is itself a quine. And this page is it.
Viewing the source of this page should reveal a page identical to the page you are now seeing. Nothing is hidden. It's a true "What you see is what you get."
this vs. that
A Website by Phuoc NguyenAn Interactive Guide to CSS Transitions
A Reference Work by Josh W. ComeauIn this tutorial, we'll dig in and learn a bit more about CSS transitions, and how we can use them to create lush, polished animations.
CSS at the Intersection
A TalkThroughout the talk I discuss the mental models we construct in tech, the cognitive dissonance we experience when confronted with new ideas, specifically about CSS.
We know CSS has a separate mental model because we keep hearing the same debate rage on: “Is CSS broken or awesome?” This talk is about enabling teams to communicate and accommodate these different mental models. I share examples of effective tools, and how they change the way designers and developers interact.
The Great Divide
An Article by Chris CoyierOn one side, an army of developers whose interests, responsibilities, and skill sets are heavily revolved around JavaScript.
On the other, an army of developers whose interests, responsibilities, and skill sets are focused on other areas of the front end, like HTML, CSS, design, interaction, patterns, accessibility, etc.
How to Think About Notes
Thinking in terms of outputs
In our use of digital and analogue filing tools, we classify information through folders. An article about railway construction gets filed under ‘infrastructure’ or ‘transport’. In Evernote we tag it with ‘rail’ or ‘construction’. This is thinking like a librarian and not like a writer. We are classifying the information as an input. The reason you take notes as a writer is to produce content. It makes sense, then, to take notes in line with this goal.
Traditional filing like this tends to fail when you attempt to write your content. You are stuck trying to figure out which categories will be relevant for your proposal, paper or blog post. Interesting writing often comes from connecting separate fields through a common idea. By revealing the common denominator. By unifying two seemingly-contradictory ideas. How can you possibly achieve this if you’re looking in the same category for your information? The categories simply do not fulfil the function required by the writer.
The notes you take and indeed, the way you process information, should be with a specific project or idea in mind. You must classify information in terms of its outputs. When you take notes on a book, think about how this could apply to a specific idea you had or how it argues against a paper you read last week. The premise is that you should be organising by context and always trying to connect the dots between the content you're consuming.