✻ In Optimizing for Large-Scale Displays, Jon Yablonski discusses some approaches that might help when refitting content to larger screens:

✻ Chris asks about advice for going freelance and he found that many folks believe that increasing your rate, finding an accountant and wearing pants on a regular basis are the most important improvements to a fledgling business.

✻ And Geoff Graham looks at our Options for Building Web Forms:
Building a form is one of those tasks in front-end development that I forget how hard it is until I'm asked to do it. It's no big deal if we're talking about a couple of text inputs and a submit button, but we're often looking at something much more complex. Radio buttons, numeric inputs, Ajax validation and submission—oh my! That's before we even start discussing browser inconsistencies, input states, payment integration, and accessibility.

What we’ve been reading, listening and watching

Harry Roberts has written about the importance of using !important from time to time, yet he warns developers that...
...using !important to get yourself out of a problem with some existing CSS is most certainly inadvisable. It will have knock-on effects whose only solution will be to use another !important, then another, then another, ad infinitum.

Do not use !important reactively. Do not use !important to solve a specificity issue. Do not use !important in anger.
Another interesting rule that comes up a lot, but in terms of design, is the one that states designers should only use three typefaces in a project. Over on the Hoefler & Co. blog, Jonathan Hoefler writes about how to use clashing fonts instead:
Here are three types of font pairings that are traditionally scorned, but when used with purpose, can be supremely successful. We’ll be retiring that old chestnut “don’t use fonts that are too similar” in favor of a more constructive philosophy: “make each font’s purpose clear, and use every one consistently.”

And finally, Robin Sloan has made a plugin for the Atom text editor that autocompletes with suggestions from hundreds of other sci-fi stories. So that whenever you hit tab after typing some text, this happens:
What’s so interesting about all this – and how it relates to our work on the web — is the questions it brings up around tooling. 
 
❥ Sponsor: Free online proofing tool
Share videos, PDFs & images. Get real-time feedback from your collaborators. Check out ProofMe!
 
A note from the archives

With the Grid specification looming on the horizon it’s a good idea to refresh our understanding of all the current methods for making grid systems. A while back, Chris made a screencast that looks at a very simple system that is still very much in use today:

 Don’t Overthink It Grids 

We'll have to do a follow up to that soon on how flexbox can make simple grids like that even easier. Stay tuned!
 
What have you learnt this week?

Chris Coyier: I needed some pretty specific functionality on an input this week. When the input was focused (clicked into, tabbed to, forced, etc) it needed to "scroll" to the end of the input and put the cursor there

As one often does, I searched around and found some promising StackOverflow threads. One of which referenced my own snippet on the subject from three years ago. Derp. The snippet was more robust than what I was tinkering with, so that was a win. But I also noticed it had some new quirks that had developed in the subsequent years and was heavy-handed in places.

So I updated the demo and the snippet! It's in the format of a jQuery plugin, but it's simple, commented code you could port anywhere.


Until next time!
Team CSS-Tricks
Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.