<?xml version="1.0" encoding="UTF-8"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>TDAC Forum Topic: CSS Basics</title>
<link>http://tucsondigitalarts.com/forum/</link>
<description>TDAC Forum Topic: CSS Basics</description>
<language>en</language>
<pubDate>Thu, 28 Aug 2008 09:14:50 +0000</pubDate>

<item>
<title>foundry on "CSS Basics"</title>
<link>http://tucsondigitalarts.com/forum/topic/css-basics#post-5</link>
<pubDate>Fri, 04 Apr 2008 11:52:27 +0000</pubDate>
<dc:creator>foundry</dc:creator>
<guid isPermaLink="false">5@http://tucsondigitalarts.com/forum/</guid>
<description>&#60;p&#62;This is a topic that is probably very important to a lot of us who use the web for our professions: &#60;strong&#62;CSS best practices&#60;/strong&#62; (or &#34;only the facts please.&#34;)There are a lot of problems in trying to unite the many different browsers out there, so it is very important for us to use a well defined list of objectives to help us coordinate and streamline our workflows.It's hard to create a comprehensive (professional) list. I have researched a few lists like what we need. (A great one is at &#60;a href=&#34;http://www.smashingmagazine.com/2007/05/10/70-expert-ideas-for-better-css-coding/.&#34; rel=&#34;nofollow&#34;&#62;http://www.smashingmagazine.com/2007/05/10/70-expert-ideas-for-better-css-coding/.&#60;/a&#62;) This is a lot of info and many people have different opinions. Therefore it is good to discuss this as a forum post.In my opinion, I think that it is important to start with why CSS was invented. No more tables!! They were to clunky to style and definitely didn't work across all browsers (Netscape vs. IE.)So our best practice should be: &#60;strong&#62;keep that CSS light!&#60;/strong&#62; This one is pretty easy. For programmers, it is best to be elegant (it's fashionable!)&#60;/p&#62;
&#60;p&#62;A couple of things:&#60;/p&#62;
&#60;ol&#62;
&#60;li&#62;-Reduce inline styles: I think that the only exception that I have run into here is the notorious html newsletter. But when working on a big website, it is pretty easy to see why we avoid inlines too much: &#34;where did that extra big, bright green border come from?&#34;&#60;/li&#62;
&#60;li&#62;-Use your inheritance: we can significantly cut down on complexity with some knowledge of the box model (http://www.w3.org/TR/css3-box/.) This is the basis for our div structure.&#60;/li&#62;
&#60;li&#62;-Also implied is the reduction of fixed sizes for as many of the page elements as possible. Let the parent do the work for the children.&#60;/li&#62;
&#60;li&#62;-Watch that notation! Using semantics in CSS may be one of the most important problems we have here. Proper grouping and naming will save us many hours of unpaid work!&#60;/li&#62;
&#60;/ol&#62;
&#60;p&#62;There are a lot more. But I have to go back to work now. Others?
&#60;/p&#62;</description>
</item>
<item>
<title>admin on "CSS Basics"</title>
<link>http://tucsondigitalarts.com/forum/topic/css-basics#post-4</link>
<pubDate>Fri, 04 Apr 2008 10:22:43 +0000</pubDate>
<dc:creator>admin</dc:creator>
<guid isPermaLink="false">4@http://tucsondigitalarts.com/forum/</guid>
<description>&#60;p&#62;The basics of Cascading Style Sheets (CSS) and how to use them to structure websites.
&#60;/p&#62;</description>
</item>

</channel>
</rss>
