<?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 for Web Developer &amp; SEO - Srikanth AD</title>
	<atom:link href="http://www.srikanth.me/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.srikanth.me</link>
	<description></description>
	<lastBuildDate>Mon, 14 Nov 2011 22:48:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on Managing Custom Stock Status &#8211; Magento by John</title>
		<link>http://www.srikanth.me/managing-custom-stock-status-magento/comment-page-1/#comment-2190</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 14 Nov 2011 22:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.srikanth.me/?p=3568#comment-2190</guid>
		<description>Thanks! This is good tutorial. 
Any way to hook such custom stock options with configurable products? For example, to show configurable product option and then this custom stock message?
Red - In stock
Black - Backorder
Green - Dropship</description>
		<content:encoded><![CDATA[<p>Thanks! This is good tutorial.<br />
Any way to hook such custom stock options with configurable products? For example, to show configurable product option and then this custom stock message?<br />
Red &#8211; In stock<br />
Black &#8211; Backorder<br />
Green &#8211; Dropship</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSS lessons learnt the hard way by Srikanth AD</title>
		<link>http://www.srikanth.me/css-lessons/comment-page-1/#comment-1934</link>
		<dc:creator>Srikanth AD</dc:creator>
		<pubDate>Thu, 30 Jun 2011 01:30:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.srikanth.me/?p=2794#comment-1934</guid>
		<description>Using inline styles is not a sin. For instance, sites like Google use it to load a page faster but, for web services/sites which are being maintained by a team of developers - it becomes tedious to maintain code with inline styles in place.

Sites based on a CMS, usually have a WYSIWYG editor (tinymce or CK Editor) which might not have control on the CSS of the theme so, in some cases the styles might be added inline.

* It&#039;s not applicable to all sites and, I mentioned the same in my footnote.</description>
		<content:encoded><![CDATA[<p>Using inline styles is not a sin. For instance, sites like Google use it to load a page faster but, for web services/sites which are being maintained by a team of developers &#8211; it becomes tedious to maintain code with inline styles in place.</p>
<p>Sites based on a CMS, usually have a WYSIWYG editor (tinymce or CK Editor) which might not have control on the CSS of the theme so, in some cases the styles might be added inline.</p>
<p>* It&#8217;s not applicable to all sites and, I mentioned the same in my footnote.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSS lessons learnt the hard way by Manuel</title>
		<link>http://www.srikanth.me/css-lessons/comment-page-1/#comment-1933</link>
		<dc:creator>Manuel</dc:creator>
		<pubDate>Wed, 29 Jun 2011 23:38:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.srikanth.me/?p=2794#comment-1933</guid>
		<description>I think you are perfectly right about the inline styles. Unfortunately 78% of all sites use that technique: 
http://w3techs.com/technologies/details/ce-inlinecss/all/all

One of them is srikanth.me:
http://w3techs.com/sites/info/srikanth.me</description>
		<content:encoded><![CDATA[<p>I think you are perfectly right about the inline styles. Unfortunately 78% of all sites use that technique:<br />
<a href="http://w3techs.com/technologies/details/ce-inlinecss/all/all" rel="nofollow">http://w3techs.com/technologies/details/ce-inlinecss/all/all</a></p>
<p>One of them is srikanth.me:<br />
<a href="http://w3techs.com/sites/info/srikanth.me" rel="nofollow">http://w3techs.com/sites/info/srikanth.me</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSS lessons learnt the hard way by Jay</title>
		<link>http://www.srikanth.me/css-lessons/comment-page-1/#comment-1918</link>
		<dc:creator>Jay</dc:creator>
		<pubDate>Tue, 28 Jun 2011 12:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.srikanth.me/?p=2794#comment-1918</guid>
		<description>Thanks, great post.</description>
		<content:encoded><![CDATA[<p>Thanks, great post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSS lessons learnt the hard way by James</title>
		<link>http://www.srikanth.me/css-lessons/comment-page-1/#comment-1890</link>
		<dc:creator>James</dc:creator>
		<pubDate>Sun, 26 Jun 2011 22:42:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.srikanth.me/?p=2794#comment-1890</guid>
		<description>I think another tip is to use rules with the least amount of selectors. It&#039;s probably not wise to get over specific for a number of reasons.

One reason is that it&#039;s pretty slow.

Another reason is that it pretty much defines how specific you have to be in the rest of your CSS document, which further means that most of your CSS will be slower to render.

This is more of a speed thing but I can&#039;t see how having to go and rewrite all your selection rules again can be a good when you have thousands of lines of CSS.</description>
		<content:encoded><![CDATA[<p>I think another tip is to use rules with the least amount of selectors. It&#8217;s probably not wise to get over specific for a number of reasons.</p>
<p>One reason is that it&#8217;s pretty slow.</p>
<p>Another reason is that it pretty much defines how specific you have to be in the rest of your CSS document, which further means that most of your CSS will be slower to render.</p>
<p>This is more of a speed thing but I can&#8217;t see how having to go and rewrite all your selection rules again can be a good when you have thousands of lines of CSS.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

