I am creating an MVC 4 web app written in C#. Among other functionality, one feature should allow a user to navigate to a page like this:
/pagecontroller/some-specific-page-name
Or, alternately,
/pagecontroller/12345
The contents of these pages are largely static html. It rarely changes.
I'll be the only one adding new pages, and I'm happy whether I do it in html or via a CMS.
What method of storing and handling this sort of content is suggested?
Should I store the html in the database and deliver it that way? I certainly want some page-specific information in the database (e.g. page categories, etc) but putting a hunk of html in the database doesn't seem right to me. Alternately I could create a database that has article names corresponding to static html documents that could be plucked out via ajax. The styling will not take place on these pages, so I see no issues there. Still, as articles build up that didn't feel 100% right either. A third, rather silly idea, is a table called elements. Each row would contain one or more elements and the code could, using a sort of template, place the elements where desired.
The real trick is I want this to be able to scale well from a small project to a larger one as needed.
I'm not using webkit.
How do you suggest I go about this? Thanks very much.
EDIT: I should say - none of these pages contain any forms or need much in the way of server-side might.