<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Anatomy of a web content document</title>
	<atom:link href="http://blog.braintraffic.com/2010/02/anatomy-of-a-web-content-document/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.braintraffic.com/2010/02/anatomy-of-a-web-content-document/</link>
	<description></description>
	<lastBuildDate>Thu, 02 Feb 2012 22:49:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Dianne White</title>
		<link>http://blog.braintraffic.com/2010/02/anatomy-of-a-web-content-document/comment-page-1/#comment-2916</link>
		<dc:creator>Dianne White</dc:creator>
		<pubDate>Fri, 22 Jul 2011 18:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1012#comment-2916</guid>
		<description>That&#039;s true. You just don&#039;t write something and post it online, since you need to do a bit more than that if you want to get noticed. Stuff like tags, formatting, and SEO can help make things easier for your readers to find you. The web is a big place, so you need to do something to help you get noticed, after all.</description>
		<content:encoded><![CDATA[<p>That&#8217;s true. You just don&#8217;t write something and post it online, since you need to do a bit more than that if you want to get noticed. Stuff like tags, formatting, and SEO can help make things easier for your readers to find you. The web is a big place, so you need to do something to help you get noticed, after all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: web site content writer</title>
		<link>http://blog.braintraffic.com/2010/02/anatomy-of-a-web-content-document/comment-page-1/#comment-1130</link>
		<dc:creator>web site content writer</dc:creator>
		<pubDate>Mon, 31 May 2010 20:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1012#comment-1130</guid>
		<description>Hi&lt;br&gt;It is quite interesting.&lt;br&gt;Thanks for this.</description>
		<content:encoded><![CDATA[<p>Hi<br />It is quite interesting.<br />Thanks for this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tedgoas</title>
		<link>http://blog.braintraffic.com/2010/02/anatomy-of-a-web-content-document/comment-page-1/#comment-927</link>
		<dc:creator>tedgoas</dc:creator>
		<pubDate>Wed, 03 Mar 2010 01:14:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1012#comment-927</guid>
		<description>Do you typically include TITLE and ALT text for images and links? What are you thoughts on who owns this? (assuming this gets done at all!)</description>
		<content:encoded><![CDATA[<p>Do you typically include TITLE and ALT text for images and links? What are you thoughts on who owns this? (assuming this gets done at all!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cane</title>
		<link>http://blog.braintraffic.com/2010/02/anatomy-of-a-web-content-document/comment-page-1/#comment-908</link>
		<dc:creator>Mike Cane</dc:creator>
		<pubDate>Sat, 27 Feb 2010 04:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1012#comment-908</guid>
		<description>Appearance will change dramatically to accommodate touchscreens.&lt;br&gt;&lt;br&gt;Web Designers: Wake Up And Smell The Touchscreen Coffee!&lt;br&gt;&lt;a href=&quot;http://ebooktest.wordpress.com/2010/01/31/web-designers-wake-up-and-smell-the-touchscreen-coffee/&quot; rel=&quot;nofollow&quot;&gt;http://ebooktest.wordpress.com/2010/01/31/web-d...&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Appearance will change dramatically to accommodate touchscreens.</p>
<p>Web Designers: Wake Up And Smell The Touchscreen Coffee!<br /><a href="http://ebooktest.wordpress.com/2010/01/31/web-designers-wake-up-and-smell-the-touchscreen-coffee/" rel="nofollow"></a><a href="http://ebooktest.wordpress.com/2010/01/31/web-d.." rel="nofollow">http://ebooktest.wordpress.com/2010/01/31/web-d..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MelissaKMcAvoy</title>
		<link>http://blog.braintraffic.com/2010/02/anatomy-of-a-web-content-document/comment-page-1/#comment-856</link>
		<dc:creator>MelissaKMcAvoy</dc:creator>
		<pubDate>Thu, 25 Feb 2010 20:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1012#comment-856</guid>
		<description>As a web developer turned content coordinator, I think it is also important to give clear instruction (or suggestion) to the developers on the URL or filename for a new web document. It should be clear, short, and keyword heavy. What good is good content if it can&#039;t be found easily, especially through a search engine?</description>
		<content:encoded><![CDATA[<p>As a web developer turned content coordinator, I think it is also important to give clear instruction (or suggestion) to the developers on the URL or filename for a new web document. It should be clear, short, and keyword heavy. What good is good content if it can&#39;t be found easily, especially through a search engine?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Ingram</title>
		<link>http://blog.braintraffic.com/2010/02/anatomy-of-a-web-content-document/comment-page-1/#comment-855</link>
		<dc:creator>Richard Ingram</dc:creator>
		<pubDate>Thu, 25 Feb 2010 19:50:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=1012#comment-855</guid>
		<description>Writing dynamic content for developers is usually the acid test of any web content document.&lt;br&gt;&lt;br&gt;As I&#039;m used to working with php programmers I tend to use its syntax for a variable (a $ sign followed by the variable name itself) to indicate a changing word or phrase within written content. So if a particular sentence contains a variable such as:&lt;br&gt;&lt;br&gt;We&#039;ve identified Heathrow as your nearest airport.&lt;br&gt;&lt;br&gt;I&#039;ll usually write something like:&lt;br&gt;&lt;br&gt;We&#039;ve identified ($airport_name) as your nearest airport.&lt;br&gt;&lt;br&gt;Or, if the content changes depending on the user&#039;s actions I&#039;ll try to best explain the scenario that should result in its appearance. For instance, in the event of an exact match being returned by a search engine I&#039;ll write something like:&lt;br&gt;&lt;br&gt;!Exact Match! Header2: We&#039;ve identified ($city_name) as your location.&lt;br&gt;&lt;br&gt;Or, in the result of a best guess scenario I&#039;ll write:&lt;br&gt;&lt;br&gt;!Best Guess! Header2: We&#039;ve identified ($city_name) as your nearest city. Is this correct?&lt;br&gt;&lt;br&gt;It&#039;s always interesting to read how others approach the creation of these documents. Thanks.</description>
		<content:encoded><![CDATA[<p>Writing dynamic content for developers is usually the acid test of any web content document.</p>
<p>As I&#39;m used to working with php programmers I tend to use its syntax for a variable (a $ sign followed by the variable name itself) to indicate a changing word or phrase within written content. So if a particular sentence contains a variable such as:</p>
<p>We&#39;ve identified Heathrow as your nearest airport.</p>
<p>I&#39;ll usually write something like:</p>
<p>We&#39;ve identified ($airport_name) as your nearest airport.</p>
<p>Or, if the content changes depending on the user&#39;s actions I&#39;ll try to best explain the scenario that should result in its appearance. For instance, in the event of an exact match being returned by a search engine I&#39;ll write something like:</p>
<p>!Exact Match! Header2: We&#39;ve identified ($city_name) as your location.</p>
<p>Or, in the result of a best guess scenario I&#39;ll write:</p>
<p>!Best Guess! Header2: We&#39;ve identified ($city_name) as your nearest city. Is this correct?</p>
<p>It&#39;s always interesting to read how others approach the creation of these documents. Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

