Tag Archives: content

Should Lorem Ipsum Die?

Last month, Paul Souders posted a piece that was one-part futurism, one-part opinion, one-part rant, entitled: “Content-first design ain’t herding cats.” He raises a handful of design trends and then makes leaps to what he perceives to be the best responses.

Amidst some of the all-caps and bolded pieces is the underlying premise that content should always drive design, and thus, the content should be present before the design is done. Not necessarily a revolutionary sentiment, but certainly an admirable one — sort of the web design version of form following function.

In practice, though, it seems like it’s a goal but not often the reality. Usually, content is getting reworked (or generated) as the design is being done as well. So Souders’ contention that we should “[k]ill Lorem Ipsum for good” might ignore how projects tend to work. Or at least how they’ve tended to work in our experience.

That’s not to say design drives content — quite the opposite. But often, a design framework will be in place well before the content is “done” (put in quotes because when is content ever really done?). When the content is ready to go into production, there are often tweaks and alterations to the design. But to hold one up altogether for the other would extend project lifespans considerably.

Other responses are predicated on the idea that walled gardens and Instapaper will be the primary way we view content in the future — web scrapers that take someone else’s content and puts it in their display. I’m not so sure about that future, both for copyright and commercial reasons. Big brands aren’t going to want some third-party app effectively removing their specific brand pieces (trade dress), nor will they stand for it for long, if it threatens to become ubiquitous.

Further, it’s difficult to see how the Instapapers of the world would handle more intrinsically dynamic content, where design necessarily is a bit removed from content because the content can vary.

Thinking hard about content before thinking hard about design is a good idea. A great idea, even. Holding up the design process until the dots and twiddles are done to accommodate a scaper-driven future? I’m not convinced.