Be the first to like this
Okay, we get it. No more blobs. Make things chunky. Separate content from code.
But this is easier said than done.
Most content professionals work with small budgets or cope with big bureaucracies. We can't move forward on ideals alone. We need practical approaches (and dare we say, compromises) for implementing adaptive content in our day-to-day jobs. Instead of discussing in vain how to build perfect solutions, let's look closely at real-world case studies of people who have made tough calls and tradeoffs to move toward adaptive content in ways that solved actual problems.
Adaptive content requires a cultural shift in thinking, and along the way, we need to be able to allow ourselves some tradeoffs. Many situations today cannot realistically support, or even require, the chunkiest solution possible. When could a little WYSIWYG sometimes be a good thing? Is it heresy to allow the errant blob into your content management system for a special use case? As we defend the purity of content, it's also our responsibility as strategists to empower content creators to do their jobs well. Sure, the larger theory is exciting to think about, we'd like to talk more about the things we can actually start doing when we arrive to work the next morning.