On Wed, Oct 09, 2002 at 09:59:48PM +1000, Roger Buck wrote:
I now vote for:
<serverroot>/<theme>/<lang>/ ./style/ ./*.css
./catalogue/ ./*.html ./*.tmpl
./members/ ./*.html ./*.tmpl
./images/
... and so on at discretion of theme author....
I think that Dorian suggested that some time ago.
Does that make sense?
Mostly, except for the location of *.css files. (I confess that I'm almost entirely ignorant about CSS, so I'll ask you to put up with naive questions, and to enlighten me when I'm wrong.) As I understand it, stylesheets specify colors, fonts, and all of those little presentation details. In particular, AIUI, stylesheets do not specify content. So why would the *.css files go in <theme>/<lang>? How are the French link colors different from the Italian or German colors? Okay, so the Japanese and Cherokee versions of the web page will obviously use different fonts. But most everything else will be identical across languages, right? Perhaps there should be theme-wide CSS and a separate per-language CSS? I'm mainly concerned with duplication ("Pragmatic Programmer" tip #11: Don't Repeat Yourself). If default/en/style/foo.css and default/jp/style/foo.css are separate, and need to be kept in sync, they _will_ drift apart. The same thing applies to language-specific templates. Of course, this applies mainly to the source. In the installation, it might be more efficient to have duplication. That is, have serverroot/default/en/style/foo.css and serverroot/default/jp/style/foo.css be automatically generated from source/foo.css, source/foo_en.css, and source/foo_jp.css. This should be done by 'make install' (which of course implies that there should be a Makefile). -- Andrew Arensburger This message *does* represent the arensb@ooblick.com views of ooblick.com I feel more like I do now than I did before I started.