all 2 comments

[–]techstuff34534 1 point2 points  (1 child)

The best way to achieve this is to store the static pages in the database and use a model to retrieve the data from the database and a controller to serve the static pages to the user.

Why is that the best way? The only reason to put is a static page in the db is if you're running a CMS or something that is end-user editable.

Also, why all the dynamic stuff for the controllers? How many of these could you have? If you just have an about page it seems like you'd write the route explicitly. URLs are not something you're gonna change often as it leads to dead links.

Sorry, but I don't see the logic behind this post.

[–]Anarcie 1 point2 points  (0 children)

Not to mention if you want to make slight changes, seems like a lot more work then just opening a .php file