carl_galloway wrote:Starting with the link to the from that Dave suggested, wow, I've never seen a css form that looks that good.
I haven't really looked at the code, but personally, I think it's a little over the top. I do, however, like those info boxes
carl_galloway wrote:my fear is that we would need to update the templates every time a plugin gets an update, just think of how many updates the contact form has had recently
I have to admit I've lost track on the contact form updates, I have zero idea what it can do now, all I know is it has been improved a lot lately
carl_galloway wrote:I've often thought the way to deal with the calendar would be to put a hidden link in at the top of the table which points to the archives page so that disabled users can still get to those entries, then make the archives page css only, which is much easier than converting the calendar.
http://sandbox.yellowled.de/archive already
is CSS only, so that's covered. However, disabled users don't have to use the calendar, as long as the blog has the Archives sidebar plugin. So maybe we should simply add a skiplink to the archives page and leave the calendar as it is?
carl_galloway wrote:backgrounds/headers, we're really talking about two different things aren't we, how many templates use a background image, probably most of the modern graphical templates, but as Dave says they are mostly just a gradient with a repeat so do we really need to support changing this in the config, or should users simply overwrite the template background image with their own version?
Well, originally we were talking about a background image for the header
If we're talking about a template background image, that should be a piece of cake. If img/background.png is present, it will be tiled. If you don't want a template background image, don't include it. Period. Anybody who wants to do more advanced stuff will have to be familiar with CSS anyway.
Now, that #!?$ header image ... we're not going to get a solution with an upload box in the theme options, so the easiest way probably is to have users overwrite a standard banner like img/banner.png (I am, by the way, all for using png images only).
However, the question remains how to include that properly. Basically, it's not a problem to give the blog a fixed width using the wrapper div. But some people (like me
) prefer to have a flexible width for the wrapper, which makes it a little tricky to have a banner. So how about this: basically, the banner image is assigned "top center no-repeat" to the header. That way, it will still look acceptable if you have a banner 600px wide in a wrapper that's wider. In addition to that, we'll have a theme option for the width of the wrapper div, i.e. a dropdown box with the options 760px, 970px, or 95%. We could also have a second theme option to set the height of the header ... that way, people can also choose whether the banner should have a border by simply making their banner smaller.
YL