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.
Five basic rules
Five basic rules:
(1) Record your work as notes to your future self and colleagues.
Write notes so that someone fifty years from now (or more) will understand and be able to use the factual information you collected, perhaps for purposes quite different from the original reasons.
Clearly separate facts from interpretations so these are not confusing to a future reader.
(2) Establish a clear and consistent notebook format and process.
I always include the data, place, main activities or events, weather conditions, and other people involves. The day, month, and year is the most important link between that particular point in time and other people’s records, separate data sheets that I filled out myself, photos, and most important, collected specimens.
Documenting collecting strategies and protocols receives special attention. In the moment, these may seem like common knowledge for the field team, so sometimes no one bothers to write them out.
(3) Don’t lose your field records!
(4) Pack a camera, create a visual record.
No matter how many words you write to describe a fossil locality, you can’t beat an actual photo, taken on the spot, annotated in pen, and pasted into your notebook.
There is no substitute for a photograph you actually mark in “real time” in the field as the best way to preserve a lasting, accurate record for yourself, or for someone who has never seen the site or object in question.
(5) Learning through sketches and diagrams.
Photographs are great, but drawn what you see is a more powerful way to learn about spatial patterns and relationships.
Even if you are not an expert at drawing, you can make sketches that are much more informative than words would be.
Always include a scale, an orientation, and labels in your diagrams.