views:

33

answers:

0

I am working on a CMS managing my website's pages' static content. There is a PageController (the default route www.mysite.com/pages/2/page-title is used) and the corresponding Views displaying the pages' static content that can be managed using WYSIWYG editors in the administration interface.

I need to be able to specify that any arbitrary page content is not rendered statically but somehow contains information specifying that a special Controller is to be used to build the called page. The routes can differ from the default route – there is no problem with www.mysite.com/specialpagename/. The non-static pages need to integrate seamlessly – they need to have the same information stored and have to be administrated the same way the other pages do using the default CMS UI).

» What would be the best way for me to achieve this?

(I thought of using a self-parsed syntax such as specialController@specialControllerAction that these pages contain in their Content property. I then could parse this and invoke the Controllers and the corresponding Action Methods but I don't think that this is the best way.)