YES, absolutely YES, take up the responsibility, but sit close to the developer to continuously review what is possible and what is not. Dont allow developer to code php to make changes. Small css changes are ok. Document all change, and test all the changes after a upgrade/update.
CMS's although promise a whole shit load of flexibility, agility, configurability and features, dont deliver to it. They primarily depend on plugins and themes developed by a bunch of developers out there. Each developer creates a plugin/theme, based on what he/she understands best. And frankly, like any software development project many of these fail big time. The ones that pass (fast) have the following in common
- Most probably the first one developed to solve that problem
- The summary is well documented from the list when a search is performed
- Screen shots clarify exactly, nicely the most important parts of configurability
- Features are listed in a nice and clear manner
- The plugin is being developed, fixed and bug fixed regularly
Ratings take a hell a lot of time to build, if there already have competition. A few bad ratings in the first can kill growth.
So a CMS along with the plugins that you will use needs to be understood very clearly by Experience Designers / Architects. If not, you have to be very patient and flexible to what your developer finds to use straight off. You "wont" get exactly what you need, but you will get close. Dont expect too much customization on the plugin/theme used, since with updates, you can loose your changes.
So CMS, comes with its own set of challenges. If you customize the css, on a update you need to test all those "customized changes".
If your developer does not get a plugin that you need, then you have to look at the options he may have. So you need to be close to him, not remote across the world.
If your developer changes php files, and css files. Oh man, are you asking for trouble. Since you are using a CMS for just that reason, to avoid coding right ? Reasonable changes are ok, but dont go overboard.
And trust me, small changes that architects/designers ask for can have crazy impact during updates, upgrades.
But dont shy away from CMS. The benefits surpass all the above pitfalls. For example, you can manage the content very easily, and not have a developer involved after you deploy. Visit (www.mcruiseon.com) made completely using Wordpress with Graphene theme and S2member plugin (just listing the essential plugin, there are a lot more). To understand more about wordpress as a CMS, visit here.