Softpanorama (slightly skeptical) Open Source Software Educational Society

May the source be with you, but remember the KISS principle ;-)

CSS

Old News ;-)

[Sep 28, 2006]  Style from a Google letter

<STYLE>
BODY {
	FONT-FAMILY: arial,sans-serif
}
TD {
	FONT-FAMILY: arial,sans-serif
}
FONT {
	FONT-FAMILY: arial,sans-serif
}
P {
	FONT-FAMILY: arial,sans-serif
}
A {
	FONT-FAMILY: arial,sans-serif
}
</STYLE>

[Sep 25, 2006] Text-transform: uppercase  -- can render title in upppercase

<style>
<!--
.post div {
margin:0 0 .75em;
line-height:1.6em;
}
h2 {
margin:1.5em 0 .75em;
font:78%/1.4em "Trebuchet MS",Trebuchet,Arial,Verdana,Sans-serif;
text-transform:uppercase;
letter-spacing:.2em;
color:#999;
}

#comments-block dt {
margin:.5em 0;
}
#comments-block dd {
margin:.25em 0 0;
}
-->
</style>

[Sep 9, 2006] My 50 favorite design resources/CSS Galleries

Sometimes it can be hard to come up with design inspiration. CSS galleries are a great place to get design inspiration and they can also be leveraged as a great source of traffic. If you can get your design on these galleries it can drive thousands of visitors to your website.

Unmatchedstyle
cssBeauty
cssvault
Stylegala
CSS Drive
css thesis
Styleboost
CSSElite
CSS Import
Web Creme
CSS Mania
DesignShack

Comments

...I generally go to the CSS Zen Garden every once in a while just to check out what people have been doing recently...

...can i suggest the marvelous http://cssplay.co.uk ...

...Don't forget dafont.com, they have almost 7000 fonts, most of them free ...

[Sep 9, 2006] CSS tips and tricks at The Blog Herald See comments section for amendments and corrections.

Tagged:

• Design

Sep 8 at 9:18 pm by Ben Bleikamp -

Welcome visitors from Digg. The Blog Herald is one of the largest sites covering the blogosphere - and has been so for more than four years.

You can subscribe to our feed and visit our archives for more stories.

I’ve been writing CSS for about 2 years now and I still feel like every time I open up a blank file and begin writing CSS for a new design I learn something new.

For those of you that are new to CSS or experts always looking for a new trick, here are some of things I do on a regular basis to keep my code organized (kind of).

1. Size text without using pixels: rather strange idea. Why pixels are bad ?

If you’re wondering how some designers get font sizes to work using em as a unit rather than px, it’s easy. There is a trick that was written about a while ago (maybe on ALA) that resets the font sizes for the entire site so that 1.0em is the same as 10px.

body { font-size: 62.5% }
 

Simply throw the font-size: 62.5% bit into your body styling and you’re done. Now you can use ems to sizes your fonts rather than pixels.

So your paragraph styles might look something like this:

p { font-size: 1.2em; line-height: 1.5em; }

You might be wondering why it matters how you size fonts? Bulletproof design. Any major site needs to be able to withstand a user enlarging text (old people use the web too!), and setting absolute sizes is not good practice.

2. Make your code easy to read

When I was looking at some of the CSS coded by Rundle I noticed that he separated his heading tags nicely. It looked something like this:

h1 {}
    h1#logo { font-size: 2em; color: #000; }
h2 {}
    h2.title { font-size: 1.8em; font-weight: normal; }
 

Quickly scanning the CSS for the different heading tags is a breeze if you use this technique. It is also helpful if you’re sharing code or working on a large site where you are using the same heading tags (say, h2) in multiple places since you’ll be able to style each one independently and not worry about child classes inheriting attributes from the parent class.

I also use similar techniques for paragraph tags, anchor tags, and any other tag that requires multiple classes to look correct in every instance.

3. Separate code into blocks

This might be common sense to some of you but sometimes I look at CSS and it’s not broken down into “sections.” It’s easy to do an it makes working with code weeks, months, or years later much easier. You’ll have an easier time finding classes and elements that you need to change.

This is how I usuall break down my site:

/* Structure */

This is where I’d put the primary site structure divs and classes.

/* Typography */

This is where I would list things like paragraphs, headings, and other miscellaneous font styles such as small and strong tags.

/* Links */

This one is simple - all the styling for anchor tags.

/* Lists, images, etc. */

This is where I would style images, lists, and any other elements that didn’t fit into the rest of the section. If I have an unordered list for the navigation I might setup a new section for navigation and setup all the styles for the navigation, including the list and link styles, in this section - it makes editing the navigation much easier.

4. Stop using so many divs! [that's really good recommendation - <div> abuse is simply rampant]

This has been echoed by a lot of coders and standards nuts, and while I don’t think there is anything wrong with using a lot of block level elements, I laugh a little when I see someone style their article headlines using a div rather than a heading tag. Some people even style their bylines using a div! Try using the small tag or the a span for goodness sake.

5. Style everything at once: [Might be problematic, see comments "You can but watch out" and  about 5]

I noticed that I was typing “margin: 0; padding: 0;” in just about every element. I remembered seeing someone use “*” to style everything on a page at once. I decided it didn’t make much sense to define margin and padding over and over when I always gave them the same parameters.

It’s easy to do:

* { margin: 0; padding: 0; }
 

Now you only have to define margin and padding on elements where you actually want some.

Know of any other tips or tricks? Let me know :)

Comments

====

The default size of text in browsers is 16px and 62.5% of 16px is 10px. By bringing the default size down to a managable whole number like 10 (instead of 16) you can now easily do font-sizes in em units without busting out your calculator. 15px is 1.5em, 12px is 1.2em and so on. Without dropping the default size to 10px (62.5% of default) to start you’d be stuck doing multiples of 16 which isn’t fun.

===

====

believe the following link is the first time I saw mention of the margin/padding reset at the beginning of a css file. Just fyi, so if this is where you read it originally, i’m sure he’d appreciate the props from a credit link:
http://leftjustified.net/journal/2004/10/19/global-ws-reset/

===

if you do that you loose the “natural spacing” that all elements have in the browser. That means that two paragraphs following each other won’t have the natural spacing that the user might expect so you’ll have to manually add this yourself.

If you’re working on large’ish site you as a CSS designer can’t predict all the kind of HTML use there will be on future pages. Sooner or later someone will try to edit a page but all padding has gone away. I’ve seen this many times and I hate it.

Don’t f**k around too much with the way browsers work. If you break the conventions of spacing in what always matters the most, content, you’ll end up annoying the readers because it feels unfamiliar.

My 2c

===

As long as you wanna make textsizing easy, why not do this?
body { font-size: 6.25% }

Then 12px text = 12em. (At least I think so, Im tired)

CSS specification-browser support page General Syntax

Layers

Both Microsoft Internet Explorer 4.0 and Netscape Navigator 4.0 support layers created using the DIV and SPAN tags. Only Navigator supports layers created with the LAYER and ILAYER tags. Earlier versions of both browsers will display the contents of a layer, but will not position them.

In Dreamweaver, the term layer refers to any element that can be positioned at exact coordinates on the page. Positioning properties include left and top (x and y coordinates, respectively), z-index (also called the stacking order), and visibility. Positioned elements can be defined with the DIV, SPAN, LAYER, and ILAYER tags in Dreamweaver. See Layer preferences.

At 12:47 PM 08/10/97 -0800, ed_scott@corp.disney.com wrote: > > I read that the Netscape LAYER tag was turned down by W3C for > inclusion in HTML v4. This seems unfortunate as it was a very > powerful tool for information presentation. See <http://www.w3.org/TR/WD-html40/intro/intro.html#h-2.3.1> for why the LAYER element does not belong in HTML. > From what I can see there > is no other way to do the sorts of thing I want in HTML This is correct. Presentation is best specified in a style sheet, not in HTML. The Positioning extensions of Cascading Style Sheets provide the functionality of Netscape's LAYER element, with the added bonus of support from Microsoft (in addition to Netscape). See <http://www.w3.org/TR/WD- positioning> for more on CSS Positioning.

DevEdge Online Codestock - JavaScript -- very important document

Description of the LAYER tag

WDVL Cross-Browser Dynamic HTML Resources

Basic DHTML for Netscape Navigator

Transitioning from LAYER, document.layers[], and document.all to W3C Standards

Renza HTML help      <LAYER>

Layer

Cascading Style Sheets- Positioning with CSS2 Tutorial

New Communicator 4 Style Properties

O'Reilly Network- Extending the Mozilla Editor

CH9.html

Full Contents Javascript book -- copy on the Web

All of the more than 400 examples in the book have an associated BBEdit HTML Sample file on the CD-ROM in the folder named DHTML-JS_BOOK-Main_Files. Each of these files starts with the word "Sample" and are intended to be run on the Netscape Navigator/Communicator browser. You can also check out the source code for copying/pasting or alteration in any text editor. If you work on a Macintosh, you might want to get the BBEdit text editor from Bare Bones Software, which is specifically designed to work with HTML and other types of coding.

Netscape's homepage on the web is:

http://home.netscape.com/

Netscape's "DevEdge" (Developer Edge) on the web is:

http://developer.netscape.com/index_home.html?cp=hom07cnde

Netscape's "DevEdge - Library" on the web is:

http://developer.netscape.com/docs/manuals/index.html

Bare Bones Software's homepage on the web is:

http://www.bbedit.com/

The CD-ROM also contains a wealth of additional information of a technical nature on a variety of subjects including HTML 4.0 white papers, Netscape's final HTML 4.0 Guide, JavaScript 1.2 and 1.3 References and Guides.

See the last two pages of the book, after the Index, for more information about the contents of the CD-ROM.

Recommended Links

70 Expert Ideas For Better CSS Coding CSS

Last modified: November 08, 2008