The next stage—the technical stage—is all about development of the website.

The workflow for this section depends on the complexity of the project.

In some cases, you'll have to build a WordPress site

and in others you will need to build a custom solution in Ruby on Rails.

Like our earlier stages, let's break the stage down into simpler tasks, as well.

If the client requires any custom solutions, start by building out the necessary frameworks.

Get the basic stuff up and running before you move on to the coding of any specific pages.

Next, code up all the templates for the basic pages that you mocked up during the design stage.

In the previous stage, we coded up the design.

Here, we add in all the functionality.

After that, if the client desires any interactive features on the website, start adding it in. You're almost there.

One of the last steps, but equally as important once you've done coding of the website

is to load all the content in.

Now, this content should have been provided by the client or copywriter beforehand.

Again, this is clearly a dependency for the completion of the project

and should have been indicated on your proposal so that the client has sufficient time to get the information to you.

Once you're done with the creation of the website, it's time to test everything.

Go through every single page on the site, testing all functionality and proofing all design and copy.

Make sure everything works as it's meant to.

Your site map should help you navigate the site and make sure you cover every page that you created.

Now, that should cover the development stage for most projects.

You still have one final stage left before you're somewhat done with the project.

This stage has a collection of tasks that can be termed "pre-launch."

Again, depending on the project, tasks will vary,

but in general they comprise of the following duties:

Cleaning up—after the development phase,

give the client another review period.

Once you hear the feedback, take this time out to clean up even more.

Make final changes. If you have planned out your time properly, this cleaning up period makes a big difference to the client's satisfaction.

If you have a tight deadline, you should still make some time to get the client's feedback and to implement any last changes.

Then, you go live. This entire time you've been working in a development environment.

Now that the project is complete, it's time to put it on a live server.

This gives you and the client a chance to test it live and allows you to complete the next step, which is browser testing.

With lots of different browsers out there, you need to make sure

the website looks good and functions as intended across all browsers and platforms.

This may not mean identical functionality and aesthetics in every situation,

but make sure things aren't breaking.