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
In this installment of our “From URL to Interactive” series, Greg Whitworth explains how cascading actually works, and then some.
Continuing our “From URL to Interactive” series, the second part dives into how HTML is parsed.
The car lurches and loses all power. You coast to a stop, steam rising from the hood. So you think you know how browsers work?
Kicking off our “From URL to Interactive” series, we take a look under the hood to find out how our code makes it to the browser.
In this excerpt from Writing for Designers, Scott Kubie explains why designers need to be more intentional with how we use words.
Brandon Gregory considers how to design accessibly for cognitive differences like anxiety disorders, inattention, and depression.
It may be easy to turn your nose up at FAQs, but Caroline Roberts can help you take the simple Q&A format to the next level.
Jon Yablonski explains three key theories of psychology that designers can use to build more intuitive, human-centered products.
Fronteers, the Dutch front-end association, aims to join the W3C to represent independent web developers worldwide.