hmmm .. Thank you for the feedback, unfortunately I was hoping for a much slicker method. Using parameter/value pairs (mysite.com/cmscontroller/id/1234) is good for viewing things like news items or article items, however I don't like that approach for actual page names. In my experience clients can be picky about their URLs, especially when they advertise them. I think people may complain if I tell them to print "mysite.com/services/id/1234" on a brochure instead of "mysite.com/services/service1/features/".

In addition, this wouldn't resolve the problem of a site with 20 or 50 (although that may be unrealistic) "top level" pages (mysite.com/a, mysite.com/b, mysite.com/c, mysite.com/d, etc). It seems odd that I would be forced to create a different controller for all of these pages even though the logic for them will be the exact same. Either I'm misunderstanding (which I admit is probably the case), or MVC is better left to web applications, not basic websites with tonnes of pages. Separating content from process is great, but now I'm stuck with choosing between unfriendly URL's, or having redundant controller files that all do the same thing.