A List Apart

Menu

Our Blog

Quick updates and practical approaches

  • Driving Phantom from Grunt

    by Jeff Lembeck · · 3 Comments

    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!

  • Destroying Your Enemies Through the Magic of Design

    by Jenny Lam / Hillel Cooperman ·

    Hierarchical organizations large and small are rife with politics. In fact, the smaller the stakes, the more vicious they can be. Political organizations are ones where what things look like are just as, or more, important as what you actually do.

  • Knowledge vs. Intelligence

    by Anthony Colangelo · · 7 Comments

    About a week ago, I was running into major issues during development of one of my side projects. After a few nights working to resolve whatever was breaking, I was getting frustrated with my lack of progress.

  • That Pixel Design is so Hot Right Now

    by Justin Dauer · · 7 Comments

    It’s no secret that pixel art is experiencing a resurgence—just look at video games like Mojang’s Minecraft and Superbrothers’ Sword & Sworcery. Justin Dauer of The Dead Pixel Society invites you to join the fun of exploring this old-meets-new medium.

  • Overwhelmed by Code

    by Susan Robertson · · 31 Comments

    There is a constant pressure to learn new things and keep up with all the latest ideas: new frameworks, new platforms, new ideas of how to write code, they just keep coming out. In addition, the ebb and flow of what is desired from a front-end developer keeps changing. It used to be that knowing CSS and HTML was enough, then jQuery came along, then responsive techniques, then Node.js and then Angular, Ember, etc., etc., etc. That list, right there, it tires me out.

  • Why Responsive Images Matter

    by Mat Marquis · · 10 Comments

    Building enormous websites means us shifting the burden of our mistakes onto every single user that visits our site. It’s us saying that we’re willing to build something that isn’t for some users, because that’s most comfortable for us—no different from “best viewed in Internet Explorer 5.5” or “best viewed at 600x800,” but much more costly.

  • Show Your Work: Demonstrating Progress on Your Projects

    by Eileen Webb · · 11 Comments

    I’ve been thinking a lot lately about how actual progress on a project doesn’t always match the impression of progress—sometimes a lot of code has changed but nothing looks very different, while other times a small change in code gives the sense that the whole project has moved leaps and bounds.

  • An Excellent Week

    by Tim Murtaugh · · 3 Comments

    A couple of big announcements are making the rounds this week: Google advises progressive enhancement and the W3C publishes an official HTML5 recommendation.

  • The Couch Cone of Silence

    by Mica McPheeters · · 7 Comments

    About five years ago, I bought a cushy couch for my office. (Okay, yes, I did get the model that could flatten into an emergency nap station, but let’s just say that I plan for contingencies—it sounds more professional that way.) Our projects required a lot of office-to-office visiting to discuss situations in person, and eventually, said couch (and therefore, my office) became a veritable beacon, attracting anyone looking for an excuse to decompress. Such is the life of a one-couch, 50-chair business.

  • Beyond You

    by Anthony Colangelo · · 1 Comment

    In client work, it’s our responsibility to ensure that our work lives beyond ourselves. Sometimes that means making sure the CMS can handle clients’ ever-changing business needs, or making sure it continually teaches its users. For clients with an internal development team that will be taking over after you, it means making sure the design system you create is flexible enough to handle changes, yet rigid enough to maintain consistency.

The Latest Issue

Issue № 409 ·

  • Planning for Performance

    by Scott Jehl · 6 Comments

    We should build websites that are not merely responsive, but sustainable, globally accessible, and, well, responsible, as Scott Jehl suggests in his new book, Responsible Responsive Design. Our approaches to responsive websites need to consider ever-changing devices, limited networks, and unexpected contexts. In this excerpt from Chapter 3, Scott discusses page load times and the responsible delivery of code.

Recent Columns

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.

Rachel Andrew on the Business of Web Dev

Managing Feature Requests

You’re proud of your product, and welcome user suggestions on making it even better. Will you be able to make everyone happy? Should you even aim to accommodate them all? Before you start coding, think about how to prioritize feature requests, and even say no to some.