Re: Using Netscape Composer to produce clean code

to follow up on what Bruce Bailey said:

> 2)	Security is somewhat compromised since we are using an ISP that (of
> course) provides only one password for our entire site.  If someone can
> post stuff regarding their program they can post stuff regarding the
> entire agency.  I am not worried about malicious behavior so much as I
> am accidents.  I will get around this problem by setting up directories
> on our site.  If someone edits and publishes a page from a different
> department, they will end up with a (modified) copy in their directory
> that will not have any links to it.

It won't break your budget to buy two sites/passwords from your
ISP.  Keep one for test and integration.  Only give your
fumble-fingered content experts the post-password for that one.
They could potentially trash one another's play space but you can
restore from the pulic site to which you hold the keys.  They
have to check sub-sites in through you.  This is not a big burden
when it is just a tree-replace after you have checked and
accepted the stuff on the preparation side of the site.

This is what the Virginia Dep't of Ed. did.  Works for them.

Al

Received on Monday, 16 November 1998 19:04:12 UTC