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
Eleanor Ratliff reflects on what happens when a design solution over here creates a new problem over there.
We need to build core development principles into our workflows by default, insists Kendra Skeene. Every single time.
The rich web is coming to email. Jason Rodriguez gives us the lay of the land and sweeps us into the future.
In A/B testing as in athletics, intuition and effort will only go so far — a champion uses advanced analysis and big data to win.
A UX gig for a hospital turned into an unexpected insight: in the realm of emotions, digital and bricks and mortar become one.
Challenging our own beliefs helps us validate situations.
Fresh and fluid design communities need builders, not takers
Patrick Clancey plies a creative use of mod queries and range selectors to change the layout of elements in lists.