As we attempt to combine multi-device design requirements with complex, media-rich narratives, we’ve hit the wall. The chunky, fields-and-templates approach we’ve developed can’t save us from the mismatch between our content and HTML’s descriptive tools. The good news is we don’t have to convert all our projects to XML to learn from the XML community’s wisdom. By using custom elements and properties to represent content’s meaning, transforming it into HTML on output, and ensuring that editing tools share the same vocabulary, we can publish structured content that supports the needs of today’s editors and art directors while also making our content safe for future generations.
More from A List Apart
Business communications benefit from better, tighter delivery—a technique we learned from fairy tales, Anne Gibson reminds us.
The same typefaces crop up everywhere on the web. But why? Jeremiah Shoaf thinks the answer might lie in cognitive biases.
User testing is a necessary part of the design process, not a luxury.
Tim Baxter encourages us to move beyond the “measles of markup” to write rich, semantic HTML and CSS. Only habit is stopping us.
Before you plan the trip, make sure you know who’s coming. Sophia Voychehovski tells us why action-first design is risky business.
Seeing clients as clueless or “difficult” is a red flag—for us. How to turn client confusion into better experiences.
Translate analytics into product paths with narrative structures. New excerpt from Donna Lichaw’s The User’s Journey.
In an excerpt from Design for Real Life, Eric A. Meyer and Sara Wachter-Boettcher discuss designing for stress cases.