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
Big value user research doesn’t need big pots of resource, just clear process, well-directed focus, and care with data analysis.
As products and services move online, dependence on component libraries can create a pattern of missing the forest for the trees.
In this excerpt from Orchestrating Experiences, you’ll learn about weaving touchpoints together into a seamless experience.
ALA’s Zeldman bemoans our industry’s fetish for the needlessly complicated over the straightforward.
Samantha Lynn weighs in on 20 years of ALA, 350 articles, and how far we’ve come as an industry.
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.