I've just finished going through and switching all the templates to an even better layout. Now you can easily make your site use a 3 column, 2 column or 1 column layout by editing the luna.css file (and of course it's cross browser compatible!). It also fixes some of the limitations of the previous layout. However, this means that the people who have already customised their templates will have to do it again (well it is a beta!). Shouldn't be too much trouble doing so though.
I've been testing everything in multiple browsers (win: ie5, ie5.5, ie6, opera 7.x, mac: safari, ie5, linux: firefox 1.0.1), so it should be fine.
Already thought of that and it's already supported. If Category_Template uses the <template set>.<theme> format then it will use the theme. Note that you can't name your theme html or htm since those denote templates with Category_Template (if anyone is using something else for template names you should let me know [ie. not *.htm or *.html]). Everything else without a . in it means it's a template set.
Actually, due to the way Gossamer Links modifies the output html, we can only make things transitional compliant (and plus it's already a pretty big jump to xhtml for most people, so we don't want to force them to code in Strict). You also probably don't want XHTML 1.1 since it's requires things like making the Content-Type of the document application/xhtml+xml, which many browsers (eg. Internet Explorer) do not support. However, XHTML 1.0 allows for sending documents as text/html.
Thanks!
Adrian
I've been testing everything in multiple browsers (win: ie5, ie5.5, ie6, opera 7.x, mac: safari, ie5, linux: firefox 1.0.1), so it should be fine.
Already thought of that and it's already supported. If Category_Template uses the <template set>.<theme> format then it will use the theme. Note that you can't name your theme html or htm since those denote templates with Category_Template (if anyone is using something else for template names you should let me know [ie. not *.htm or *.html]). Everything else without a . in it means it's a template set.
Actually, due to the way Gossamer Links modifies the output html, we can only make things transitional compliant (and plus it's already a pretty big jump to xhtml for most people, so we don't want to force them to code in Strict). You also probably don't want XHTML 1.1 since it's requires things like making the Content-Type of the document application/xhtml+xml, which many browsers (eg. Internet Explorer) do not support. However, XHTML 1.0 allows for sending documents as text/html.
Thanks!
Adrian