Re: Link Management

On Wed, 15 Sep 2004 02:50:50 -0700, Robert Koberg wrote
> 
> I also have posted why I 
> felt relying on redirects for link management /in the CMS/ was not a 
> good idea.

Sorry, I think I missed this, or misunderstood the context - can you resend
the text directly to [email protected]?

> I guess the bookmarking problem would be better handled by a CMS 
> that edits the live site directly and has the ability/knowledge to 
> affect the webserver. I personally don't think a CMS should edit the 
> live site directly without a development and QA stage, but that is a 
> different topic.

I may be misunderstanding again, but I am interested in more perspective on
this topic as well.  I know it's critical to have a staging environment for
previewing changes, but I think that can be a logical environment, not
necessarily a separate physical box.  To some extent it seems to depend on the
scope of the enterprise and project, as well as the type of work and worflow -
in many organizations a separate staging environment could be overkill (though
I for one hate making changes in production without a rigorous
build/test/release engineering discipline).  So as long as changes don't
affect the published site without workflow, I don't see the problem with edits
being performed in a CMS on the same server as the live site, unless the CMS
is such a pig that it degrades performance for end clients.  Tight integration
between webserver, appserver and CMS really streamlines implementation and
allows all sorts of functionality that can be difficult in a custom integration.

I used to think it was important to separate the CMS from the live site,
hoping to modularize the components, but now I see CMS getting so embedded
that it can never be swapped out - even migration to the latest major CMS revs
can be referred to as conversions rather than upgrades.

Thanks,

   -John