HTML
  Home arrow HTML arrow Page 2 - Web Design - First Things First
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Sun Developer Network 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
HTML

Web Design - First Things First
By: Richard Lowe
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 4 stars4 stars4 stars4 stars4 stars / 2
    2002-09-23

    Table of Contents:
  • Web Design - First Things First
  • Think, then Act
  • Conclusion

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Web Design - First Things First - Think, then Act


    (Page 2 of 3 )

    For many years I was a programmer and I found the same exact sentiment in that field. Just start coding was the watchword. In fact, I had more than one boss in my long career who actually stopped design and analysis so that we could start coding the programs. One very memorable boss, by the name of Gary, forced me to skip any kind of specification for a project on which we were working because he believed (mistakenly as it turned out) that the customer needed to see finished programs as soon as possible.

    A fact that must be understood is it is imperative that a project be well thought out in advance or there is an excellent chance that it will fail. I have been managing software projects for over 22 years, and one common thread among hundreds of projects is quite simply those that had good design and analysis done up front succeeded, and those that didn't failed (or required superhuman effort to get finished).

    This fact works with websites as well as software projects. The more time you put in up front thinking about what you want to accomplish the better the project will turn out. Of course, this can be taken to a ridiculous extreme and a project can never even be started because the analysis never gets done, but it works in general.

    The first thing to do before you code any HTML, build any databases, create any graphics or write any content is find out or figure out what purpose you are trying to achieve. I usually start with a single paragraph which states exactly what I am trying to accomplish. For example, for an intranet which I built a couple of years ago the purpose was stated thusly:

    A compendium of all of the technical documentation needed by my staff to support our warehouse systems, applications, operating systems, server hardware and operating system software. The site is to include many flowcharts which demonstrate how data flows from system to system. This data is intended to be used in day-to-day operations and should be specifically tailored to fit each of my staff's individual jobs.

    You see - simple. Yet what flows from this paragraph are many implications. The target audience is my own staff, which defines how the articles will be written. The content is defined as is the intention.

    For my Internet Tips And Secrets website, the purpose was defined as follows:

    Our web site will contain original articles intended to help people learn about the internet. The articles will stress ethics on the internet. All aspects of the internet are to be covered, including newsgroups, email, graphics, web site design, ftp and so forth.

    My wife's Surviving Asthma site had the following definition:

    This site will contain information about how I am combating my asthma condition, and how I have survived with this disease. My intention is to help other people gain hope and assurance that the disease can be successfully combated.

    You see how each of these paragraphs defines the intention behind the web site. What overall purpose is trying to be achieved? Who is the intended audience? What kind of content (very generally) will be required? Is the purpose commercial, informational or something else?

    It is important to keep this paragraph short and to the point. You are just trying to get down in simple terms the reason why you are doing this project. You are not performing the analysis and design as of yet - you are defining what you are trying to analyze.

    More HTML Articles
    More By Richard Lowe


     

    HTML ARTICLES

    - Using a 3D HTML Table as a Recordset
    - Building a 3D HTML Table
    - Maximizing and Restoring HTML Images: Layer ...
    - Completing Construction of a Database Form w...
    - Maximizing and Restoring Images in a Tabular...
    - Building the Recordset for an HTML Database ...
    - Laying Out a Database Form with HTML
    - Tabular Database Form Functions with HTML
    - Tabular Database Forms with HTML
    - Using the Find Functions for HTML Database F...
    - Sorting for Database Forms with HTML
    - Edit and Other Database Form Functions with ...
    - More Database Form Functions with HTML
    - Database Form Functions with HTML
    - Using the HTML Table Element as a Recordset






    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 6 hosted by Hostway
    Stay green...Green IT