<?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: New Blog Theme</title>
	<atom:link href="http://sites.middlebury.edu/lis/2009/09/29/new-blog-theme/feed/" rel="self" type="application/rss+xml" />
	<link>http://sites.middlebury.edu/lis/2009/09/29/new-blog-theme/</link>
	<description>We Bring Knowledge to You</description>
	<lastBuildDate>Mon, 29 Apr 2013 18:45:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Adam Franco</title>
		<link>http://sites.middlebury.edu/lis/2009/09/29/new-blog-theme/comment-page-1/#comment-3631</link>
		<dc:creator>Adam Franco</dc:creator>
		<pubDate>Mon, 05 Oct 2009 12:35:08 +0000</pubDate>
		<guid isPermaLink="false">http://sites.middlebury.edu/liscurriculartechteam/?p=191#comment-3631</guid>
		<description><![CDATA[Mike, the CT Team blog was moved into the LIS blog last Friday (note the URL if viewing in a browser). The old URLs automatically redirect into the LIS blog to preserve existing permalinks. Some feed readers will also transparently follow the redirects so an existing subscription to the CT Team blog will now show items from the LIS blog.

As for other blogs, I have no idea. Our thought with moving the CT Team blog is that this blog&#039;s purpose was to provide information and updates to LIS staff as well as faculty; consolidating with the LIS blog improves the ability to fulfill that purpose by increasing the number of eyeballs on our posts. Other blogs with divergent purposes -- say, exploring the integration of blogging and Facebook by trying out various plugins to each -- might be less appropriate for merging with the LIS blog.

As we were informed by the LIS website team, informational blogs are likely good candidates for a merger, but it is up to those doing the blogging to make the decision to merge or not.]]></description>
		<content:encoded><![CDATA[<p>Mike, the CT Team blog was moved into the LIS blog last Friday (note the URL if viewing in a browser). The old URLs automatically redirect into the LIS blog to preserve existing permalinks. Some feed readers will also transparently follow the redirects so an existing subscription to the CT Team blog will now show items from the LIS blog.</p>
<p>As for other blogs, I have no idea. Our thought with moving the CT Team blog is that this blog&#8217;s purpose was to provide information and updates to LIS staff as well as faculty; consolidating with the LIS blog improves the ability to fulfill that purpose by increasing the number of eyeballs on our posts. Other blogs with divergent purposes &#8212; say, exploring the integration of blogging and Facebook by trying out various plugins to each &#8212; might be less appropriate for merging with the LIS blog.</p>
<p>As we were informed by the LIS website team, informational blogs are likely good candidates for a merger, but it is up to those doing the blogging to make the decision to merge or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Roy</title>
		<link>http://sites.middlebury.edu/lis/2009/09/29/new-blog-theme/comment-page-1/#comment-3611</link>
		<dc:creator>Mike Roy</dc:creator>
		<pubDate>Mon, 05 Oct 2009 03:05:52 +0000</pubDate>
		<guid isPermaLink="false">http://sites.middlebury.edu/liscurriculartechteam/?p=191#comment-3611</guid>
		<description><![CDATA[I am wondering whether or not the curricular technology team is going to move its blog into the LIS blog? What blogs within LIS are not going to be consolidated into the new LIS blog?]]></description>
		<content:encoded><![CDATA[<p>I am wondering whether or not the curricular technology team is going to move its blog into the LIS blog? What blogs within LIS are not going to be consolidated into the new LIS blog?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
