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
No matter what your dev job description is, you need a robust and reliable system for note-taking, bookmarking and—this part is essential—finding the information you’ve captured. Even before you’ve built up your skills, a mature process for managing the information involved in your work will help throughout your career. Mark Llobrera likes to keep his memory management method simple, searchable, and software-independent.
From the Blog
Everyone talks a lot about empathy, but distilling that theory-driven talk into practices for our day-to-day work can seem daunting. Susan Robertson shows how she's been able to practice empathy for users as a developer.
This week's recommended reading list has bad news for icon fonts: we learn from Seren Davies' presentation that they present accessibility issues for people with dyslexia. Plus: our favorite tech TinyLetter, the NYSE computer glitch, an animal gif, and more.