Geeks With Blogs

News Google

Nick Harrison Blog<Nick>.Next()

Here are some guidelines that I have started following to structure pages and get the style sheets right.

I have found it useful to have one style sheet for the web site that sets the color schemes, fonts, and page structure as well as any other UI constraints that would be common across all pages in the site.   I then add a new style sheet for each page to handle positioning information specific to that page.   This seems to keep the style sheets more manageable while still keeping the content separate from the format and positioning.

When designing a page, I have started following the following process:

  1. Mark up the page with HTML using simple input tags to get the flow and style sheets right.
  2. Convert the HTML to an aspx or ascx as appropriate.
  3. Convert the input tags to server controls using the same style classes as the original HTML
  4. Wire up the data binding
  5. Wire up the navigational controls
  6. Replace built in controls with third party controls as appropriate.

This first step could potentially be done by a designer allowing developers to skip this step all together.   

Having the original HTML to refer back to as a reference also comes in handy.   At every point, we can refer back to it to ensure that you are still true to the original design.  

Is anyone following a similar approach?   Does anyone see any concerns with such an approach?

Posted on Sunday, November 20, 2005 7:01 PM Stylish musings | Back to top


Comments on this post: Iterative Process for Web Page Design

comments powered by Disqus

Copyright © Nick Harrison | Powered by: GeeksWithBlogs.net