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
Oliver Williams argues that we can and should develop websites for modern browsers without leaving IE users behind.
Want to write a professional article? ALA’s own Brandon Gregory gives some advice on common pitfalls in submissions.
Come share with us! Our industry-leading editors, tech editors, and copy editors are ready to help you polish your best idea.
Little-known, yet highly effective, priority guides are the content-first, responsive alternative to the ubiquitous wireframe.
We think of our job as controlling the user’s experience. But the reality is, we control far less than we imagine.
Can’t hire a full-time user researcher? Here’s how to make the most of your time and money when hiring one on a project basis.
In this excerpt from Going Offline, Jeremy Keith introduces us to Service Workers, a critical component of Progressive Web Apps.
In this excerpt from Planning for Everything, Peter Morville shares insights about how reflection can improve our work.
We’re delighted to share this excerpt from Meeting Design by Kevin Hoffman.