For years, we've been telling designers: the web is not print. You can't have pixel-perfect layouts. You can't determine how your site will look in every browser, on every platform, on every device. We taught designers to cede control, think in systems, embrace web standards. So why are we still letting content authors plan for where their content will "live" on a web page? Why do we give in when they demand a WYSIWYG text editor that works "just like Microsoft Word"? Worst of all, why do we waste time and money creating and recreating content instead of planning for content reuse? What worked for the desktop web simply won't work for mobile. As our design and development processes evolve, our content workflow has to keep up. Karen will talk about how we have to adapt to creating more flexible content.
3. “
Fragmenting our content across
different “device-optimized”
experiences is a losing proposition,
or at least an unsustainable one.
—Ethan Marcotte
Responsive Web Design
4. “ You can’t afford to create a piece of
content for any one platform.
Instead of crafting a website, you
have to put more effort into crafting
the description of the different bits
of an asset, so they can be reused
more effectively, so they can deliver
more value.
—Nic Newman, BBC
Nimble Report, http://nimble.razorfish.com
10. We’re about to usher in a golden age
of PDFs on the iPad.
Paul Ford, @ftrain
11. “ Existing art and production staffers
from the print side would be
responsible for making two iPad
layouts (one in portrait and one in
landscape) on Adobe’s platform.
—Condé Nast Is Experiencing Technical Difficulties
http://www.observer.com/2011/07/scott-dadich-ipad-conde-nast/?show=all
12. All I see is an
entire organization screaming,
“WE WANT IT TO BE THE EIGHTIES
GODDAMMIT.”
Condé Nast Is Experiencing Technical Difficulties
31. “
Over the last year, NPR’s total page
view growth has increased by more
than 80%.
How did we get that much growth?
Our API.
—Zach Brand,
Senior Director Technology, NPR
32. “
The biggest impact that the API has made,
however, is with our mobile strategy. The
API has enabled NPR product owners to
build specialized apps on a wide range of
platforms and devices, liberating them
from being dependent on custom
development to access the content.
Through this process, we built our iPhone
and iPad apps, mobile sites, Android app
and HTML5 site, some of which were
turned around in a matter of weeks!
37. Thinking about where content will “live”
on a “web page” is pretty 1999.
Lisa Welchman, @lwelchman
38. MOBILE
WEB MOBILE
WEBSITE
APPS
SOCIAL TABLET
MEDIA APPS
PRINT
MICROSITES PRINT
BLOGS EMAIL
INTRANET
39. MOBILE
WEB MOBILE
WEBSITE
APPS
SOCIAL TABLET
MEDIA APPS
WEB
MICROSITES PRINT
BLOGS EMAIL
INTRANET
40. MOBILE
WEB MOBILE
WEBSITE
APPS
SOCIAL TABLET
MEDIA APPS
MOBILE
MICROSITES PRINT
BLOGS EMAIL
INTRANET
41. MOBILE
WEB MOBILE
WEBSITE
APPS
SOCIAL TABLET
MEDIA APPS
CONTENT
MICROSITES PRINT
BLOGS EMAIL
INTRANET
42. “ Traditional publishing and content
management systems bind content
to display and delivery mechanisms,
which forces a recycling approach
for multi-platform publishing.
—Dan Willis
http://dswillis.com/uxcrank/?p=378
43. “ A semantic content publishing
system creates well-defined chunks
of content that can be combined in
whatever way is most appropriate
for a particular platform.
All display issues are addressed by
delivery applications, rather than by
a content management system
earlier in the process.
http://dswillis.com/uxcrank/?p=378
61. “
Beautiful software, even for back-end
users, is becoming an expectation.
We’re moving in this direction
because we now understand that
better content management systems
foster better content.
—Matt Thompson
http://www.poynter.org/how-tos/digital-strategies/134791/4-ways-content-management-systems-are-evolving-why-it-matters-to-journalists/