Nothing Special — OZONE Asylum, home of the Mad Scientists

Nothing Special

This page's ID: 27321

Edit Post

Who can edit a post?	The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.

Your User Name:
Your Password:
Login Options:	Remember Me On This Computer

Your Text: Insert Slimies » Insert UBB Code » Close Last Tag \| All Tags UBB Help	I do think these colors work better- FWIW. There are still a lot of code issues going on here. I've taken the liberty of restructuring the code, matching your style as closely as possible - http://www.in-dented.com/temp/brakecheck.html The key problems with your HTML are ones of structure/heirarchy. The markup exists to rpovide the document with a logical structure - the CSS exists to handle anything style related. Headers - the <h1> - <h6> tags exist to help define the heirarchy of the page. Therefore you'll note in my code that the top most header (HARTAKE) is coded as an <h1>. The scoend most header, defining the partiuclar page within the site, is coded as an <h2>. It is debatable where the headers for the "pages" and "favorites" fall, semantically speaking. I have coded them here as <h3>'s. The headers within the main content area are coded as <h4>'s, and finally the headers for the lists beneath the images are yet one step further down the line, and are coded as <h5>'s. The use of the <p> tag with a special class to define headers is very poor practice and should be avoided at all costs. The use of an <li>to define the header for the list is also very bad practice. The header belongs before the list, and belongs within the proper tag type. Overall document structure - The use of ID's and Classes, and the names you give them, are important for the document structure. Names like tbox, seebox, lebox, rebox, etc, don't tell us anything about structure. Also, as I noted above, for boxes that are set elements, such as the header, the footer, the main content area, the navigation area, and the links area, should be defined by ID's. You'll note in my code, the top box is <div id="head">, the .tnavbox has been eliminated - it was totally unneccesary. The content area is <div id="content">, the nav box is <div id="nav">, the links box is <div id="links">, and the footer is <div id="foot">. This gives us a logical structure to work within, and by making proper use of CSS, eliminates the need for a lot of repetitive classes later on. You'll note that many of the classes are no longer there - they aren't needed. By making use of CSS and the parent/child relationship between the elements on the page, you can streamline your code a great deal. Note the #nav ul, #links ul { ... } and the #nav ul li, #links ul li { ... } this bit defines how a list within the #nav and the #links will be displayed, and allows you to avoid using a class name for you <ul>. If you look through the code, you will see a lot of this. It is very important to look at the structure of your site, and to code it accordingly, keeping your structure, content, and style as seperate elements. I hope this helps, and I hope you will ask for clarification on anything that does not make sense. *please note, I have not done extensive browser testing on my example page, and have not tweaked the CSS to make a perfect match with your site - there is plenty of room to play around and clean things up further. [url=http://in-dented.com/sigs.html][img]http://in-dented.com/sigs/knot_sig_32.gif[/img][/url] Loading...
Options:	Enable Slimies Enable Linkwords

« Backwards — Onwards »

Show Forum Drop Down Menu