TFS 2010 branch strategy for daily web content changes
===

We have a group of .net web projects that are maintained by both a team of developers and a team of content managers.  Content managers are allowed by company policy to make and deploy content changes to the production servers pretty much on demand. The development team, on the other hand, works on releases which last weeks and move through a structured lifecycle.

I'm trying to settle on a branching strategy that best supports this kind of dual development.  The best I can come up with is a Main branch that's always in-sync with production, a Dev branch where we work on the next code release, and a Content branch that functions something like a "hot fix" branch in most of the guides I've found.

Can anyone point me to a better model?  
Is there any way to force the content managers to merge their changes into Main and Dev as they check them in?

And yeah, I know there are content management systems out there as well as better ways of handling code/content separation, but this is what I have to work with.

Thanks in advance!