Services: Web Site Implementations

A web site implementation can take many forms, but in the end what's important is a high-quality, production-ready site which embodies the design you and your client have envisioned. What's most important to us is working closely with you to produce that high quality site. Since all projects and web designers are different we don't use one set process for everyone, we tailor our process to you and how you work most comfortably.

The general pattern that most implementations follow is this:

Planning

  • We start by jointly defining the implementation 'team'. This is usually made up of the web designer, client technical staff, any content producers and the Glennweb.net developer.
  • Next we look at your site design and vision. Here we will outline your design goals and general 'feel' for the site. We will also try to plan for any implementation issues we might foresee at this point.
  • Then we will begin to define the scope of the work to be done. This is where we discuss the 'knowns' about the project and the 'unknowns' we are likely to run into. We will document the size and depth of the complete site and the specific features to be delivered and their complexity.
  • We will then make an inventory of the available site assets, including content, and who is responsible for producing them.
  • Another area which we must carefully define is the site technical requirements. Starting with the technical parameters of the production hosting service we will work backwards to define what operating systems, servers, databases, languages, and tools we can use in developing the site.
  • After this we need to define the goals for site feature testing and site validation. This will include defining a supported browser set and what web standards the completed site should validate against.
  • Finally we will agree on a the timeline for completion of the individual milestones and the complete implementation.

Iterative Development

During the actual development period we have found that one of the most useful ways we can stay flexible to your needs and work style is to develop in short iterations with many milestones. We will normally begin the implementation by creating a complete navigable 'site skeleton' which will always be available on a staging server. As work progresses the various milestones will be deployed on this skeleton until we arrive at a complete site. By doing this the site progress and nuances are always visible to the whole development team.

We will also use an email or online method of project communication during this period as well. This could be done through normal email, an email list-serv, or possibly through a project web blog where information and ideas are regularly published. All projects will have specific development issues tracked through an online issue/bug tracking system.

Testing

Throughout the development period we will do as much site testing as is practical. We will create indivdual automated unit tests for scripted site features in addition to normal browser and validation testing.

Acceptance

There is normally some sort of acceptance testing for the site, sometimes involving first the web designer and then the actual site client. This might constitute the last iteration or two of development.

Production

Finally the site will be made ready for production. This could just be packaging up of the site for publication or it might involve Glennweb.net publishing the site to the client's host/servers.

? Work from your toolset (photoshop, etc.)

? Most web projects follow a certain pattern (design comps, art, colors, content, site layout).

We will look at your site design and vision,
the size and depth of the complete site,
the specific features to be delivered and their complexity,
the available site assets and content,
the site technical requirements,
the site testing and validation goals,
and the timeline for completion.

Then we will coordinate a plan for the various site designs, asset and content hand-offs, and development deliverables/milestones.

As development proceeds the implementation team will remain in contact through its method of choice (email, email list, blog, etc).
At each milestone you will receive an interim deliverable, usually a document or partial site, review-able on our staging server.
The final deliverable will be a thoroughly tested, production ready, maintainable web site implementation that meets or exceeds your quality metrics.