<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style><head>
<style></style>
<table class="backgroundTable" width="100%" cellpadding="0"
cellspacing="0" bgcolor="#ffffff">
<tbody>
<tr>
<td valign="top" align="left">
<table cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td style="border-top: 0px solid rgb(0, 0, 0);
border-bottom: 1px solid rgb(255, 255, 255);
background-color: rgb(255, 255, 255); text-align:
center;" align="center"><span style="font-size:
10px; color: rgb(96, 96, 96); line-height: 200%;
font-family: verdana; text-decoration: none;">Email
not
displaying correctly? <a
href="http://www.oplin.org/4cast/"
style="font-size: 10px; color: rgb(0, 0, 255);
line-height: 200%; font-family: verdana;
text-decoration: none;">View
it in your browser.</a></span></td>
</tr>
<tr>
<td style="border-top: 0px solid rgb(51, 51, 51);
border-bottom: 0px solid rgb(255, 255, 255);
background-color: rgb(255, 255, 255);">
<center><a href=""><img id="editableImg1"
src="cid:part2.04030708.08050907@oplin.org"
title="OPLIN" alt="OPLIN 4Cast" align="middle"
border="0"></a></center>
</td>
</tr>
</tbody>
</table>
<table style="width: 763px; height: 877px;" cellpadding="20"
cellspacing="0" bgcolor="#ffffff">
<tbody>
<tr>
<td style="font-size: 12px; color: rgb(0, 0, 0);
line-height: 150%; font-family: trebuchet ms;"
valign="top"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"
bgcolor="#ffffff">
<p><!-- Make sure you modify the 4Cast title in this section -->
<span style="font-size: 20px; font-weight: bold;
color: rgb(0, 0, 0); font-family: arial;
line-height: 110%;">OPLIN 4cast #339:
Smart(phone) websites</span><br>
<!-- Make sure you modify the date of the 4Cast in this section -->
<span style="font-size: 11px; font-weight: normal;
color: rgb(102, 102, 102); font-style: italic;
font-family: arial;">June 19th, 2013</span></p>
<!-- Begin copy of Web Source here -->
<p style="text-align: justify;font-size: 16px;
font-family: arial; line-height: 110%;"><img
alt="google mobile"
src="cid:part4.09060204.09020507@oplin.org"
height="120" width="68" align="left">Google has
a lot of power to control which websites receive
web traffic and which don't, simply by altering
the way they present search results. In the past
month or so, it has become clear that Google wants
to advance the development of websites that
efficiently handle traffic from mobile devices.
One way they intend to do this is by lowering the
search rankings of websites that improperly
redirect mobile users to special web pages or
error pages, rather than using something like
"responsive web design" (RWD), which automatically
adapts the layout of a page depending on the type
of device accessing it. Does your library's
website handle mobile users properly?
</p>
<div> </div>
<ul style="text-align: left;">
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://readwrite.com/2013/05/15/now-google-wants-to-kill-the-mobile-web">Now
Google wants to kill the mobile web</a>
(ReadWrite/Owen Thomas) "You know those clunky,
stripped-down versions of sites with addresses
that tack an 'm.' onto the beginning, and serve
up a dumbed-down, limited version of their
content? If Google has its way, those sites are
headed for the dustbin of history. At I/O,
Google's developer conference held this week in
San Francisco, executives Sundar Pichai and
Linus Upson showed off examples of websites that
traveled smoothly from desktops to tablets to
smartphones."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://techcrunch.com/2013/06/12/google-fixes-mobile-web/">Thank
you, Google overlords</a> (TechCrunch/Sarah
Perez) "If you've at all used the web on your
smartphone, then you're all too familiar with
this frustrating experience - you do a search,
tap on a result for an article you want to read,
then end up staring confusingly at the site's
mobile-web optimized homepage. Where is the
content you wanted? Who knows! It's a huge waste
of time and bandwidth to have to deal with pages
like this when surfing on a smartphone, and
Google is now going to make sure that sites like
that no longer get top placement."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://googlewebmastercentral.blogspot.com/2013/06/changes-in-rankings-of-smartphone_11.html">Changes
in rankings of smartphone search results</a>
(Google Webmaster Central Blog) "Avoiding these
mistakes helps your smartphone users engage with
your site fully and helps searchers find what
they're looking for faster. To improve the
search experience for smartphone users and
address their pain points, we plan to roll out
several ranking changes in the near future that
address sites that are misconfigured for
smartphone users."</li>
<li style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;"><a
href="http://www.webpronews.com/mobile-site-speed-to-be-a-google-ranking-factor-2013-06">Mobile
site speed to be a Google ranking factor?</a>
(WebProNews/Chris Crum) "Google is making it so
you have no excuse to treat your mobile content
with less regard than your desktop content.
Frankly, sites should be optimizing for mobile
anyway, simply for the benefit of their users,
but if ignoring the mobile experience is going
to cost sites search rankings, perhaps this will
light a fire under their butts to do something
about poor mobile site performance."</li>
</ul>
<div style="text-align: left;"> </div>
<p style="text-align: left; font-size: 20px;
font-family: arial; line-height: 110%;"><small><strong><em>OPLIN
fact (and sneaky promotion?):</em></strong></small><br>
</p>
<div style="text-align: justify; font-size: 16px;
font-family: arial; line-height: 110%;">If your
library uses an OPLIN Dynamic Website Kit, no
worries. All new sites are built with responsive
web design, and all existing sites should be
upgraded within the next year or so.
</div>
<div style="text-align: left;"> </div>
<!-- End paste of web source here --> </td>
</tr>
<tr>
<td style="" solid="" background-color:="" rgb(255,=""
255,="" 255);="" >="" valign="top" width="760"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickbgwide.jpg"><span
style="font-size: 10px; color: rgb(96, 96, 96);
line-height: 100%; font-family: verdana;">
<hr><!-- Begin standard subscription verbiage -->
<div style="text-align: justify;">The <strong><em>OPLIN
4cast</em></strong>
is a weekly compilation of
recent headlines, topics, and trends that could
impact public
libraries. You can subscribe to it in a variety
of ways, such as: <br>
</div>
<div style="text-align: left;"> </div>
<ul>
<li style="text-align: justify;"><strong>RSS
feed.</strong>
You
can receive the OPLIN 4cast
via RSS feed by subscribing to the following
URL:
<a class="moz-txt-link-freetext" href="http://www.oplin.org/4cast/index.php/?feed=rss2">http://www.oplin.org/4cast/index.php/?feed=rss2</a>.
</li>
<li style="text-align: justify;"><strong>Live
Bookmark.</strong>
If you're using the Firefox
web browser, you can go to the 4cast website
(<a class="moz-txt-link-freetext" href="http://www.oplin.org/4cast/">http://www.oplin.org/4cast/</a>) and click on the
orange "radio wave" icon
on the right side of the address bar. In
Internet Explorer 7, click on
the same icon to view or subscribe to the
4cast RSS feed. </li>
<li style="text-align: justify;"><strong>E-mail.</strong>
You
can have the OPLIN 4cast
delivered via e-mail (a'la OPLINlist and
OPLINtech) by subscribing to
the 4cast mailing list at
<a class="moz-txt-link-freetext" href="http://mail.oplin.org/mailman/listinfo/OPLIN4cast">http://mail.oplin.org/mailman/listinfo/OPLIN4cast</a>.
</li>
</ul>
</span> </td>
</tr>
<tr>
<td style="border-top: 0px solid rgb(255, 255, 255);
background-color: rgb(255, 255, 204);" valign="top"
width="760"
background="http://www.oplin.org/4cast/wp-content/themes/4cast/images/kubrickfooter.jpg">
<br>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<title>OPLIN 4Cast</title>
<style>
.headerTop { background-color:#FFFFFF; border-top:0px solid #000000; border-bottom:1px solid #FFFFFF; text-align:center; }
.adminText { font-size:16px; color:#0000FF; line-height:200%; font-family:verdana; text-decoration:none; }
.headerBar { background-color:#FFFFFF; border-top:0px solid #333333; border-bottom:0px solid #FFFFFF; }
.title { font-size:20px; font-weight:bold; color:#000000; font-family:arial; line-height:110%; }
.subTitle { font-size:11px; font-weight:normal; color:#000000; font-style:italic; font-family:arial; }
.defaultText { font-size:12px; color:#000000; line-height:150%; font-family:trebuchet ms; }
.footerRow { background-color:#FFFFCC; border-top:0px solid #FFFFFF; }
.footerText { font-size:10px; color:#996600; line-height:100%; font-family:verdana; }
a { color:#0000FF; color:#0000FF; color:#0000FF; }
</style>
</body>
</html>