jump to content

Satheesh Babu

This document aims at providing a starting point on the guidelines and processes involved in developing web pages. .


  1. Basic knowledge of HTML.
  2. Remember, a site is NOT for you to see, but for others to see.
  3. Always have a GOAL for the site.
  4. HTML is NOT intended to do everything for you. Know its limitations.
  5. HTML is NOT suitable for typesetting. For that use PDF or LaTeX.

Quoted from top ten mistakes in web design...

  1. Using Frames
  2. Gratuitous Use of Bleeding-Edge Technology
  3. Scrolling Text, Marquees, and Constantly Running Animations
  4. Complex URLs
  5. Orphan Pages
  6. Long Scrolling Pages
  7. Lack of Navigation Support
  8. Non-Standard Link Colors
  9. Outdated Information
  10. Overly Long Download Times

Quoting the top ten mistakes of web management...

  1. Not Knowing Why
  2. Designing for Your Own VPs
  3. Letting the Site Structure Mirror Your Orgchart
  4. Outsourcing to Multiple Agencies
  5. Forgetting to Budget for Maintenance
  6. Treating the Web as a Secondary Medium
  7. Wasting Linking Opportunities
  8. Treating Internet and Intranet Sites the Same
  9. Confusing Market Research and Usability Engineering
  10. Underestimating the Strategic Impact of the Web


If this is a new site
   If has idea of the content, ready and approved
        Create a new folder structure
           Create the folder
           Create subfolders for supporting components
           If site has subsections which can have more than 2 html pages:
              Consider that as a sub site and follow the whole process for that
        Make a default document
        Add other pages as necessary
        Stop, make sure you come back with content!
    If you have good idea on how the site is organized, and you have the modified content
        If you have come to add pages
           Create the pages with the site's template in mind
           Distribute the supporting content into appropriate subfolders
        Else If you want to modify pages
           Make sure no one else is modifying it at the same time
           Modify the content
           See if you broke any links or anything else that was working before your work
        Stop, get a grip on the site and come back
Test the site
Copy the files over to the staging area
Clean up all your backup files from the staging area
Get it approved - self or peer or supervisor
Upload the file to the production server and do a final test.


Naming folders

Naming files

Folder Structure

Just remember that you don’t need to put all your HTML files in a single folder. Arrange these using folders based on subject and use, just like your normal documents. If you think some content needs only one HTML file now and will probably grow to 10 files in a year, start by making a folder for that first. It is a lot more difficult to arrange things into folders when you have a good amount of content.

Supporting components

Supporting components can be arranged into subfolders named like below.

Default document

Adding pages


  1. W3C
  2. Yale Style Guide
  3. Philip and Alex's Guide to Web Publishing
  4. Web usability