A co-worker of mine sent me this link. Its a tool that will go through your css code and find any fixes that will be needed for IE6. It’s very useful because many of my clients work in environment that are still using old browsers.
Many people use a hidden content editor webpart for this purpose but there is a second option. On each page layout there is a Content placeholder called “AdditionalPageHead”.
<asp:ContentPlaceHolder id="AdditionalPageHead" runat="server"> </asp:ContentPlaceHolder>
Anything placed inside this placehodler will be added to the head of the rendered page.
You can also create your own custom placeholders in the masterpage and page layout to allow you to add items to any part of the masterpage. For instance I have created a custom placeholder to insert webparts in the footer area of the masterpage.
I have been usin wordpress for about two weeks now and never thought of using it as a CMS solution. In most cases I use Joomla, Drupal or DotNetNuke for CMS sites. I built my first non-blog WordPress site. It was alot esier than I expected and customizing the template to act like a regular site was easy. Here is a link to the site (I did not do the design just the implementation) http://givetomorgan.com/
Here are some additional resources on using WordPress as a CMS
Designing for IE6 means you must consider its lack of support for PNG transparency. There are many PNG hacks out there, I prefer this one from Unit Interactive Labs . The problem with this one is that it has to read through the whole page searching for PNGs to fix which cna make load times noticable slower. I was trying top find a faster solution when I remembered that SharePoint uses PNGs on some of its pages.
On the all items view of most lists Sharepoint uses a png image. Built into the core code is a png fix that allows this image to work in IE6. You can take advantage of the built in png fix by using the following tag:
<asp:Content ContentPlaceHolderId="YourPlaceHolderName" runat="server"> <SharePoint:ViewIcon Width="widthInPx" Height="heightInPx" runat="server"></asp:Content>
The tag will need to be inside of a content placeholder tag. You can name the placeholder whatever you want that makes sense. The placeholder canb be wrapped in a DIV tag for positioning purposes.
The ViewIcon tag will require a width and height to render properly and will not work for background images.