<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ninethirty Creative Blog &#187; Newsletters</title>
	<atom:link href="http://www.ninethirty.co.uk/blog/tag/newsletters/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ninethirty.co.uk/blog</link>
	<description>Ninethirty Web Design</description>
	<lastBuildDate>Thu, 16 Apr 2009 10:45:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Writing for the web and print, what&#8217;s the difference?</title>
		<link>http://www.ninethirty.co.uk/blog/2009/04/writing-for-the-web-is-it-important/</link>
		<comments>http://www.ninethirty.co.uk/blog/2009/04/writing-for-the-web-is-it-important/#comments</comments>
		<pubDate>Thu, 16 Apr 2009 10:42:39 +0000</pubDate>
		<dc:creator>Steven</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Fonts]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Newsletters]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Web sites]]></category>

		<guid isPermaLink="false">http://www.ninethirty.co.uk/blog/?p=47</guid>
		<description><![CDATA[Clients often ask, what&#8217;s the difference between writing on the web, as appose to writing for print. Well, writing for the Web needs to grab your attention and gets the results you want. This needs special skill, and inclusion of keywords to also help with SEO, whether you are selling products or services or if [...]]]></description>
			<content:encoded><![CDATA[<p>Clients often ask, what&#8217;s the difference between writing on the web, as appose to writing for print. Well, writing for the Web needs to grab your attention and gets the results you want. This needs special skill, and inclusion of keywords to also help with SEO, whether you are selling products or services or if you just want to let people know what you are up to on your personal site. <span id="more-47"></span></p>
<p>One of the impediments to online reading is physical: It’s harder to read on a screen than it is to read on paper. Even the best computer monitors are hopelessly fuzzy when compared to the crisp images on a glossy magazine page, and the extra effort this requires from human eyes and brains slows<br />
readers down. The longer the document, the bigger the problem.  </p>
<p>Today’s monitors are vastly better than the ones in use years ago—especially the latest<br />
generation with flat screens and liquid crystal displays. Better software is also<br />
helping. Microsoft, for instance, has created a superior family of fonts<br />
specifically designed for online reading (Arial and Tahoma are two of the most widely<br />
used). </p>
<p>But the more significant barrier web writers must overcome is behavioral, not physical. Everyone who has studied online reading will know that people behave differently when online. When viewing a new page, they don’t read—they scan. They look at headings and subheadings first; they scan for hyperlinks, numerals, and keywords. They jump around, scrolling and clicking—their fingers never far from the browser’s “Back” button.  </p>
<p>The challenge for the web writer is to overcome readers’ impatience by keeping things as brief as possible. </p>
<p>Do you know of some good articles, tutorials, newsletters, Web sites, books, or other resources related to writing for the Web, Web site content, or related topics? Recommendations are welcome and encouraged! </p>
]]></content:encoded>
			<wfw:commentRss>http://www.ninethirty.co.uk/blog/2009/04/writing-for-the-web-is-it-important/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

