<?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: 7 additional tips for CSS markup</title>
	<atom:link href="http://blog.mixu.net/2010/03/15/7-additional-tips-for-css-markup/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mixu.net/2010/03/15/7-additional-tips-for-css-markup/</link>
	<description>When I read what I write I learn what I think</description>
	<lastBuildDate>Tue, 31 Jan 2012 10:55:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Brian</title>
		<link>http://blog.mixu.net/2010/03/15/7-additional-tips-for-css-markup/#comment-9633</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Thu, 10 Nov 2011 12:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mixu.net/?p=740#comment-9633</guid>
		<description>All and all a good article. Well done !!</description>
		<content:encoded><![CDATA[<p>All and all a good article. Well done !!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kohana 3 auth: sample implementation and documentation &#171; Mixu&#039;s tech blog</title>
		<link>http://blog.mixu.net/2010/03/15/7-additional-tips-for-css-markup/#comment-6778</link>
		<dc:creator>Kohana 3 auth: sample implementation and documentation &#171; Mixu&#039;s tech blog</dc:creator>
		<pubDate>Tue, 14 Sep 2010 08:24:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mixu.net/?p=740#comment-6778</guid>
		<description>[...] this post. You can do a lot by adding a few more divs into the header div. I have tried to follow my own advice about CSS, but the included CSS file is pretty basic. It includes the Yahoo CSS [...]</description>
		<content:encoded><![CDATA[<p>[...] this post. You can do a lot by adding a few more divs into the header div. I have tried to follow my own advice about CSS, but the included CSS file is pretty basic. It includes the Yahoo CSS [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Better web application interface markup: lessons from Wordpress theme frameworks (Thematic, Theme Hybrid, WP Framework) &#171; Mixu&#039;s tech blog</title>
		<link>http://blog.mixu.net/2010/03/15/7-additional-tips-for-css-markup/#comment-6700</link>
		<dc:creator>Better web application interface markup: lessons from Wordpress theme frameworks (Thematic, Theme Hybrid, WP Framework) &#171; Mixu&#039;s tech blog</dc:creator>
		<pubDate>Tue, 20 Jul 2010 10:25:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mixu.net/?p=740#comment-6700</guid>
		<description>[...] Every time I start a new web application project, I spend a while (re)thinking what the layout structure should be in terms of CSS and HTML (e.g. semantic naming, organizing CSS markup). [...]</description>
		<content:encoded><![CDATA[<p>[...] Every time I start a new web application project, I spend a while (re)thinking what the layout structure should be in terms of CSS and HTML (e.g. semantic naming, organizing CSS markup). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikito Takada</title>
		<link>http://blog.mixu.net/2010/03/15/7-additional-tips-for-css-markup/#comment-5122</link>
		<dc:creator>Mikito Takada</dc:creator>
		<pubDate>Sat, 27 Mar 2010 16:27:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mixu.net/?p=740#comment-5122</guid>
		<description>Thanks for commenting. I think that there is a small set of inline elements, such as H1 for which it is useful to define &quot;global&quot; styles. You can still override the styles in those cases where it is necessary - just organize the related elements as a &quot;widget&quot; with a base class name or use an ID. 

I don&#039;t think tables should have global styles besides the CSS reset. It seems to always end up being too complex. So what I would do is give the table a class name or ID, and give each type of table widget it&#039;s own set of styles. 

This would include inline elements like H1 as well - but instead of relying on the coincidental application of styles from the &quot;global style&quot; I would explicitly define all the necessary styles inside the widget definition. This wastes some space, but in my opinion stylesheets are meant to be human-readable and portable and if that requires an extra couple of hundred bytes, it still is worth it.</description>
		<content:encoded><![CDATA[<p>Thanks for commenting. I think that there is a small set of inline elements, such as H1 for which it is useful to define &#8220;global&#8221; styles. You can still override the styles in those cases where it is necessary &#8211; just organize the related elements as a &#8220;widget&#8221; with a base class name or use an ID. </p>
<p>I don&#8217;t think tables should have global styles besides the CSS reset. It seems to always end up being too complex. So what I would do is give the table a class name or ID, and give each type of table widget it&#8217;s own set of styles. </p>
<p>This would include inline elements like H1 as well &#8211; but instead of relying on the coincidental application of styles from the &#8220;global style&#8221; I would explicitly define all the necessary styles inside the widget definition. This wastes some space, but in my opinion stylesheets are meant to be human-readable and portable and if that requires an extra couple of hundred bytes, it still is worth it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gman</title>
		<link>http://blog.mixu.net/2010/03/15/7-additional-tips-for-css-markup/#comment-5085</link>
		<dc:creator>gman</dc:creator>
		<pubDate>Thu, 25 Mar 2010 07:12:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mixu.net/?p=740#comment-5085</guid>
		<description>I&#039;m not an HTML or CSS guru by any means but running a blog, I can say that &quot;#content h1&quot; makes it hard to edit my blog.

What happens is around the main page there is #body or some such. That means EVERYTHING inside that is effected. Around that this are things like #left-column, #middle, #right-column. So now both #body and #middle effect everything in my content. Finally there is something like #posts, #post and #content

So I&#039;m trying to write some content. I need a table. That table needs custom styles to get it&#039;s point across.  But now the css for #body, #middle, #posts, #post and #content all effect it.  I really want an easy way to be able to make some custom content with custom styles and not have to know which 25 settings I need to reset because of the &quot;#id tag&quot; idiom.

Is there a recommended way to do that?</description>
		<content:encoded><![CDATA[<p>I&#8217;m not an HTML or CSS guru by any means but running a blog, I can say that &#8220;#content h1&#8243; makes it hard to edit my blog.</p>
<p>What happens is around the main page there is #body or some such. That means EVERYTHING inside that is effected. Around that this are things like #left-column, #middle, #right-column. So now both #body and #middle effect everything in my content. Finally there is something like #posts, #post and #content</p>
<p>So I&#8217;m trying to write some content. I need a table. That table needs custom styles to get it&#8217;s point across.  But now the css for #body, #middle, #posts, #post and #content all effect it.  I really want an easy way to be able to make some custom content with custom styles and not have to know which 25 settings I need to reset because of the &#8220;#id tag&#8221; idiom.</p>
<p>Is there a recommended way to do that?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

