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 excerpt from Image Performance, Mat Marquis chronicles the pros and cons of `img` and why we needed something better.
When we put the UX at the expense of the developer experience, it’s the user who pays the price.
Stop designing for the happy path! Steven Garrity shows how to create more robust layouts by designing with difficult data.
With voice interfaces becoming the norm, semantic markup is more important than ever. Learn how HTML tags can have a huge impact.
Code suffers without clarity. Brandon Gregory illuminates some principles for organizing object-oriented code.
Help keep the web open and free! Contribute to open source projects.
In this excerpt from Flexible Typesetting, Tim Brown articulates the challenges facing the modern web typographer. (That’s you.)
Breaking down the walls between the internet’s many social silos, Webmentions offer a new level of freedom for web interactions.