Thank you for the reply Toppy, however I believe you misunderstood. I actually have viewed the new layout webinar and do plan on using that approach, however my question was related to the framework files (mostly controllers), not just the layout. For instance, take the following URLs:

mysite.com/index
mysite.com/about_us
mysite.com/services/
mysite.com/services/service1
mysite.com/services/service1/features
mysite.com/services/service2
mysite.com/services/service1/pricing

My understanding of Zend Framework and MVC is that I'd need a controller for index, about_us, and services. In addition, I'd need view scripts for service1 and service2. Anything after the view sript is supposed to be variable/value pairs, so I don't even know how that would work (third, fourth, fifth level directories), but it's besides the point. The problem is that with a CMS I have no idea what pages the user will create, and how many child pages each page will have. Let's say a user wants to create two new pages, one being mysite.com/contact_us, and the other being mysite.com/services/service3. From a coding standpoint, do I need to dynamically create a new controller and view script for the contact_us page, and dynamically create a new view script in the already created services view script area for service3? I plan on storing the actual page content in a database or XML file, therefore the view scripts won't even contain the main content, so it would be nice if I can have one controller and view script handle everything.

BJM