🚀 go-pugleaf

Dr. Peter Kittel wrote:

> What else does one need than C:Ed? Ok, our web designer likes luxury,
> he used CygnusEd for our pages :-).
> 
> Those "WYSIWYG Web editors" just give their users the false impression
> that WYSIWYG were possible on the Web. It's not, and thus I think it's
> only half as critical what tools you use to do it.

The closest one can get to wysiwyg is saving the page, then view it with
different browsers to get an idea of how the page looks.

But, that isn't important.

The most important things when making web-pages is concistency and ease
of updtading them. How can this be achieved? A web server combined with
a database system.

How does this work?

Each local page (ie. served by your local web-server) should be made in
the following way:

- First add an entry to the database, telling the name of the page,
probably the author, language, and other specifics which might go into
the header or meta tags. And most importantly, the file name of the
page. Perhaps also the next and prev page references, table of contents,
and other standard links of the web-pages. (Part of concistency.)
- Then make a file with plain text. Where ever there are links, one
should write <The Amiga Web Directory>. Why, because the server/db will
substitute that with data from the data base (like <A
HREF="http://www.cucug.com/awd" IMG SRC="awd.logo" ALT="The Amiga Web
Directory>). That will ensure concistency, and each time awd moves, you
only have to update the data in the database.
- Make styles. Ie. instead of hardcoding <I><B>A<B><I><FONT="+1"> make a
style <FIRST>A</FIRST>, which substitutes all that with something easier
to write. That's ease of updating.
- Much more can be thought of; much use of the database will make the
web site easy to maintain, and ensure that new information will be
indexed properly and presented in a way which will not conflict with the
overall design of the site.

Paul K Egell-Johnsen

mailto:paulken4@afrodite.hibu.no
http://afrodite.hibu.no:8001/paulken4/