/******************************************************************************* Basic HTML selectors still need to be prefixed with the "lia-custom-header" and "lia-custom-footer" class so they won't conflict with the Lithium Community CSS. An example of a common conflict goes like this... - With no prefix, the following generic CSS would affect all unordered list items on the page, whether intended or not: ul li { background:url(image/bullet.png) no-repeat 0 0; } - With the prefix, we only affect unordered list items contained in the header and footer, as intended: .lia-custom-header ul li, .lia-custom-footer ul li { background:url(image/bullet.png) no-repeat 0 0; } *******************************************************************************/ /******************************************************************************* Again, we need to wrap the header and footer content styles with the "lia-custom-header" or "lia-custom-footer" class because there is a possibility that generically named classes such as ".message-list" or ".content" may still conflict with the Lithium Community CSS. In general, it is also good practice to use company specific CSS classes to avoid CSS conflicts with third-party add-ons. *******************************************************************************/ /******************************************************************************* tag customization and site-wide styling is handled in the skin CSS rather than the header/footer CSS. We have basic centering CSS here for demo purposes. If you require the use of classes and mark-up that wrap both "lia-custom-header" and "lia-custom-footer" to make your header and footer work, add them here so they can be merged during the skinning process. Use company prefixed CSS classes to reduce likelihood of CSS conflicts (".acme-wrapper" = good; ".wrapper" = bad). *******************************************************************************/