Multiple Views or db records

[eluser]mddd[/eluser]
The idea of not putting html in a controller or model is valuable, because it makes managing the application easier. In principle, a designer should be able to change the design of the site by only working in the views folder. That's why it is better not to build tables inside a model, etc.

But this doensn't mean that all your content has to be in a view. There can be a difference between the html of your site layout, and the html that is the real content of your site. Imagine a site with 100 000 pages.. they can never be all views. They should be in a database!

So, html-content in the database - fine. Building pieces of html in a model or controller - not so fine, because it makes maintainance harder.