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
Be patient, be smart, and above all persevere. Janice Gervais guides us through guerrilla innovation in the workplace.
Encourage people to shine in their brilliance, but make sure your product also helps them avoid being petty or awful.
Culture fit in hiring limits perspective, and that inhibits a team’s problem-solving abilities.
Pesky nesting issues are a thing of the past if we envision web content blocks as the tops of Lego bricks.
The inside-out path to becoming a public speaker
Issues underlying workplace drama aren’t totally random—Brandon Gregory shows us how to stabilize ourselves and our relationships.
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.