Okay, guys - Easter break's over, time to get back to work
Well, basically, I think we don't have any work left. I've just now uploaded the latest update including that visibility fix for the spacer png in the calendar. Hopefully, that was the final IE bug we had to smash.
However, I recently got Dan Cederholm's "Bulletproof Webdesign", and Dan has some interesting ideas which might or might now help us improve bulletproof even more, so I thought I'd run them by you.
First of all, Dan suggests a different approach to font-sizes. His way is to assign a keyword size (font-size: small;) to the body and use percentage sizes for everything else. I'm not sure whether this is really an advantage over our approach using percentage plus ems.
Another idea would maybe make it possible to convert any of our layouts to be content first - I have to take a closer look at our code, but the basic technique behind this is to put the left sidebar (in a 3-column layout) into a container div with the content. However, that's extra markup ...
Here's another idea which came up in a thread in the German forum. We could pretty easily strip the sidebar plugins of excessive divs using sidebar.tpl. I'm not completely done figuring it out, but basically, we could use something like this:
Code: Select all
{if $is_raw_mode}
<dl id="serendipity{$pluginside}SideBar">
{/if}
{foreach from=$plugindata item=item}
<dt class="serendipitySideBarItem container_{$item.class}">
{if $item.title != ""}<h3 class="serendipitySideBarTitle {$item.class}">{$item.title}</h3>{/if}
</dt>
<dd class="serendipitySideBarContent">{$item.content}</dd>
{/foreach}
{if $is_raw_mode}
</dl>
{/if}
Now, I don't think any of this is
necessary, and at least the content first technique would mean to seriously reconsider the index.tpl, so that might be quite of a hassle. The font sizes should be fine the way they are, and personally, I can live with the sidebars just the way they are now.
That's why I wanted to hear what you guys think.
YL