A List Apart

Menu
Issue № 193

What’s the Problem?

by Tim Meehan, Norm Carr33 Comments

Freud asked, “What does a user really want?” Ten-plus years into web development, we still don’t know. One of the biggest problems in creating and delivering a site is how to decide, specify, and communicate exactly what we’re building and why. Use cases can help answer these questions by providing a simple, fast means to decide and describe the purpose of your project. In this quick-reading article, Messieurs Carr and Meehan introduce use cases and their, uh, uses.

More from A List Apart

Columnists

Matt Griffin on How We Work

Being Profitable

So you own a business. It’s the best job you’ve ever had, and it will be forever—as long as the business stays viable. That means understanding when it's profitable, and when you may have to make some adjustments. Don’t worry—it doesn’t require an accounting degree and it won’t turn you into a greedy industrialist.

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.