Is It Ok To Create The Html First For An Asp.net Or Asp.net Mvc Site?

Does it work OK to code the HTML first for an ASP.Net or ASP.Net MVC site, and then hand this off to the coders? If not, what would be the best approach to integrating these?

Solution 1:

This is absolutely acceptable. That is one of the great things about MVC.

Create your HTML and CSS and let the developers code in the dynamic bits and worry about all that side of it.

Solution 2:

I don't think there's anything necessarily wrong with that approach. I know places that have web designers mock-up html to give their developers "starting points" to creating their pages.

Solution 3:

It works quite well. Some of the HTML may be replaced with ASP controls.

Personally I'd rather start from a HTML page that's reasonably well mocked-up rather than a JPEG in a Word Doc.

Solution 4:

For ASP.NET MVC yes this is certainly possible. In fact, that's one of the benefits of MVC. You can switch your front end at a whim without a big, breaking change. Web designers can work independently of back end developers.

With WebForms (Traditional ASP.NET) this is possible, but not so easy. With things like the code behind page being the main issue. Web designers shouldn't care about this, but ASP.NET has the code behind tied to the page.

Solution 5:

If you are talking about doing a mockup then it really depends on what you expect them to do with it in terms of dynamic content that will be added. The html may not be useful to them at all, but it would probably be better than a mockup in anything else, since the html will limit you to doing things that are easily implemented in asp.net. where as a mockup in word or photoshop would allow you to do things that might not be easily implemented in asp.net. So I would say html mockup is a good idea.

If there is no programming to be done, i.e. it is just a static hmtl page, then I'd just link to it as an html page.