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
Working with a team of like-minded folks not only makes for more copacetic daily interactions, it actually has a positive effect on the end product. Developers are valued for more than their technical skills. Another hallmark of a good developer is how well they mesh with a team.
From the Blog
I’m trying to be learn more about accessibility these days. Thinking about it more, reading about it some, and generally being aware as I write code what I should and shouldn't do in that arena.
A new edition of Responsive Web Design is here. To celebrate, A List Apart’s editor-in-chief, Sara Wachter-Boettcher, sat down with author Ethan Marcotte to talk about what’s new—and what’s next.