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
Play to your strengths, and outsource everything that slows you down or makes you less productive.
Transform your weblog into a lead generating machine.
Converting existing designs to Grid without breaking in non-grid browsers
Ensure design choices trace back to specific objectives
Stop hawking design like it was a household gadget that needs upgrading and start building relationships instead.
Web-based data visualizations take UX to a new level.
Just because your users don’t ask for help doesn’t mean they don’t need it.
Avoid common performance issues by teaching your site how to adapt.
HTTP/2 challenges how we optimize sites for users