Five Keys to Successful Web Development
- on 10.31.08
- Random Musings
- No Comments
- Digg
- Del.icio.us
Today was the last day of my contract with Target, and before I left, I was asked to jot down some guidelines for the developers to help them in the future when designing their applications. Below are the pearls of wisdom I came up with. Not new or revolutionary by any means, but it has been my experience that they are all too often over looked.
First, let me just say there are no hard and fast rules to development. Every project is unique and has it’s own challenges, and you need to be flexible in finding solutions. The guidelines listed below are just that, guidelines; they are not meant to be followed absolutely or blindly. Size plays a big role in these guidelines; the bigger the project, the more important these guidelines become.
- Never develop a site to work with just one browser. I don’t care what you’ve been told, but at some point, someone is going to need this site to work on a browser other than the one you developed it for.
- Future-proof your site. You don’t know how your site will be used or expanded in the future. Building it with the future in mind will minimize rework.
- Building your site to be cross browser compatible goes a long way in future-proofing your site.
- Develop and use a naming convention. A naming convention is an essential tool in organizing your site’s files and CSS and allows others to more easily understand the structure of your site.
- Use CSS to control the layout and design of your application.
- Use external style sheets to easily make global site changes. Do not use in-line styles or HTML attributes (i.e. <td width= "100">).
- Use tables for what they were intended, to display data. Do not use tables to layout your site.
- Use prototypes. Build HTML and CSS prototypes to test UI and browser compatibility before starting construction.
- “Know your users—for they are not you.” As developers we often become too close and familiar with the project we are working on. It is important to make sure that you get feedback from you audience as you develop the prototypes.
- Not all browsers display HTML and CSS the same way. Prototyping gives you the opportunity to discover browser specific issues and fix them before construction begins.
- Once the prototypes have been tested and approved, use them as the foundation of your development. This speeds up construction and helps eliminate chances of error.
- Know the limits of your technology. If a particular .Net or ASP control is incapable of rendering code in the format you need it to be in, make sure your prototype reflects this. Nothing is more frustrating than spending weeks building and tweaking a prototype only to find out that the technology you have chosen for development is incapable of recreating your prototype.












