Links from 2014

Solid wash-up.

<blockquote>while we were filming in 35mm and could have ostensibly “protected” ourselves by adopting wider shot composition in the event of some future change of heart by HBO, the problem with doing so is obvious: If you compose a shot for a wider 16:9 screen, then you are, by definition, failing to optimize the composition of the 4:3 image. Choose to serve one construct and at times you must impair the other.</blockquote>

<blockquote>Informative and easily navigable live styleguide which can be edited directly in the browser.</blockquote>

<blockquote>A quick-and-dirty frontend styleguide, designed to be copied and pasted into your CMS. Why? You're not Twitter Bootstrap. You don't have the time or money to make a custom fancy-pants dynamic CSS pattern-library. And that's OK. You have other fish to fry.</blockquote>

<blockquote>We’ve long been curious about the performance of popular JavaScript MVC frameworks such as Angular, Backbone, and Ember.</blockquote>

Nice visual run-down of OpenType features.

<blockquote>OpenType features are like secret compartments in fonts. Unlock them and you’ll find ways to make fonts look and behave differently in subtle and dramatic ways. Not all OpenType features are appropriate to use all of the time, but some features are critical for great typography.</blockquote>

Hosted CMS for SSGs

<blockquote>Up-to-date data on support for type and typographic features on the web.</blockquote>

<blockquote>Monospace text sizing is, from time to time, completely unintuitive and can be quite maddening if you don’t look at it in exactly the right way.</blockquote>

Autoprefixer is moving browser list handling to a separate plugin.

<blockquote>the whole idea of converting pixels to ems is pointless. Use ems where you need something to scale with the font size of the component, rems for something that scales with the base font-size and pixels where you need an absolute value that doesn’t depend on the font-size whatsoever etc. Different units have different purposes. </blockquote>

Lea Verou makes a good point.

<blockquote>The easiest way to create front-end style guides with Sass and Compass.</blockquote>

<blockquote>The most important thing for our components is the documentation. This defines the interface that applications can call the component with. It contains a set of fixtures to demonstrate how an application might call the component.</blockquote>

<blockquote>Helps you find the trains that arrive punctually and avoid those that are often delayed. See how much trains on your route are typically delayed by and plan accordingly.</blockquote>

Why postprocessors are better than preprocessors. So there.

And dads, obviously.

Some excellent live examples.

<blockquote>Grid forms are dense forms designed for use in applications that require lots of data to be entered regularly. A tiny Javascript/CSS framework that helps you make forms on grids with ease.</blockquote>

<blockquote>An Open Source Design & Frontend Framework that serves as a foundation for internal business applications.</blockquote>

Good intro.

<blockquote>My third post about typography in sci-fi has been gestating for a while now...</blockquote>

<blockquote>All too often mobile forms make use of drop-down menus for input when simpler, more appropriate controls would work better. Here's a few alternatives.</blockquote>

<blockquote>Native select boxes are rubbish and I have the user research videos to prove it.</blockquote>

<blockquote>Unless you have been residing under a rock for the last month (and I’m starting to wish I had been) you’ll be aware of the impending EU VAT Place of Supply change. Much of the noise has been made by those businesses who will be forced into VAT Registration because of it, and rightly so. However, for those of us who are VAT Registered and so must update our systems to cope, the issues of implementation loom large.</blockquote>

<blockquote>Crucially, if you’re rendering templates to a Style Guide and you want it to be maintainable then they can’t just be identical to your application templates, they need to be the exact same templates. This is easier said than done.</blockquote>