Re: Dynamic CMS Publishing?

This is exactly what Bricolage does.  Components can be published for 
request-time evaluation and the components can be for any language 
(SSI, JSP, PHP, HTML::Mason or whatever) -- the CMS need not know anything 
about a component system, just how to invoke something that does.

This design is directly descended from the CMS in production at Salon.com; 
Bricolage is in production at a number of big sites (check the Bricolage 
web site for a list).

As far as using the CMS for handling form submissions from end-users... 
the use case isn't clear but if it were upto me, I'd batch them up for 
asyncronous imports into the backend data repository (though only if it 
_had_ to somehow be used for relationships to the editorial data) but, in 
general, editorial content and user data should be managed separately.


On Fri, 14 May 2004, Peter Bell wrote:
> 
> Does anyone out there have experience of using a publishing model but
> publishing to dynamic (e.g. aspx, cfm, php, etc.) files? For example,
> you have content personalization where there are 3 articles on a page,
> but depending on user group you may only see one or two. Rather than
> doing EVERYTHING dynamically, you publish to a single simple script file
> but you publish switching logic that checks for session variables and
> you may include personalization tokens so you can have a Hello
> %FirstName% even though the site is published.
> 
> I'd be interested to know how widespread this is. I'm doing it in my new
> CMS to get balance between performance and personalization, but would
> like to get an idea of how others have implemented similar systems.
> 
> Also, if anyone has gone this route, do you have any experience of form
> handling on published sites where you want to use the back end CMS for
> form handling? I guess the obvious way is for the published site to just
> use the form action to call the CMS site that would run validation, save
> to db and create any workflow tasks/notifications before either
> displaying the thanks page or redirecting back to the thanks (or error)
> page on the published CMS. Again, any thoughts on best practices much
> appreciated!
> 
> Best Wishes,
> Peter
> FreshStart Software, Inc.
> 
> 
> ---
> [This E-mail scanned for viruses by Declude Virus]
> 
> _______________________________________________
> CMS mailing list
> [email protected]
> Subscription controls:
> http://lists.cms-forum.org/mailman/listinfo/cms
> Netiquette FAQ and related CMS lists - [CMS-Forum], [CMS-Meta], [CMS-PR], [CMS-Develop]
> http://www.cmsreview.com/NetiquetteFAQ.html
> 

-- 
Ian Kallen <spidaman _at_ arachna _dot_ com> | Yahoo/AIM: iankallen
                      http://www.arachna.com/