<?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"
	>
<channel>
	<title>Comments on: Considering WordPress</title>
	<atom:link href="http://tigerblade.net/journal/2006/10/19/considering-wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://tigerblade.net/journal/2006/10/19/considering-wordpress/</link>
	<description>mindless observations of the world around us</description>
	<pubDate>Wed, 19 Nov 2008 22:29:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: MrEggsalad</title>
		<link>http://tigerblade.net/journal/2006/10/19/considering-wordpress/#comment-1130</link>
		<dc:creator>MrEggsalad</dc:creator>
		<pubDate>Fri, 20 Oct 2006 12:51:10 +0000</pubDate>
		<guid isPermaLink="false">#comment-1130</guid>
		<description>Yeah, just make sure it is un-wordpressy. Give it your style! I personally have never messed with Word-Press skins and themes or whatever they are, but, from what you are saying it looks just to be some CSS which shouldn&#39;t be &lt;i&gt;too&lt;/i&gt; hard to figure out. (I did Xanga and MySpace.. :P ) Good luck!</description>
		<content:encoded><![CDATA[<p>Yeah, just make sure it is un-wordpressy. Give it your style! I personally have never messed with Word-Press skins and themes or whatever they are, but, from what you are saying it looks just to be some CSS which shouldn&#39;t be <i>too</i> hard to figure out. (I did Xanga and MySpace.. :P ) Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tigerblade</title>
		<link>http://tigerblade.net/journal/2006/10/19/considering-wordpress/#comment-1129</link>
		<dc:creator>Tigerblade</dc:creator>
		<pubDate>Thu, 19 Oct 2006 07:49:37 +0000</pubDate>
		<guid isPermaLink="false">#comment-1129</guid>
		<description>Wow.  Holy crap.  I did it.  It was a lot of... interesting... work, but I managed to write converters to move all the content (entries and comments) over to the new database.&lt;br /&gt;&lt;br /&gt;Now I just need to play with the design a bit to get it looking not-default-wordpress, and we&#39;ll see where it goes from there.</description>
		<content:encoded><![CDATA[<p>Wow.  Holy crap.  I did it.  It was a lot of&#8230; interesting&#8230; work, but I managed to write converters to move all the content (entries and comments) over to the new database.</p>
<p>Now I just need to play with the design a bit to get it looking not-default-wordpress, and we&#39;ll see where it goes from there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AwesomeSauce</title>
		<link>http://tigerblade.net/journal/2006/10/19/considering-wordpress/#comment-1128</link>
		<dc:creator>AwesomeSauce</dc:creator>
		<pubDate>Thu, 19 Oct 2006 05:17:42 +0000</pubDate>
		<guid isPermaLink="false">#comment-1128</guid>
		<description>I&#39;m proud of you, man. I&#39;ve mostly only known about HTML for the past few years, yet I have not gone far enough as to really learn PHP. I don&#39;t even know that much about CSS.&lt;br /&gt;&lt;br /&gt;I might find a blogger template I like a lot on the internet, and I can usually make several drastic changes to it as I want.. but designing it from scratch? I&#39;m not really up to that.&lt;br /&gt;&lt;br /&gt;Le sigh.. instead of webscripting, I guess I&#39;d better start learning more on what I REALLY wanna do.. develope software. C++, I suppose.</description>
		<content:encoded><![CDATA[<p>I&#39;m proud of you, man. I&#39;ve mostly only known about HTML for the past few years, yet I have not gone far enough as to really learn PHP. I don&#39;t even know that much about CSS.</p>
<p>I might find a blogger template I like a lot on the internet, and I can usually make several drastic changes to it as I want.. but designing it from scratch? I&#39;m not really up to that.</p>
<p>Le sigh.. instead of webscripting, I guess I&#39;d better start learning more on what I REALLY wanna do.. develope software. C++, I suppose.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
