A List Apart

Menu
Issue № 1

Where we started, what it's all about.

Writing for the Web

by Jeffrey Zeldman1 Comment

When Brian and I launched the original LIST APART in January '98, we had two goals: to create a noise-free, high-level discussion list for the web; and to cover all the bases of webmaking – from pixels to prose, coding to content. Posts in the digest have begun that work. It continues with this article, the first in a series. The scarcity of online writing about online writing is baffling when you consider that most websites consist of words.

Redefining Possible

by Lance Arthur

I come to stir up the quiet, solemn waters of backwards compatibility and lowest-common denominator coding. I come not to praise one-size-fits-all site design, but to demean it. I am here before you today shielded with tomato-proofed Teflon coating, ready for the shouts of indignation and hurled epithets from you in the front row while all you quiet types in the back nod your heads in silent agreement because I want you to go out now and f*ck sh*t up.

More from A List Apart

Columnists

Laura Kalbag on Freelance Design

I Don’t Like It

The most dreaded of all design feedback is the peremptory, “I don’t like it.” Rather than slinking back to the drawing board, it’s important to get clarity on what the client is reacting to. Guiding this conversation can turn a show-stopper into a mutual win.

From the Blog

Ten CSS One-Liners to Replace Native Apps

Håkon Wium Lie is the father of CSS, the CTO of Opera, and a pioneer advocate for web standards. Earlier this year, we published his blog post, “CSS Regions Considered Harmful.” When Håkon speaks, whether we always agree or not, we listen. Today, Håkon introduces CSS Figures and argues their case.

Longform Content with Craft Matrix

Jason Santa Maria recently shared some thoughts about pacing content, and my developer brain couldn’t help but think about how I’d go about building the examples he talked about. The one fool-proof way to achieve heavily art-directed layouts like those is to write the HTML by hand. The problem is that content managers are not always developers, and the code can get complex pretty quickly. That’s why we use content management systems—to give content managers easier and more powerful control over content.