[En-Nut-Discussion] New website design

[Edwin van den Oetelaar]

Harald Kipp wrote:
> Edwin van den Oetelaar (Oetelaar Automatisering uit Best) wrote:
>> I have to agree with Ole.
>> There should be an automatic site map and bread-crumbs trail.
> 
> I agree too. BUT...
> 
>> Also the Tab-pages could be menus.
> ...
>> I sure hope that you have all this stuff in a database/CMS system.
> 
> There are two opinions in our company. One is lead by Niels, who is a
> professional print designer. They are currently working with Typo3. The
> other group is my humble self, without any chance to enforce his view of
> basic HTML design, _except_ for ethernut.de. I'm generally claiming,
> that the Ethernut community wants information, not design frippery.
> 
> Edwin, I'd have expected more loyalty. ;-)
;-)
> 
> I may be a minority in my company, but the most visited sites, probably
> google and wikipedia, share my view.
> 
> Harald

Harald, I think you mis-understood my remarks.
I am all for a completely flat html presentation.
I work with browsers that do not have JavaScript or Flash enabled.
Also I would like to view sites from my mobile phone which does not do
javascript and fancy other stuff.
I think that people who make flash and javascript essential to view the
basic content of their website are completely missing the point of what
the web is.

So XHTML is what you should present to the user. We agree on that.

However, the point I want to make is that the content should be
generated dynamically (perl/CGI/php/whatelse) or statically
(perl/makefile/frontpage ;-) or DreamWeaver) from one (1) code base
(your information content).

This makes sure that all presentation and navigation is consistent.
It also makes updating much more easy, since you only update one page
the rest is regenerated. If you change the way some part is generated,
like eg. a menu, it only has to be updated in one place.
I say this because I have some experience in this field and this method
has proven itself to me.