Great advice on writing sensible comments in your code.
Wednesday, November 8th, 2017
Wednesday, August 23rd, 2017
Alla looks at ways of documenting animations into a pattern library. I tell ya, her book is going to be unmissable!
Friday, July 14th, 2017
Once again, we can learn from Christoper Alexander’s A Pattern Language when it comes to create digital design systems, especially this part (which reminds me of one of the panes you can view in Fractal’s default interface):
- Each pattern’s documentation is preceded with a list of other patterns that employ the upcoming pattern
- Each pattern’s documentation is followed by a list of other patterns that are required for this pattern
Thursday, June 1st, 2017
Sunday, October 23rd, 2016
A nicely-documented styleguide from Atlassian. It’s not a component library, though—there’s no code here.
Wednesday, August 24th, 2016
An in-depth look at the current Shadow DOM spec. It’s well-written but I don’t think this will really click with me until I start playing around with it for myself.
It’s good to see that the examples have some thought given to fallback content.
There’s also a corresponding tutorial on custom elements
Friday, July 22nd, 2016
Thursday, July 21st, 2016
I think Tyler’s onto something here:
I noticed three qualities that recurred in different combinations. Without at least two, the projects seemed doomed to failure.
I certainly think there’s a difference in how you approach a pattern library intended as a deliverable (something we do a lot of at Clearleft) compared to building a pattern library for an ongoing ever-evolving product.
Thursday, July 14th, 2016
Monday, May 16th, 2016
Wednesday, May 11th, 2016
If you don’t comment your CSS, you’ll confuse other people looking at your code, and, more embarrassingly, you’ll confuse future you. If you do comment CSS, everybody will be less confused, and things will be accidentally broken less often. You will be popular and generally well-liked, and people will remember to send you cards on your birthday. Comment more.
Some good advice here on how to write better comments in CSS.
Monday, February 29th, 2016
A pattern library of Walmart’s front-end code.
Sunday, January 24th, 2016
A nicely documented pattern library.
Thursday, August 27th, 2015
A nice combination of style guide and pattern library, with plenty of documentation.
Monday, September 22nd, 2014
Monday, July 28th, 2014
Mark Otto talks through the state of Github’s CSS and the processes behind updating it. There’s a nice mix of pragmatism and best practices, together with a recognition that there’s always room for improvement.
Thursday, January 16th, 2014
A handy one-stop-shop for documentation on web technologies.
Friday, October 26th, 2012
Jason goes into detail describing the File Format problem that he and others are going to tackle in the effort known as Just Solve The Problem.
Friday, December 2nd, 2011
Put this one on speed dial.
Wednesday, March 30th, 2011
I was nervous as hell before my talk at An Event Apart Seattle. I don’t normally get quite so nervous but it was a new talk and also …it’s An Event Apart! They set a very, very high bar.
Once I got on stage though, I just started geeking out. I was talking about design principles, a subject I find fascinating. I’m hoping that some of my enthusiasm for the subject helped make for a compelling presentation.
It was a whirlwind tour, starting with a long-zoom look at design principles in history before moving on to the web, where I took an up-close-and-personal look at CSS and quite a bit of HTML, before pulling back again to talk about our planet, our solar system and our galaxy. Yes, there was a space elevator.
I mentioned a range of people, organisations and projects that have documented their design principles, but rather than fill up the slides with lots of URLs, I gave just one URL at the start (and end) of the talk:
That’s where I gathering today examples of documented design principles. By “documented” I mean “published on the web.” There are some really interesting principles from disciplines like urban design but as long as they are locked up in books that aren’t addressable on the network, I can’t link to them.
This is a fairly small-scale project so I figured a wiki might be overkill but if you know of any good documented design principles that should be added to the list, let me know