One of the most important aspects which ASP.NET brought to application development is the ability for development to be separated from design. This separation allowed for programmers to prepare applications and designers to skin them accordingly or if preferred, the other way round.
For example if you go in http://www.dotnetmushroom.com you will see a DotNetMushroom RAD module which displays our last 3 blog entries. Luke, who is a developer in our offices, developed this Blog application using DotNetMushroom RAD by designing tables, any necessary queries, forms and controls in these forms.
The developer would most probably leave the design that DotNetMushroom RAD generated and finalize the application. The application developer will then test the site and give the application to the designer.
This is the body template which DotNetMushroom RAD created and which Luke used to test the application.
Finally when Luke was happy with the result of the application (the logic), he gave the application to Justin, our head designer (who, by the way, was behind the polish design of RAD itself).
Just like he usually does to a DotNetNuke skin, Justin updated the templates using his preferred Divs, styles and css classes (in simple terms: his magic).
The designer will skin the application’s templates either by editing the HTML templates directly or by using the DotNetMushroom RAD interface itself inside each form.
And viola! Luke’s blog application resulted in this nice and clean look by Justin.
Obviously testing of the whole application would then commence, this final test to check not only the functionality of the application but also the look and feel in the various browsers: a headache which all developers and designers do know pretty well!