> Dave, you've hit on one of the key reasons Deanna is asking. > We also are trying to support Contribute users on the same > sites. So we are looking for an environment or process that > will support the Contribute file management as well as the > CF developers. That means we can't use FuseBox or any other > framework that breaks things such that Contribute can't edit > the pages. Ideally we're also shooting for something that > would prevent the CF devlopers from overwriting what the > Contribute people are doing and vice versa. > > (I work with Deanna and she got tied up in a meeting so I'm > jumping in.)
Out of curiosity, why are you mixing static and dynamic content anyway? I think Contribute is great, but I wouldn't recommend its use for a dynamic (or partially dynamic) site. At some point, you risk getting the worst of both worlds - an environment which has all the drawbacks of static sites, but all the infrastructure (and its associated drawbacks) of a dynamic site. I would recommend that you separate your static and dynamic content as much as possible, and limit your use of Contribute to the static portion. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/lists.cfm?link=t:4 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
