<?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: A Little Help For An Old School HTML Based Web Designer</title>
	<atom:link href="http://thequeenb.net/2010/02/26/cssbasics/feed/" rel="self" type="application/rss+xml" />
	<link>http://thequeenb.net/2010/02/26/cssbasics/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=cssbasics</link>
	<description>Indiscriminately Bitchy</description>
	<lastBuildDate>Tue, 06 Mar 2012 15:19:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Whitters</title>
		<link>http://thequeenb.net/2010/02/26/cssbasics/comment-page-1/#comment-457</link>
		<dc:creator>Whitters</dc:creator>
		<pubDate>Sat, 27 Feb 2010 17:07:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.thequeenb.net/?p=862#comment-457</guid>
		<description>Thats why I always use just a .html file when I&#039;m building the theme. Since relatively all my pages look the same, I build it in one .html file so I don&#039;t have to upload to look at it. Then once I&#039;ve got it looking how I want, I break it down into the WP theme files (comments.php, header.php, etc) and upload. Then if I have any tweaking to do I just do it through Wordpress. For things like plugins, I just copy the html they generate from my current site&#039;s source and use those since the plugins won&#039;t randomly start generating a new code with the new theme.

Also, if you wanted to work with .php extensions, you could think about installing a PHP environment on your computer. Then you wouldn&#039;t have to upload. Theoretically you could install Wordpress as a local copy. I know a program that works REALLY well for that and includes MySQL support. Basically it turns a www folder on your computer into a virtual server that you can test things on.

:D</description>
		<content:encoded><![CDATA[<p>Thats why I always use just a .html file when I&#8217;m building the theme. Since relatively all my pages look the same, I build it in one .html file so I don&#8217;t have to upload to look at it. Then once I&#8217;ve got it looking how I want, I break it down into the WP theme files (comments.php, header.php, etc) and upload. Then if I have any tweaking to do I just do it through WordPress. For things like plugins, I just copy the html they generate from my current site&#8217;s source and use those since the plugins won&#8217;t randomly start generating a new code with the new theme.</p>
<p>Also, if you wanted to work with .php extensions, you could think about installing a PHP environment on your computer. Then you wouldn&#8217;t have to upload. Theoretically you could install WordPress as a local copy. I know a program that works REALLY well for that and includes MySQL support. Basically it turns a www folder on your computer into a virtual server that you can test things on.</p>
<p> <img src='http://thequeenb.net/wp-includes/images/smilies/grins.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angel</title>
		<link>http://thequeenb.net/2010/02/26/cssbasics/comment-page-1/#comment-455</link>
		<dc:creator>Angel</dc:creator>
		<pubDate>Sat, 27 Feb 2010 07:11:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.thequeenb.net/?p=862#comment-455</guid>
		<description>I guess part of my problem is if I can&#039;t see what the code is actually doing, then I start to lose my direction as to how I want the theme to turn out.  Though I like your suggestion about using two files to code.  Originally, I had attempted to code the CSS first and that didn&#039;t go well.  Now if I can only find a way to view how my theme is being effected without constantly having to upload and refresh...</description>
		<content:encoded><![CDATA[<p>I guess part of my problem is if I can&#8217;t see what the code is actually doing, then I start to lose my direction as to how I want the theme to turn out.  Though I like your suggestion about using two files to code.  Originally, I had attempted to code the CSS first and that didn&#8217;t go well.  Now if I can only find a way to view how my theme is being effected without constantly having to upload and refresh&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Whitters</title>
		<link>http://thequeenb.net/2010/02/26/cssbasics/comment-page-1/#comment-454</link>
		<dc:creator>Whitters</dc:creator>
		<pubDate>Sat, 27 Feb 2010 07:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.thequeenb.net/?p=862#comment-454</guid>
		<description>When I start a template, I start with two completely blank files: index.html and style.css. From there I actually go back and forth with coding. I code the html elements in my index.html page and then go to style.css and code the corresponding CSS. I also try to keep my CSS extremely organized by grouping things / indenting / etc. That way Im not trying to code all the HTML or all the CSS at once and I don&#039;t end up getting overwhelmed.</description>
		<content:encoded><![CDATA[<p>When I start a template, I start with two completely blank files: index.html and style.css. From there I actually go back and forth with coding. I code the html elements in my index.html page and then go to style.css and code the corresponding CSS. I also try to keep my CSS extremely organized by grouping things / indenting / etc. That way Im not trying to code all the HTML or all the CSS at once and I don&#8217;t end up getting overwhelmed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

