A List Apart

Menu
Issue № 241

Never Use a Warning When you Mean Undo

by Aza Raskin · 81 Comments

Are our web apps as smart as they should be? By failing to account for habituation (the tendency, when presented with a string of repetitive tasks, to keep clicking OK), do our designs cause people to lose their work? Raskin's simple, foolproof rule solves the problem.

Conflicting Absolute Positions

by Rob Swan · 77 Comments

All right, class. Using CSS, produce a liquid layout that contains a fixed-width, scrolling side panel and a flexible, scrolling main panel. Okay, now do it without JavaScript. By chucking an assumption about how CSS works in browsers, Rob Swan provides the way and means.

More from A List Apart

Columnists

Matt Griffin on How We Work

Pricing the Web

If you plan to bill your clients, you need a method for putting a price on what you do. The variables are always money, time, and scope of work, but the way they relate to each other can bring different client motivations to the foreground and fit different agency needs.

From the Blog

Driving Phantom from Grunt

For this example, we're going to build a Grunt task that takes a screen shot of the pages we're building (similar to Wraith, but far less advanced). There are multiple parts to make this work, so let's break it down. First, we will write a PhantomJS script that renders each page. Second, we make a NodeJS function that calls this script. Finally, we make a GruntJS task that calls that Node function. Fun!