A List Apart

Menu

The Articles

Issue № 389

  • Designing for Easy Interaction

    by Sarah Horton, Whitney Quesenbery · · 16 Comments

    Whether you contribute to the user experience, development, or strategy of your website, you have a business, ethical, and (in many cases) legal responsibility to make your site accessible. And an equally compelling duty to your stakeholders, creativity, and career to achieve accessibility without sacrificing one whit of design or innovation. So what’s a site and application maker to do? For starters, read this book! We are thrilled to present an exclusive excerpt from Chapter 5 of A Web for Everyone: Designing Accessible User Experiences by Sarah Horton and Whitney Quesenbery, available now from Rosenfeld Media—and with a 20 percent discount for ALA readers, even.

Issue № 388

  • A List Together

    by Mat Marquis · · 21 Comments

    A List Apart gets back to its roots: building community, giving a platform to new voices, and getting people excited about the web. We’re making changes to the way we work—starting with our decision to open-source the code that powers alistapart.com itself—and we want you to participate. Our Mat Marquis invites you to contribute code and concepts via GitHub, get to know our acquisition scouts, and use ALA and its editors to share your ideas and insights with the whole web design and development community.

  • Writing Is Thinking

    by Sally Kerrigan · · 27 Comments

    When you write about your work, it makes all of us smarter for the effort, including you. Done well, this kind of sharing means you’re contributing signal, instead of noise. But writers are made, not born. We often hear from people who say they’d love to write for A List Apart or start blogging, but don’t know where to start. They feel unfocused and overwhelmed by the task. If this is beginning to sound like you, read on, as Sally Kerrigan walks you through how writing works, and how you can get better at it.

Issue № 387

  • A Moment to Breathe

    by Nick Cox · · 29 Comments

    Burning both ends of the candle night after night, weekend after weekend, has long been part of web design and development culture. Especially in the startup subculture, we pride ourselves on working long hours with little sleep. It’s part of a new generation’s favorite myth—the one where we get in early in a company destined for an enormous IPO, work our little hearts out for a year or two, and end up rich and happy. The truth is rather less glamorous: the way we are working starves our prefrontal cortex, hurting not only our precious health, but also our productivity. Nick Cox shares the science behind the high cost of constant crisis mode, and explains how to strike a better balance.

Issue № 386

  • Surveying the Big Screen

    by Mike Pick · · 23 Comments

    We’ve been designing responsively for more than three years, now, and have the small-screen pattern libraries and portfolios to prove it. But what about larger screens? While we commonly use liquid design for smaller breakpoints, allowing our content to expand and contract as needed, few of us consider what happens beyond a maximum width of 960 pixels or so—which can leave a heap of unused pixels on a contemporary desktop display. Mike Pick explores how to use negative space, scale, density, and layout devices such as grids, modules, and columns to break through the 1024-pixel layout barrier.

  • Designing Offline-First Web Apps

    by Alex Feyerke ·

    We assume our users are like us—with the latest devices, the most recent software, and the fastest connections. And while we may maintain a veritable zoo of older devices and browsers for testing, we spend most of our time building from the comfort of our modern, always-online desktop devices. But what happens when our users descend into the subway, board a plane, go to live in the country, or just happen to find themselves in the wrong corner of the room? The truth is, offline is a fact of life—but there are ways to design for it. Alex Feyerke tells all.

Issue № 385

  • Why Sass?

    by Dan Cederholm · · 64 Comments

    “I was a reluctant believer in Sass. I write stylesheets by hand! I don’t need help! And I certainly don’t want to add extra complexity to my workflow. Go away!” So says designer, CSS wizard, and Dribbble co-founder Dan Cederholm at the beginning of his new book Sass For Web Designers, released today by A Book Apart. Yet the reluctant convert soon discovers that the popular CSS pre-processor can be a powerful ally to even the hand-craftiest front-end designer/developer. Dan has never learned a thing about CSS he wasn’t willing to share (and great at teaching). And in this exclusive excerpt from Chapter 1 of Sass For Web Designers, you’ll get a taste of how Dan learned to quit worrying and use Sass to take better control of his stylesheets and websites.

Issue № 384

  • Flat UI and Forms

    by Jessica Enders · · 74 Comments

    Though some decry flat user interfaces as pure fashion, or as the obvious response to skeuomorphic trends, many designers have embraced the flat approach because the reduction in visual styling (such as gradients, drop shadows, and borders) creates interfaces that feel simpler and cleaner. Trouble is, most flat UIs are built with a focus on the provision of content, with transactional components (i.e., forms) receiving very little attention. So what happens when flat UIs and forms collide? User experiences can, and often do, suffer. Keep your flat forms from failing by using controlled redundancy to communicate difference.

  • Mastering Digital Project Momentum

    by Perry Hewitt · · 12 Comments

    Digital projects begin in high spirits and tip quickly into miscommunication and crisis. But it doesn’t have to be that way. Extend your early kickoff meeting harmony throughout the life of your projects. By understanding your client’s organizational drivers and key players before the sticky note sessions even begin, you can establish the momentum needed to keep the extended team focused on goals. And by managing stakeholder communications throughout the job, you can avoid land mines, save time and effort in the long run, and deliver a project that satisfies stakeholders, agency, and users alike.

Issue № 383

  • Sustainable Web Design

    by James Christie · · 46 Comments

    Do you know your website’s carbon footprint? Or how to lower it? Emissions standards have been set for the automotive, construction, and telecommunications industries, yet the internet’s carbon footprint is growing out of control: a whopping 830 million tons of CO2 annually—larger than that of the entire aviation industry. At least 40 percent of that falls partially under the responsibility of people who make websites. It’s time for web designers to do our part. James Christie explains how to slim our obese websites and simultaneously attack our industry’s carbon footprint, using methods that conveniently dovetail with good business practice and future-friendly design.

  • The Web Runs on Electricity and We’re Running Out

    by Dorian Peters · · 20 Comments

    It’s a humbling thought, but as web professionals, nothing we create actually exists when the power goes out. As we increase the number of devices in our world, planning for a connected web of things in hopes that the poor will be liberated, education will be free, and our fridges will tell us we’re out of lettuce, we fail to acknowledge that we scarcely have enough fossil fuels to maintain the current state for long. Web designers need to be part of the solution—and the situation is more hopeful than you may think. Dorian Peters shows how we can exercise the surprising power that lies in seemingly small designerly decisions to help our industry not only survive, but create positive impact worldwide.

Issue № 382

  • Interviewing Humans

    by Erika Hall · · 7 Comments

    The humble one-on-one interview is the basic unit of ethnographic research. The price is right for even the most cash-strapped team, and with practice (plus a few principles) you can gain the knack for it—even if “researcher” is the one title that doesn’t appear on your business card. The great myth is that you need to be a good talker. But conducting a good interview is actually about shutting up. Learn to coax good data from willing humans in our excerpt from Erika Hall’s new book, Just Enough Research.

Issue № 381

  • Connected UX

    by Aarron Walter · · 26 Comments

    Your inbox overflows with customer emails suggesting features and improvements. Instead of benefiting, you feel overwhelmed by an unmanageable deluge. You conduct usability tests, user interviews, and competitive analyses, creating and sharing key insights. Yet within months, what you learned has been lost, forgotten, or ignored by someone in a different department. What if you could sift, store, and share all your customer learning in a way that breaks down silos, preserves and amplifies insights, and turns everyone in your organization into a researcher? MailChimp’s user experience director Aarron Walter tells how his team did it. You can, too.

  • Seeing the Elephant: Defragmenting User Research

    by Lou Rosenfeld · · 11 Comments

    Silos: good for grain, awful for understanding customer behavior. Just as we favor the research tools that we find familiar and comfortable, large organizations often use research methods that reflect their own internal selection biases. As a result, they miss out on detecting (and confirming) interesting patterns that emerge concurrently from different research silos. And they likely won’t learn something new and important. IA thought leader Lou Rosenfeld explains how balance, cadence, conversation, and perspective provide a framework enabling your research teams to think across silos and achieve powerful insights even senior leadership can understand.

Issue № 380

  • Getting to Flow

    by Breandán Knowlton · · 5 Comments

    When design and client cultures truly come together, magical and memorable projects emerge. These magic projects aren’t random, though—they happen when you reach a state of flow. The beautiful part is, you can get both yourself and your client into a flow state more often by doing three things: enabling immediate feedback, balancing capability and challenge, and setting clear goals with visible progress. Breandán Knowlton shows you how.

  • Defining a Vision: Making Sure Your Work Matters

    by Russ Starke · · 2 Comments

    When an architect designs a structure, he or she can be fairly sure the work will endure for decades, maybe even centuries. Here on the web, we’re not so lucky. Knowing how temporary digital creations can be, how can we ensure our work matters? By defining the organization's vision. This isn’t just about solidifying a mission statement, though. Russ Starke shows you how to help organizations create a detailed story of their future success—and how that story can serve as a compass for both the company and its customers.

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.

Recent Blog posts

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!

Overwhelmed by Code

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

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.

The Couch Cone of Silence

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.