Progressive Enhancement vs. Graceful DegradationMobile FirstResponsive Design
Which one of these is not like the others?
It is always easier to add than to take away.It’s not about sticking to “responsive” or “elastic” designs. With this many devices and apps, you do what works across the board.
Compare – is it a bug? Is it supposed to be that way? Did we do something wrong?
Jan 8 2014 NISO Webinar: Device to Device: Adaptive Interfaces for Content
Device to Device:
Adaptive Interfaces for Content
January 8, 2014
Toby Plewak - Client Strategist, Publishing Technology
Jean Kaplansky - Digital Content Solutions Architect, Aptara
From Device to Device:
Adaptive Interfaces for Content
Toby Plewak, Client Strategist
What is Responsive Web Design?
Maintain one website that serves all devices
Based on fluid, grid layouts
Layouts that adapt to fit whatever screen size
they render on
What are the advantages of RWD?
Maintain one website that serves all devices and
Provide complete support for (almost) all website
pages and features, regardless of device or
Implement changes across all devices
How does Responsive Web Design work?
Made possible by new capabilities in
CSS3, which are supported by most desktop
browsers and all mobile browsers
New concept: Breakpoints
Responsive web design is about designing SYSTEMS,
and not PAGES
From Device to Device:
Adaptive Interfaces for
Digital Content Solution Architect
NISO Webinar, January 8, 2014
Review – Responsive Web Design
Discuss – Adaptive Design in General
Discuss – Progressive Enhancement Maturity Model
Review – eBook File Formats and Vendors
Walkthrough – Progressive Enhancement for eBooks
Consider – To Fixed Layout, or not?
Progressive Enhancement for eBooks: Going from Point A to Point B
Responsive Web Design
The eBook World – Reading Systems
Adobe Digital Editions – desktop
Amazon Kindle – eInk, tablets, iOS, Android, desktop, cloud reader
Apple iBooks (universal, iPhone, iPod, iPad, OS X Mavericks)
CourseSmart – Android, iOS, desktop web browsers
Google Play Books – Android, iOS, desktop web browsers
Inkling – iPhone, iPad, Chrome web browser
The eBook World – Reading Systems, continued
Kobo – eInk, Tablets, Android and iOS apps, cloud reader
Nook Media – eInk, Tablets, Android and iOS apps, Windows 8 app
Readium – Chrome Browser
Sony Reader – Android, iOS, Windows, Mac
Vital Source Bookshelf – iOS, Android, desktop browsers
Goal: Progressive Enhancement for eBooks
One reflowable EPUB for all vendors is possible.
Starting from the simplest form and working up from there.
– Fluid Grid
– Flexible Images
– Media Queries
But first… A few words about
fixed layout eBooks
To produce fixed layout or reflowable texts? This is THE question.
To Fixed Layout?
Fixed layout is always appropriate for:
Children’s picture books
Manga, Comics, and graphic novels
Illustrated titles requiring print replication to preserve EXTREME design
– Illustrated Textbooks
– “Coffee table” art books
– Gift books
…or NOT to Fixed Layout?
Reasons to consider reflowable text:
Fixed layout may limit distribution options.
Fixed layout may interfere with device and reading system (app) user
– Font and font size
– Space between lines
– 1-up or 2-up (may be based on orientation)
– Live text searching
Reasons to consider reflowable text, continued.
Pinch and zoom is a painful user experience for text heavy publications.
More cost effective than fixed layout.
Easier to produce, thus accommodates tight production schedules.
But… What about my tables? And my high res images?
Welcome to the world of Responsive Web Design!
Tables may require review to establish whether the content really is best
presented as a table.
Images – both high and low resolution contribute to the overall “payload”
of an eBook.
Have you done everything you can to facilitate accessibility?
Going From Point A to Point E
A. Plan content structural semantics (HTML5)
– HTML5 provides built-in accessibility.
– HTML5 easily adjusts and adapts as the basis of most eBook file
B. List all target devices and reading system apps
– Collect vendor specifications, guidelines, and examples.
– Lay hands on each device required. Emulators aren’t good enough.
C. Plan approach to CSS
– Follow CSS best practices wherever possible
– Consider using a preprocessor (e.g., Sass - http://sass-lang.com/)
Going From Point A to Point E, continued.
D. Build EPUB files
– Remember to use EPUB metadata wherever possible
– Apply semantic inflection through the EPUB Structural Semantics
E. Test, adjust, test again, wash rinse repeat.
Plan content structural semantics (HTML5)
What objects are in your content?
How will you map and convert existing content to your new HTML5
Content Architecture Example: Sidebar
<aside epub:type="sidebar" class="sidebar" id="ch03sb002">
<h1 id="ch03sb002.title" class="title" epub:type="title">
<span class="label">A Teacher’s Voice: </span>
Creating Classroom Community</h1>
<p>Creating a classroom community is an important part of what I
do. Each year the mix of children-their strengths, needs, and
personalities, is different. I want children to learn to value
their classmates for who they are. I want them to be respectful
and kind and realize that every person has something to offer.
As the group forms over the course of the year, and we work through
accepting the “hard to like” ones and appreciating ourselves and
each other for our strengths and challenges, I find great joy in
the moments when children reach out to each other, share, encourage
and collaborate, or defend a classmate.</p>
Content Architecture Example: Figure
<img src="images/ch02fig03test.png" alt="Two neurons figure"/>
<h1 class="title" epub:type="title">
<span class="number">2.3 </span>Two neurons,
an astrocyte, and their interconnections</h1>
<p>This is the caption text</p>
<p><span class="label">Source: </span>This is the
List all target devices and reading system apps
Don’t forget cross platform apps
Plan Approach to CSS
Build EPUB Files
Potential Development Tools
– oXygen XML
– Bluegriffon EPUB Edition
– Text Editors
– HTML IDE’s
– CSS Editors
Approaching eBook production with a mind toward Progressive
Enhancement is possible – but your mileage will vary.
Carefully consider the pros and cons before deciding to produce fixed
layout publications over reflowable titles.
Get your hands on the target devices. Emulators are not as reliable as
the devices themselves.
There’s a very good reason to use the new semantic markup in HTML5
The Open Web Platform enables the eBook Progressive Enhancement
Good things come to those who PLAN.
Looking for a Semantic Content Model for your eBooks?
Device to Device: Adaptive Interfaces for Content
All questions will be posted with presenter answers on
the NISO website following the webinar:
NISO Webinar • January 8, 2014
Thank you for joining us today.
Please take a moment to fill out the brief online survey.
We look forward to hearing from you!