Tweet
Well, the ice is broken - the new site prototype is here - it's a layout study only, mind you!
The test version is currently at
http://www.qed.de/work/clash/
So, yes, I'll make the font larger - but the text on the homepage is a dummy text only, anyway
Next step: When you click on the "Divisions" button in the left menu, you will find a list of areas of responsibilities - more or less following the areas of the "Dukes". There are some sub-topics, too (maybe we should make those in charge of these "Earls"? )
My general idea is the following: Each single page will have someone who's responsible for it and who regularly updates the content, so as to take away the routine work from Mark and me. I'm working on a module which will enable each Duke (or Earl) to edit his pages only much like you can edit messages on this forum (don't try it yet - the "edit" function appears, but doesn't run properly yet). So what's needed now is an assignment of each and every branch to... someone
You don't need to know HTML - whatever you will insert in the "edit" box will be embedded in the overall layout (i.e. the menus and all links etc. will be added automatically). What you can do, however, is to edit a text with, say, MS Word, "save as..." HTML and insert the resulting code (so your text keeps the formatting). The program will remove all unnecessary lines and just insert the page body then.
The "menu" to the roght hand side (where it says "testtext" right now) will be the news overview, so that one can easily see the newset changes (Apolyton does it similarly).
MarkG, I chose a pure CGI solution because I think the structure and content will change VERY often, and this is the only way to guarantee that any change is correctly integrated, since even a new section costs one line in the menu data file only (all menu links will be generated accodringly). If you are concerned that the server will be too busy with this, I could change it to a mode where the files are "compiled", but this would cost us a lot of flexibility. Btw., our own site runs this way for a year now, and no performance problems ever occurred.
[This message has been edited by Dominique (edited June 18, 1999).]
The test version is currently at
http://www.qed.de/work/clash/
So, yes, I'll make the font larger - but the text on the homepage is a dummy text only, anyway
Next step: When you click on the "Divisions" button in the left menu, you will find a list of areas of responsibilities - more or less following the areas of the "Dukes". There are some sub-topics, too (maybe we should make those in charge of these "Earls"?
)My general idea is the following: Each single page will have someone who's responsible for it and who regularly updates the content, so as to take away the routine work from Mark and me. I'm working on a module which will enable each Duke (or Earl) to edit his pages only much like you can edit messages on this forum (don't try it yet - the "edit" function appears, but doesn't run properly yet). So what's needed now is an assignment of each and every branch to... someone
You don't need to know HTML - whatever you will insert in the "edit" box will be embedded in the overall layout (i.e. the menus and all links etc. will be added automatically). What you can do, however, is to edit a text with, say, MS Word, "save as..." HTML and insert the resulting code (so your text keeps the formatting). The program will remove all unnecessary lines and just insert the page body then.
The "menu" to the roght hand side (where it says "testtext" right now) will be the news overview, so that one can easily see the newset changes (Apolyton does it similarly).
MarkG, I chose a pure CGI solution because I think the structure and content will change VERY often, and this is the only way to guarantee that any change is correctly integrated, since even a new section costs one line in the menu data file only (all menu links will be generated accodringly). If you are concerned that the server will be too busy with this, I could change it to a mode where the files are "compiled", but this would cost us a lot of flexibility. Btw., our own site runs this way for a year now, and no performance problems ever occurred.
[This message has been edited by Dominique (edited June 18, 1999).]
Comment