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
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.
Sara Wachter-Boettcher, coauthor of Design for Real Life, reflects on how we too easily dismiss users in crisis.
Web animation is undergoing an explosive evolution, reframing what it means to design for the web.
Brendan Murray persuasively argues that agile development is a framework within which content work can flourish.
Designers need to overcome their own predispositions to produce what’s needed for the project.