andyford

It's one guy with a Lego fan hobby blog. Not everything needs to be Web Scale all the time

As much as I like dunking on Amazon and Bezos, I can't help but wonder if this could be applied to brick and mortar stores where you go in and ask for help finding something and they pitch you the product that's best for their sales commission

Bet on Eleventy... the creator of it works for Netlify

how to get to moon without a rocket: 1. go to moon and install thin wire on moon and dangle it toward earth 2. use a rocket to reach wire

oops. one of the homepage links points to their dev site http://theparisreview.tierradev.com/interviews/6806/the-art-...

I'm glad to see another viable CSS non-framework and Shoelace looks very promising. I haven't put it through its paces yet, but found a nitpicky thing... why have a "table td" selector? You can't have a td outside of a table anyway. This is top of mind for me because I was just grappling with Bootstrap's lovely specificity nightmare ".table > tbody > tr > td"

one, two and zero are all numbers.

rare video indeed

Totally awesome. But can't buy the wall map until they fix the "asterix" typo!

Whooo! Thank goodness!!! We needed more YUI URLs!

The moment before your code looks like this, you use Sass.

I can hear it now... "but how do I do it in jQuery?!"

http://api.jquery.com/ done

The lowercase 'e' in Monofur is a deal breaker. Too reminiscent of italics. And the mixed baseline numerals don't help either. Otherwise it's pretty nice. Of the 10, Inconsolata deserves to be #1.

For the OP (and HN readers in general), I recommend Founders Talk - http://5by5.tv/founderstalk. But make sure to check the list of all the shows - http://5by5.tv/broadcasts - lots of good ones.

This is missing the point. The problem isn't that some designers are losing work to 99designs. The problem is that spec work devalues the entire design industry.

Like many of the other commenters, I break the code into reset, global elements, layout, modules/blocks, and then special overrides if any.

I'll admit it's a personal preference, but as a team consideration I don't recommend the 'all properties on one line' approach. It's discouraged in other languages so why do it in CSS?

Definitely check out OOCSS as well as the Natalie Downe talk both posted by in the comments already.

I can't overstate how highly I recommend Sass/SCSS. It's been mentioned already as "for Ruby". Yes, you need Ruby installed to use Sass/SCSS but you do not need to be working on a Ruby project to use it. You can run "sass --watch (directory name)" from the command line and sass will automatically compile your .scss (or .sass) files to .css files upon save. Even if you're scared of the command line I assure you, it's easy! If you're a TextMate user, there's also a great SCSS bundle here: https://github.com/kuroir/SCSS.tmbundle (it was enough for me to abandon CSSEdit for good)

One thing that hasn't been discussed in this thread yet is the organization of properties within a declaration block. It's a good idea to have an approach and stick with it. Alphabetizing the properties is one approach. I wrote about my preferred approach a couple years ago here: http://fordinteractive.com/2009/02/order-of-the-day-css-prop... (also check out the SitePoint discussion linked in the "Further Reading" section of the post)

"iOS is far less usable and powerful than Android, but people like it more because it's visually pleasing."

I'd argue that iOS is far more usable than Android in addition to being visually pleasing.

They did http://stackoverflow.com/questions/2253110/how-to-manage-css...