Methodology explained - Part III Develop
2006.07.30 22:10
In a brief introduction to our approach to a project we have been going over some of the larger concepts in working towards a finished site. The third stage in our process is development. Once the finished concept is signed and approved by the client, we then move to actually build the site. During the development process, we move from designing the experience to creating the site.
The design, and its subsequent pieces, is dissected to create any graphic imagery that may be needed per the design. These images are any item that can not be readily or consistently created by pure code (i.e. photographic elements vs. styled text headings). Once the assets are exported we are ready to divide the space and build the site.
The first step in this stage is to block out the big picture and then begin filling in. Following the flowchart, we begin to create templates that reflect the differing qualities of the pages on the site; home-page, top-level page, editorial, gallery, contact form, etc. These templates will be used to populate the site. Once that is done, we fill in the flowchart to further insure the user-experience is at the optimum level.
Now that the basic flow is established we will begin to flow in the actual content of the site. All of the editorial content and image assets to build a rough version of the site; alpha code. After this is functional we begin the review process. With the client, we review the site to make sure it meets the expectations of the client and the potential visitors to the site. Portions of the code will be non-functioning (i.e. forms, shopping carts, etc.). Minor layout changes can be made at this stage, as well as editorial rewrites and image selection are common practice at this point. A major retooling of the site would require stepping back in the development process and re-adjusting the tasks and timelines.
Once the alpha site has met with approval, we refine the code and optimize any element that we can to deliver a site that meets the project's requirements. Beta code development insures semantic valid code as well as insuring the graphics are optimized and the editorial content is search engine friendly. These steps are all taken together, working the site development as an artist works a canvas…blocking the canvas and working back the detail into each section at the same time to create a clear image.
After the beta code has reached review, we again have the client review every page of the site. The site at this point is technically done and this is the quality assurance step before we move to final testing. Most items changed at this stage are usually misspellings, correcting email addresses and changing the occasional picture. Any other change at this point would freeze development and halt the launch of the site.
Once approved the site moves to testing phase. We brute-force try to break the site. Just another level of QA before launching the site. The client will always give the final approval before launching and once given the site will go live. Our contracts differ per project, but many times we are called to maintain a site for a pre-determined time after launch. Providing consistency in stewardship of the online brand of our clients.
