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
Partners in a small, close leadership team—such as in a family business—often know each other’s minds very well, and agree on most things. That’s great to keep things running smoothly (though sometimes there’s awkwardness when business disagreements intrude on home life). On the other hand, it can also lead to stagnation. Rachel Andrew is finding that an outsider’s perspective can help when partners can’t quite see eye to eye—or when they agree too much.
From the Blog
Why did we all start using
btn? Anthony Colangelo considers whether a lack of clarity is worth the benefits of a shorter class name, of brevity, in our code.
A decade ago here in A List Apart, we published a radical article by Peter-Paul Koch arguing for custom attributes in markup. Today, Mat Marquis takes a look back at how times have changed, and shows how PPK’s idea has worked its way into the web.