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
Your users evolve, which mean your user personas should evolve as well.
The way of the web now means adapting to ever-multiplying forms of input.
Enjoy travel while staying healthy and productive with great tips from road warrior Rachel Andrew.
Sheer willpower isn’t necessarily the best way for knowledge workers to approach fitness, suggests Chen Hui Jing.
A Maintain-Repair-Overhaul plan isn’t just for valuable physical assets—digital MRO keeps websites tuned between redesigns.
Tech leadership is the skillful combination of technical expertise and the best management principles.
To get the web where it needs to go we have to do it wrong first.
An open call to the web community to pull together and give back to our colleague and friend Carolyn Wood.
A system’s success is all about how you define and message it, says Nathan Curtis.