Adaptive content may just be the future of content management, but there is still no widespread agreement on what it should look like or how it is to be implemented.
After several decades of web-focused technology, we're rapidly embracing a mobile defined world. In the past five years, the use of mobile devices has been surged. According to the latest Pew Research, 63 percent of US adults use their phones to go online and 35 percent of Americans 16 and older own tablet computers.
Companies have tried to develop native apps for various mobile platforms. But the reality is that trying to wedge web tools into a mobile world is difficult and time-consuming — little more than a Band-Aid for an issue we have failed to adequately address.
"I'm calling it the hole in the web problem," Don Day, an independent structured markup expert said in an interview with CMSWire. "We've got a problem with web architecture, browsers and how we access information in databases."
Responsive web design (RWD) — the framework for websites that respond to their environments — offers some relief. As Jeffrey Veen, CEO and Founder of Typekit, said in a book by Ethan Marcotte:
Day by day, the number of devices, platforms, and browsers that need to work with your site grows. Responsive web design represents a fundamental shift in how we’ll build websites for the decade to come.”
Marcotte is credited with coining the phrase Responsive Web Design, which he introduced in his A List Apart article, "Responsive Web Design" and evolved in A Book Apart — Responsive Web Design. RWD will fluidly change and respond to any screen or device size.
What is the Difference
Both AWD and RWD allow websites to be viewed in mobile devices and various screen sizes. So what are the key differences?
"CMS tools have largely been built on a page model, not on data types," Gustafson said in an interview. "We need to be thinking more modularly about content. We need to design properties of content types rather than how it's designed."
Where responsive design is a model for addressing front end issues like fluid grids and images, adaptive design concerns back-end approaches that take into account both the form and function of a user's capabilities, he added.
Responsive design can improve how websites look on mobile devices, but adaptive design can help companies reuse existing content and allow it be viewed properly on even more devices.
One example here is an airport kiosk or a digital sign in a museum. Content that is built for the web may not look right on one of these displays unless it is adaptive. The responsive design approach may not solve this problem, but building content models that can be more easily reused in a wider variety of places could, Gustafson said.
COPE: Create Once, Publish Everywhere
Whether an adaptive design or responsive design strategy should be employed depends greatly on the context, Rahel Bailie, a content strategist, told CMSWire. Adaptive design has been the purview of web geeks for many years, Bailie said. It is becoming more mainstream now as site owners realize they have a problem that goes beyond responsive design and web content management systems (WCMS).
"Writing for the web is more than just addressing multiple channels," Bailie said. "Producing adaptive content is more a content build."
- 5 Tech Trends We'll See More of in 2014
- The Future of Collaboration Isn't What It Used to Be
- SharePoint Conference Keynote: Releases and Roadmap #SPC14
- The Fall of Collaboration, The Rise of Cooperation
- Who Leads the Big Data Market? (Probably Not Who You Think)
- If You Dress SharePoint Differently, Is it Easier to Use? #SPC14
- Navigating the Microsoft Forms Roadmap #SPC14