I think it’s important to publish what you learn. There’s really no school for front-end development. You can’t go to a university for a JavaScript degree or a class about how browsers work. Most of us learn from blogs and Twitter. Early in my career, I learned a bunch of things whenever I worked on a project, but I never told other people about them. So my general advice is to publish what you learn, share with the community, and collaborate on projects that help move the community forward.

How to make an background image scale without using a ton of JavaScript.

This may be worth looking into. I waffle on whether this sort of thing is ultimately a good decision — you're relying on someone else's framework, it takes a while to learn and master, and once you decide to go with it you're essentially stuck with it. But isn't that the case with any pseudo-framework developed for a website design? I should test this on a little project.

As seen on Normative.com.

"A tool for visual layout development of YAML based CSS layouts." YAML stands for Yet Another Multicolumn Layout.

"The need for these distinctions becomes moot, of course, when no secondary actions are present. Make sure you really need each secondary action on a form and don’t add them indiscriminately."

Things always to remember when building a form.