[eluser]mddd[/eluser]
If it is something you are showing in the view, then why is that breaking MVC? I don't see why it would be a problem to put a page of static content in a view and then just have a controller that does nothing but load the view. The overhead in that will be very low. Especially if the controller does not load any unneeded models and libraries. I often make a controller called 'static' that takes 1 argument, namely the view to load. So if you call /static/disclaimer that will display views/disclaimer .php. The 'static' part can even be 'removed' by using routes so the user only sees the page as /disclaimer. I think it is still good to show the page via CI and build your headers, menus etc. in the same way as you do on your other pages. To avoid duplicate content en update troubles.
