EXPRESSIONENGINE The CSS mentioned here is typical of (Yahoo web space)
EXPRESSIONENGINE The CSS mentioned here is typical of the various navigation styles, in that many classes are grouped together as they have equal properties. Be aware that mak- ing one change will affect several link states on your menu. A word of caution Be sure that you re still saving template revisions here (Admin . Template Preferences) because menu customization has you tweaking all the various nav styles, and it is easy to stray from a working model into a mess that fails on some browsers. Work step-by-step, pixel-by-pixel, and never make more than two moves before saving and checking the results. #content The #content id does little more than hold the sidebar and the main column together. Just think of it as important stitching that just happens to have a 10px margin between the previous navigation and the columns it contains. Edit that 10px setting to tighten the stitching: #content { margin: 10px 0; } Inheritance CSS is full of shorthand, and once you understand how this works hand-in-hand with markup, you can save a great deal of time and effort, and avoid overdeclaring classes. Perhaps the best example of this efficiency is inheritance. Let s say you are using an unordered list in your sidebar, and another one in your main content, and you want to style each differently. You might add a unique indicator to the
- or
- items for each, but it bloats the markup and will make redesigning your site much more difficult. Who owns what? The key here is that one list lives inside your #sidebar column, and the other lives inside your #blog column. So, in the CSS you can assign a set of list styles to each id, so your list markup contains no class declarations because you specified in your CSS that a list within a certain id should look a certain way. Here s how it works for your sidebar links: #sidebar ul { list-style-type: none; margin: 0; padding: 3px 5px; border: 0 solid #CCC; color: #666; } 159