Yeah, I use the MVC pattern for large applications... But for a portfolio I personally hardly see the point, unless it is a very big portfolio.
What I was getting at though, was the resulting URL. Whether he uses one page or many pages, using:
Where x is a number, just doesn't seem appropriate to me for a small site where the content is clearly separated and the creator knows whats going to be on each page.
For example, within a forum or a blog, you will often find entries referenced by their ID's... why? Becuase the person who puts the forum online does not know exactly what will be posted and how many times etc. You can get systems for vB that clean up URL's to make them more friendly (eg: this would become something along the lines of
However when you have a low number of pages, and you know exactly what each page contains, I feel:
- It is a waste of time to implement an MVC pattern unless you want to for the learning experience
- It is bad to use page Ids which is probably not helping search rankings or anyone looking at the URL
- There is nothing wrong with using some good old static XHTML to build the pages
Basically what I was trying to get at was that the result isn't good in any terms... Although I dont see anything wrong with using some static HTML or multiple pages for a something small like this, even those that think MVC should be used for everything should be able to see that this is a bad implementation.