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
Resources may be limited, but that doesn’t mean you have to drop the all-important discovery phase when planning a new venture.
Manuel Matuzovic explains why and how to up your accessibility game.
Aimee Gonzalez reflects on a difficult user migration project that led to a dramatic shift in how she approaches her work.
We’re pleased to offer this selection from CSS: The Definitive Guide, 4th Edition.
Can learning chess make you a better designer? Erik Kennedy believes it can. Find out how.
A List Apart thinks we should be talking more about mental health. Five people who make websites share their stories.
So you need to bring on an external user researcher to your team. How do you get started?
The all-too-common FAQ is the antithesis of effective user experience, but it’s easy to avoid (or improve) with a little guidance.
Mutation can change objects in unexpected ways. Knowing how it works—and how to prevent it—keeps unintended side effects at bay.