<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: How to Convert a Static Web Site to a WordPress blog site</title>
	<atom:link href="http://blog.looseends.net/2008/how-to-convert-a-static-web-site-to-a-wordpress-blog-site/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.looseends.net/2008/how-to-convert-a-static-web-site-to-a-wordpress-blog-site/</link>
	<description>A Virtual Assistant&#039;s Blog</description>
	<lastBuildDate>Thu, 02 Feb 2012 13:25:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: ktcosmos</title>
		<link>http://blog.looseends.net/2008/how-to-convert-a-static-web-site-to-a-wordpress-blog-site/comment-page-1/#comment-3803</link>
		<dc:creator>ktcosmos</dc:creator>
		<pubDate>Mon, 19 Jan 2009 16:02:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.looseends.net/?p=651#comment-3803</guid>
		<description>Hi Debbie,
I would love to see some of the sites you have going. Learning WP&#039;s backend can be a challenge, especially when it is updated so often. It has become my favorite approach to web development over the past few years, though, and I benefit by meeting others (like you!) who are moving in that same direction. Thank you for stopping by.</description>
		<content:encoded><![CDATA[<p>Hi Debbie,<br />
I would love to see some of the sites you have going. Learning WP&#8217;s backend can be a challenge, especially when it is updated so often. It has become my favorite approach to web development over the past few years, though, and I benefit by meeting others (like you!) who are moving in that same direction. Thank you for stopping by.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Debbie</title>
		<link>http://blog.looseends.net/2008/how-to-convert-a-static-web-site-to-a-wordpress-blog-site/comment-page-1/#comment-3802</link>
		<dc:creator>Debbie</dc:creator>
		<pubDate>Mon, 19 Jan 2009 00:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.looseends.net/?p=651#comment-3802</guid>
		<description>Thanks for the information. I wish I had some wonderful insight to add. I am currently working with a client to create websites using Wordpress as our content manager.  The trouble I am having is in the editor, I have learned a lot about customizing by trial and error.
This was a wonderful post full of information.
Thanks, Debbie
PS I have read your blog in the past and really enjoy your content.</description>
		<content:encoded><![CDATA[<p>Thanks for the information. I wish I had some wonderful insight to add. I am currently working with a client to create websites using WordPress as our content manager.  The trouble I am having is in the editor, I have learned a lot about customizing by trial and error.<br />
This was a wonderful post full of information.<br />
Thanks, Debbie<br />
PS I have read your blog in the past and really enjoy your content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loosely SpeakingÃ¢â‚¬â€?A Virtual Assistant&#8217;s Blog &#187; Roundup #4, Prescott Style: WordPress</title>
		<link>http://blog.looseends.net/2008/how-to-convert-a-static-web-site-to-a-wordpress-blog-site/comment-page-1/#comment-3783</link>
		<dc:creator>Loosely SpeakingÃ¢â‚¬â€?A Virtual Assistant&#8217;s Blog &#187; Roundup #4, Prescott Style: WordPress</dc:creator>
		<pubDate>Wed, 07 Jan 2009 18:14:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.looseends.net/?p=651#comment-3783</guid>
		<description>[...] Speaking of this, read these related posts from the Loosely Speaking archives: How to convert a static web site to a WordPress blog site [...]</description>
		<content:encoded><![CDATA[<p>[...] Speaking of this, read these related posts from the Loosely Speaking archives: How to convert a static web site to a WordPress blog site [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loosely SpeakingÃ¢â‚¬â€?A Virtual Assistant&#8217;s Blog &#187; Updating to WordPress 2.7</title>
		<link>http://blog.looseends.net/2008/how-to-convert-a-static-web-site-to-a-wordpress-blog-site/comment-page-1/#comment-3741</link>
		<dc:creator>Loosely SpeakingÃ¢â‚¬â€?A Virtual Assistant&#8217;s Blog &#187; Updating to WordPress 2.7</dc:creator>
		<pubDate>Tue, 16 Dec 2008 21:03:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.looseends.net/?p=651#comment-3741</guid>
		<description>[...] Speaking of this, read these related posts from the Loosely Speaking archives: How to convert a static web site to a WordPress blog site [...]</description>
		<content:encoded><![CDATA[<p>[...] Speaking of this, read these related posts from the Loosely Speaking archives: How to convert a static web site to a WordPress blog site [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ktcosmos</title>
		<link>http://blog.looseends.net/2008/how-to-convert-a-static-web-site-to-a-wordpress-blog-site/comment-page-1/#comment-3233</link>
		<dc:creator>ktcosmos</dc:creator>
		<pubDate>Wed, 27 Aug 2008 14:13:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.looseends.net/?p=651#comment-3233</guid>
		<description>And here is the lovely Lorelle&#039;s FIRST comment on this post, left when it appeared at it&#039;s former location:

Ã¢â‚¬â„¢&quot;I&#039;ve been through this process myself long before there were the handy tools and improved import features in WordPress, so I understand where you are coming from. As for creating a static front page, create a Ã¢â‚¬Å“PageÃ¢â‚¬? in WordPress and assign that as the front page. Personally, with a good Theme where you can easily customize the front page, I donÃ¢â‚¬â„¢t see any reason to bother with a static front page in the old sense, as I want a dynamic front page portal to my site. ItÃ¢â‚¬â„¢s so much more user friendly and better SEO.

As for the drop in page rank, donÃ¢â‚¬â„¢t worry. With your site in WordPress and out of static, your pings will increase and that page rank 4 you fought for should actually go much higher as WordPress is so SEO friendly. Years ago, we had to wait months and months for any recovery in ranking from changes, even changing domains or web hosts with no change in the domain.

Using a sitemap Plugin will help those redirects and indexing, too.

However, the Plugin you mention I recommend I donÃ¢â‚¬â„¢t recommend for new versions of WordPress, and I hope you are using the latest version as past versions have security vulnerabilities and bugs. The latest version of WordPress has built-in image loading through the Gallery feature. Give it a try. ItÃ¢â‚¬â„¢s wonderful. However, it does change the URL structure for your images. I recommend that if you are not moving your site around, you make sure your images stay in their folders on your server and the links to them be absolute, and you should have no problems at all with them. And nothing to upload.

I havenÃ¢â‚¬â„¢t written about this subject in a while, so youÃ¢â‚¬â„¢ve reminded me that it is probably past due. &quot;Thanks for the kick in the butt and good luck with the changes. I think you are going to be so much happier. Heck, I KNOW you will be much happier.</description>
		<content:encoded><![CDATA[<p>And here is the lovely Lorelle&#8217;s FIRST comment on this post, left when it appeared at it&#8217;s former location:</p>
<p>Ã¢â‚¬â„¢&#8221;I&#8217;ve been through this process myself long before there were the handy tools and improved import features in WordPress, so I understand where you are coming from. As for creating a static front page, create a Ã¢â‚¬Å“PageÃ¢â‚¬? in WordPress and assign that as the front page. Personally, with a good Theme where you can easily customize the front page, I donÃ¢â‚¬â„¢t see any reason to bother with a static front page in the old sense, as I want a dynamic front page portal to my site. ItÃ¢â‚¬â„¢s so much more user friendly and better SEO.</p>
<p>As for the drop in page rank, donÃ¢â‚¬â„¢t worry. With your site in WordPress and out of static, your pings will increase and that page rank 4 you fought for should actually go much higher as WordPress is so SEO friendly. Years ago, we had to wait months and months for any recovery in ranking from changes, even changing domains or web hosts with no change in the domain.</p>
<p>Using a sitemap Plugin will help those redirects and indexing, too.</p>
<p>However, the Plugin you mention I recommend I donÃ¢â‚¬â„¢t recommend for new versions of WordPress, and I hope you are using the latest version as past versions have security vulnerabilities and bugs. The latest version of WordPress has built-in image loading through the Gallery feature. Give it a try. ItÃ¢â‚¬â„¢s wonderful. However, it does change the URL structure for your images. I recommend that if you are not moving your site around, you make sure your images stay in their folders on your server and the links to them be absolute, and you should have no problems at all with them. And nothing to upload.</p>
<p>I havenÃ¢â‚¬â„¢t written about this subject in a while, so youÃ¢â‚¬â„¢ve reminded me that it is probably past due. &#8220;Thanks for the kick in the butt and good luck with the changes. I think you are going to be so much happier. Heck, I KNOW you will be much happier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lorelle</title>
		<link>http://blog.looseends.net/2008/how-to-convert-a-static-web-site-to-a-wordpress-blog-site/comment-page-1/#comment-3232</link>
		<dc:creator>Lorelle</dc:creator>
		<pubDate>Tue, 26 Aug 2008 22:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.looseends.net/?p=651#comment-3232</guid>
		<description>You&#039;ve raised some very good points here that people need to know when converting from a static website. The number one benefit is that they will spend less time playing with code and uploading a ton of web pages every time they make the smallest change across all the pages. The time savings is incredible. It puts the focus back on generating content and not on messing around with web pages. That is so wonderful!

Having done this too many times, here are some clarifications. 

1. Google isn&#039;t the only player in town. On a WordPress blog, you will actually automatically improve your SEO value across ALL search engines over a very short period of time, so don&#039;t worry too much over the redircts issue. It is MORE important that your users have a seamless experience. A good XML sitemap will help search engines, too, as you mentioned. 

2. If your images are absolute links not relative, then just FTP upload your images into their original directories that match the link URL structure and you don&#039;t have to mess with them later. WordPress has a funky way of storing images that I&#039;m not a fan of, linked to the post by date. Learn to live with the structure of uploading new images, but keep all your old images where ever they were and you don&#039;t have to deal with URL changes for images. That saved me a ton of time.

3. The &quot;quirk&quot; in the home page issue is a Theme issue, not WordPress, though they are considering how to deal with this as it comes up repeatedly. The template tag used to generate the listing of your Pages, including &quot;home&quot; (the root index page) doesn&#039;t check the &quot;home&quot; page setting. Dig into the template file and manually set the &quot;home&quot; link to whatever you want, and then let the tag take care of the rest, excluding that link. Check the WordPress Codex for specifics on how to do that. I&#039;ve done that for years with great success.

4. About the installation to the root, that is the smartest choice. You do not want your URL to have the word &quot;blog&quot; or &quot;wordpress&quot; or another variation as that becomes a keyword, diluting your keyword mix, and making your URL longer than it needs to be. I always recommend installation to the root directory. Much cleaner.

Your last three points (7, 8, and 9) don&#039;t really have much to do with converting from a static site. Upgrading is part of the process of everything, static or not. I had to upgrade static sites all the time for various reasons, including changes in scripts and code. Natural part of the process. Luckily, WordPress is working hard on making the process of handling upgrades even easier.

The same applies to security issues. When they are found, you deal with them, no different than anything else. If you keep WordPress upgraded and you monitor WordPress news for updates, not a problem. WordPress is more response than most to these issues.

The Duplicate Content issue was exaggerated. Static content sites can also have duplicate content issues. The point is that this is easily resolved if you have worries about it with a well-designed Theme. By using excerpts on multi-post pageviews, much of the problem is automatically solved. 

Good work. Too many people are afraid to convert to dynamic content generation platforms. It is life changing, and I can&#039;t recommend it enough. If I can survive a 2,000+ static web page to dynamic (WordPress) conversion, so can others. :D</description>
		<content:encoded><![CDATA[<p>You&#8217;ve raised some very good points here that people need to know when converting from a static website. The number one benefit is that they will spend less time playing with code and uploading a ton of web pages every time they make the smallest change across all the pages. The time savings is incredible. It puts the focus back on generating content and not on messing around with web pages. That is so wonderful!</p>
<p>Having done this too many times, here are some clarifications. </p>
<p>1. Google isn&#8217;t the only player in town. On a WordPress blog, you will actually automatically improve your SEO value across ALL search engines over a very short period of time, so don&#8217;t worry too much over the redircts issue. It is MORE important that your users have a seamless experience. A good XML sitemap will help search engines, too, as you mentioned. </p>
<p>2. If your images are absolute links not relative, then just FTP upload your images into their original directories that match the link URL structure and you don&#8217;t have to mess with them later. WordPress has a funky way of storing images that I&#8217;m not a fan of, linked to the post by date. Learn to live with the structure of uploading new images, but keep all your old images where ever they were and you don&#8217;t have to deal with URL changes for images. That saved me a ton of time.</p>
<p>3. The &#8220;quirk&#8221; in the home page issue is a Theme issue, not WordPress, though they are considering how to deal with this as it comes up repeatedly. The template tag used to generate the listing of your Pages, including &#8220;home&#8221; (the root index page) doesn&#8217;t check the &#8220;home&#8221; page setting. Dig into the template file and manually set the &#8220;home&#8221; link to whatever you want, and then let the tag take care of the rest, excluding that link. Check the WordPress Codex for specifics on how to do that. I&#8217;ve done that for years with great success.</p>
<p>4. About the installation to the root, that is the smartest choice. You do not want your URL to have the word &#8220;blog&#8221; or &#8220;wordpress&#8221; or another variation as that becomes a keyword, diluting your keyword mix, and making your URL longer than it needs to be. I always recommend installation to the root directory. Much cleaner.</p>
<p>Your last three points (7, 8, and 9) don&#8217;t really have much to do with converting from a static site. Upgrading is part of the process of everything, static or not. I had to upgrade static sites all the time for various reasons, including changes in scripts and code. Natural part of the process. Luckily, WordPress is working hard on making the process of handling upgrades even easier.</p>
<p>The same applies to security issues. When they are found, you deal with them, no different than anything else. If you keep WordPress upgraded and you monitor WordPress news for updates, not a problem. WordPress is more response than most to these issues.</p>
<p>The Duplicate Content issue was exaggerated. Static content sites can also have duplicate content issues. The point is that this is easily resolved if you have worries about it with a well-designed Theme. By using excerpts on multi-post pageviews, much of the problem is automatically solved. </p>
<p>Good work. Too many people are afraid to convert to dynamic content generation platforms. It is life changing, and I can&#8217;t recommend it enough. If I can survive a 2,000+ static web page to dynamic (WordPress) conversion, so can others. <img src='http://blog.looseends.net/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loosely SpeakingÃ¢â‚¬â€?A Virtual Assistant&#8217;s Blog &#187; Converting From Static Site to Wordpress Blog?</title>
		<link>http://blog.looseends.net/2008/how-to-convert-a-static-web-site-to-a-wordpress-blog-site/comment-page-1/#comment-3231</link>
		<dc:creator>Loosely SpeakingÃ¢â‚¬â€?A Virtual Assistant&#8217;s Blog &#187; Converting From Static Site to Wordpress Blog?</dc:creator>
		<pubDate>Tue, 26 Aug 2008 17:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.looseends.net/?p=651#comment-3231</guid>
		<description>[...] Read about my conversion story here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Read about my conversion story here. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

