Sass

Setting the scope for Loom

Submitted by sonniesedge on Sat, 10/08/2016 - 13:30

Writing the core of Loom has been extraordinary fun, and I'll be sharing some of the thought processes and techniques behind it with you.

So what did I want from a new framework?

Introducing Loom

Submitted by sonniesedge on Mon, 10/03/2016 - 12:00

So, I thought it'd be a great idea to write my own CSS framework. This is the kind of thinking that occurs when I've had too much caffeine (file this alongside my other caffeine-based projects, such as "Why not repaint the apartment?" and "Try abseiling down an industrial chimney").

I was inspired by writing an in-house framework for a previous client. It was eventually used on several major projects, but was relatively inflexible, written as it was for one use-case and for a certain way of writing code.

Migrating your team to Sass

Submitted by sonniesedge on Tue, 11/04/2014 - 11:00

Having read all the articles, watched all the talks, and used it on your own personal projects, you've decided to start using Sass in your workplace. Congratulations! But now you've got the job of actually implementing it in your team.

Oh boy.

This article will give you the lowdown on ensuring the migration goes smoothly. It will show that the move to Sass isn't just about Sass, as lovely as it is. In reality the move is just as much about team culture and making the best use of supporting technologies.

Inlining critical CSS

Submitted by sonniesedge on Mon, 10/27/2014 - 11:00

Lately I've been playing with LoadCSS from Filament Group. It's a wonderful system for asynchronously loading CSS, therefore removing a blocking resource from your page loads.

The only snag I've hit with it is the FOUC - a Flash Of Unstyled Content, caused by the HTML of the site loading before the heavier CSS asynchronously loads. To get around this there are known techniques for inlining critical CSS in the header of a page.

Using Bootstrap on a large site

Submitted by sonniesedge on Thu, 09/25/2014 - 11:00

It's fair to say that Bootstrap has a poor reputation in modern frontend circles. "It's bloated! It's redundant! It makes every site look the same!", shouts the Bearded Developer, "Roll your own damn solution!"

But it's not always that simple, is it?

Bypassing Jekyll via Grunt

Submitted by sonniesedge on Sat, 09/06/2014 - 11:00

Like many front-end people, I find myself mostly working on stylesheet files, rather than the actual HTML structure of a site.

My build process is pretty basic - Grunt Watch is running and upon detection of a change to the site's file structure it builds out the site, and triggers a livereload event. This is ace, and lets me work in my editor, while watching the changes occurring in all devices currently accessing that page.

Subscribe to Sass