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
Tech leadership is the skillful combination of technical expertise and the best management principles.
To get the web where it needs to go we have to do it wrong first.
An open call to the web community to pull together and give back to our colleague and friend Carolyn Wood.
A system’s success is all about how you define and message it, says Nathan Curtis.
Remy Sharp brings the love by adopting some tools to make newcomers more comfortable contributing to open source projects.
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.