>>>>>>Hi,
>>>>>>
>>>>>>I am starting to re-write my web site that I created back several years ago using VS 2005. Now I am using VS 2012 ASP.NET web site feature. My question is, is creating a Master Page for the site a still best practice? If so I will update my Master Page and use new HTML5 elements. But if you (collective) think that Master Page is yesterday's approach, please let me know.
>>>>>>TIA.
>>>>>
>>>>>Just curious - did you consider moving it to MVC ?
>>>>
>>>>I understand that MVC may have advantages when creating a database application (I personally don't know enough about it to say if it is so). But I am discussing in the thread a static web site (product information) that - most likely - will not deal with database. Do you think that MVC would have advantage in this case?
>>>
>>>I would not describe MVC as data centric, other than in the sense that just about all computer applications are data centric. Managing and presenting data is what they do. I would describe MVC as one implementation of a three tiered design pattern. Data, called the Model in MVC, is one of the three tiers.
>>
>>And since my static web site has no Data and no Model, what would be the purpose of using MVC? Control what? :)
>
>Since you are not connecting to data there is no reason to use MVC. Any plain old web design tool would do.
>
>And yes, Masterpages work well to give your site a consistent look and feel.

Thank you. Especially I need to change the menu on my master page. I used (IIRC) the ASP.NET-specific menu but I want to switch to a HTML5 type menu tags. The reason is that my site's menus do not work now on iPad.