Dave, That's not always possible. We're a very small shop - one CF/database developer (me), one interface designer (Kevin), one person that handles the static sites, and one student. (Plus a few scattered "developers" who mostly deal with static stuff for a specific department.) We support 600 faculty and staff. You could say we're swamped. We have one site that we're working on right now that's a prime example. It's a soybean grower's resource site, and it has one section that's all dynamic. But, it has another section that is a "library" of content - primarily links to other sites and pdf's and word documents. Now, we could build a whole content management system to handle that, or we could let the agronomy department use their student (& Contribute) to organize and post all that static content, while I'm using my time working on developing the interactive soybean yield trials data. It's not a perfect world, but it's what we have to deal with.
So, what we're trying to figure out is the best way to do that sort of thing. We're playing around with the templates, trying to find the best combination of dynamic and static stuff, and we're a bit frustrated by our efforts. -d ----- Original Message ----- From: "Dave Watts" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Monday, September 08, 2003 6:08 PM Subject: RE: development environments > > 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
