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
Building an API? Software documentation expert Diana Lakatos has some great advice for you.
Staffing teams can feel a bit like a game of Tetris, but don’t forget your teams are human beings.
If you volunteered to help A List Apart and haven’t heard back from us yet, here’s what’s up.
We’re pleased to share an excerpt from Chapter 2 of Rachel Nabors’s new book, Animation at Work.
As ALA nears its 20th anniversary, we’re reimagining the magazine. We want your feedback. And most of all, you.
Key to hiring technical talent are a clear view of the role and the ideal candidate.
Most websites—and, more importantly, their readers—can benefit from becoming PWAs. And it’s so easy!
Variable fonts give us a new, wide open typographic space with which to work.
A cohesive animation system can help express a product’s personality and make the interface feel connected and whole.