<?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: Press Release 2.0?</title>
	<atom:link href="http://www.atypicalva.com/blog/2007/03/23/press-release-20/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.atypicalva.com/blog/2007/03/23/press-release-20/</link>
	<description>Online Presence &#124; New Media &#124; Social Networking</description>
	<lastBuildDate>Sat, 12 Dec 2009 18:05:38 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: In Defense of Press Release 1.0 &#124; Highlight This!</title>
		<link>http://www.atypicalva.com/blog/2007/03/23/press-release-20/comment-page-1/#comment-622</link>
		<dc:creator>In Defense of Press Release 1.0 &#124; Highlight This!</dc:creator>
		<pubDate>Tue, 03 Apr 2007 13:18:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.atypicalva.com/atypical-va-blog/press-release-20/#comment-622</guid>
		<description>[...] Jen over at Atypical VA , posted about Press Release 2.0.  The new press release is friendly, fun and written so that your personality shows through.  Yes, you should always have a hook, and of course, your releases should be attention-getting.  However, depending on your goals, you should sometimes go the more traditional route.  It all depends on the paper and your goals for publishing the release. [...]</description>
		<content:encoded><![CDATA[<p>[...] Jen over at Atypical VA , posted about Press Release 2.0.  The new press release is friendly, fun and written so that your personality shows through.  Yes, you should always have a hook, and of course, your releases should be attention-getting.  However, depending on your goals, you should sometimes go the more traditional route.  It all depends on the paper and your goals for publishing the release. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meredith</title>
		<link>http://www.atypicalva.com/blog/2007/03/23/press-release-20/comment-page-1/#comment-620</link>
		<dc:creator>Meredith</dc:creator>
		<pubDate>Tue, 03 Apr 2007 13:03:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.atypicalva.com/atypical-va-blog/press-release-20/#comment-620</guid>
		<description>You need to know your goal in sending the release and your target audience.  One of my part-time gigs is doing public relations for a local government agency. When I do releases for them, my goal (usually) is to get the information into a *very* local paper. The small paper does not have enough staff to actually interview me, they use the press release pretty much as is. 

Even when I am shooting for the Washington Post, I tend to play it &quot;straight&quot; because some journalists are pretty traditional.  

On the other hand, when I send a pitch e-mail to a specific journalist, it tends to be much more 2.0-ish (fun, personal, interesting).  I usually know them, know their writing style and can send something completely customized.</description>
		<content:encoded><![CDATA[<p>You need to know your goal in sending the release and your target audience.  One of my part-time gigs is doing public relations for a local government agency. When I do releases for them, my goal (usually) is to get the information into a *very* local paper. The small paper does not have enough staff to actually interview me, they use the press release pretty much as is. </p>
<p>Even when I am shooting for the Washington Post, I tend to play it &#8220;straight&#8221; because some journalists are pretty traditional.  </p>
<p>On the other hand, when I send a pitch e-mail to a specific journalist, it tends to be much more 2.0-ish (fun, personal, interesting).  I usually know them, know their writing style and can send something completely customized.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
