J Graham Zahoruiko wrote:
> Or, don't even use the CMS for publishing. The CMS should be used for
> managing content (Create/Workflow/Version). The database or file server for
> storage. And your preferred application servers and Web scripting languages
> for publishing.
> CMS scalability problem solved & eliminated!
I agree that the CMS and the final product should be separate. But, you
can publish out to that final product -- whatever that is. For example,
for one project we are publishing out to a large scale portal
application that makes use of Jive Forums and a number of other dynamic
features. The CMS is used to create the portal as 'statically' as
possible, sent through the staging process (the CMS manages promotions
in this case). The live version has nothing to do with the CMS.
I have never understood why pages have an 'edit this page' that I can't
please trim your posts.