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
Workspaces now include the comforts of home, and homes are filled with devices that connect us to work. It’s time to reconsider our enthusiasm for being available to deal with work any time, day or night. The balance we thought we’d find is tipped heavily toward productivity, to the detriment of exploration, inspiration, and regeneration.
From the Blog
This week I wrote about conducting CSS audits to organize your code, keeping it clean and performant—resulting in faster sites that are easier to maintain. Now that you understand the hows and whys of auditing, let’s take a look at some more resources that will help you maintain your CSS architecture. Here are some I’ve recently discovered and find helpful.
As users we switch seamlessly between the web and apps, yet as designers and developers we huddle in separate rooms. Wouldn’t this party be livelier if we mingled?