<?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>Daniel Eizans: Content Strategist, Geek &#187; Content Management</title>
	<atom:link href="http://danieleizans.com/tag/content-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://danieleizans.com</link>
	<description></description>
	<lastBuildDate>Wed, 21 Mar 2012 13:05:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Accounting For Context In Content Strategy</title>
		<link>http://danieleizans.com/2011/01/accounting-for-context-in-content-strategy/</link>
		<comments>http://danieleizans.com/2011/01/accounting-for-context-in-content-strategy/#comments</comments>
		<pubDate>Mon, 10 Jan 2011 15:22:50 +0000</pubDate>
		<dc:creator>Daniel Eizans</dc:creator>
				<category><![CDATA[Content Management]]></category>
		<category><![CDATA[Content Strategy]]></category>
		<category><![CDATA[Context]]></category>
		<category><![CDATA[Information Architecture]]></category>
		<category><![CDATA[Usability]]></category>

		<guid isPermaLink="false">http://danieleizans.com/?p=664</guid>
		<description><![CDATA[You can't have a content strategy without content planning and it won't be good strategy without the Ménage à trois between CS, an information architect and your content team. That's all fine and good. Now, where where the hell is the context? ]]></description>
		<wfw:commentRss>http://danieleizans.com/2011/01/accounting-for-context-in-content-strategy/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Contextual Delivery: How To Hit The Moving (And Evolving) Mobile Target</title>
		<link>http://danieleizans.com/2010/12/contextual-delivery-how-to-hit-the-moving-and-evolving-mobile-target/</link>
		<comments>http://danieleizans.com/2010/12/contextual-delivery-how-to-hit-the-moving-and-evolving-mobile-target/#comments</comments>
		<pubDate>Fri, 10 Dec 2010 14:11:11 +0000</pubDate>
		<dc:creator>Daniel Eizans</dc:creator>
				<category><![CDATA[Context]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Content Management]]></category>

		<guid isPermaLink="false">http://danieleizans.com/?p=604</guid>
		<description><![CDATA[Is your content prepared for the oncoming influx of new smartphone wielding mobile users? Here are the three strategies to focus on first when you're getting into the mobile game. ]]></description>
		<wfw:commentRss>http://danieleizans.com/2010/12/contextual-delivery-how-to-hit-the-moving-and-evolving-mobile-target/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Who&#8217;s Responsible For Content That Expires?</title>
		<link>http://danieleizans.com/2009/12/whos-responsible-for-content-that-expires/</link>
		<comments>http://danieleizans.com/2009/12/whos-responsible-for-content-that-expires/#comments</comments>
		<pubDate>Thu, 17 Dec 2009 17:14:10 +0000</pubDate>
		<dc:creator>Daniel Eizans</dc:creator>
				<category><![CDATA[Content Strategy]]></category>
		<category><![CDATA[Content]]></category>
		<category><![CDATA[Content Management]]></category>
		<category><![CDATA[Governance]]></category>

		<guid isPermaLink="false">http://danieleizans.com/?p=324</guid>
		<description><![CDATA[When it comes to your Web site content, who is responsible for removing it after its lifecycle? For many of you publishers out there, I'd wager that you treat your expired content the same way you treat your recently deceased and always distant Aunt Mildred.]]></description>
		<wfw:commentRss>http://danieleizans.com/2009/12/whos-responsible-for-content-that-expires/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

