Structure of our websites (in CVS + on the servers)

Christoph Cullmann crossfire at
Wed Oct 9 20:10:23 BST 2002

Hash: SHA1

overlooking the current mess in www + the mass of * domains (some have 
even own cvs modules) I would like to know if it wouldn't be possible to 
clean that up a "bit". ;)

My proposal would be:

a) move the applications homepages to www/apps/"appname" + make the 
"appname" domains pointing to that + create a index in www/apps which 
shows what application are around there with links

b) move ALL * subdomains into www/areas/"areaname" + make the 
"areaname" domains pointing to that (and again index)

c) move ALL internationalisation pages to www/i18n/?? (or www/international/?? 
or even seperated www-?? modules)

d) let all this pages (after we have our new design ready + xhtml conform) use 
the templates located at www/templates to get one corporate identity look for 
the whole kde web sites (but that is AFTER we have done the first hard 

e) use <base href=""> (and let the * domains not 
change the docroot, only redirect them to the given subdirs, which will make 
links consistent to the base url, which might be set different (like 
www.kde.?? for the translated websites which will get a document root set to 
www/international/?? or www/i18n/??)

Would that be possible ?

BTW., would be nice to get a common suffix for the pages that are written in 
php, should we use .html (as now on or the more comment .php 
suffix (if .php should be it, please change that the server accepts 
index.php), the includes will get .inc.

Please constructive answers, no flames ;P
This mail goes to kde-core-devel + kde-www and the sysadmin(s), please feel 
free to forward to any other people involved in the www stuff.


- -- 
Christoph "Crossfire" Cullmann
Kate/KDE developer
cullmann at
Version: GnuPG v1.2.0 (GNU/Linux)


More information about the kde-core-devel mailing list