This is an overview of the sequence of events in building an InForm site.
Once the client has agreed that they would like to work with fiennes.org then we get the ball rolling which involves:
The build process is pretty flexible in format depending on how clear the model for the design and the information architecture is at the start of the process.
We are looking to form a pretty early model as to:
This will help us to propose a visual structure and navigational hierarchy that best fits the information that is going to be put into it.
There will probably be several iterations of the design process, but we prefer to work "in the browser" as much as possible so that all design ideas are presented as functional prototypes with as much of the client's proposed structure included so that the designs can be interacted with as early as possible. We may configure the test build to generate random pages to emulate how the site might behave in 6-12m time based on the expected usage patterns.
Once everyone is happy with the visual state and behavior of the site then we formally sign off the development process.
What this means is:
The client uses the CMS to populate their site until it is fit for launch in their eyes.
It is not impossible that further changes will be required to visual aspects during this process because the way that people interact with a site changes when they start to put larger amounts of content into them.
Once the site content has been signed off by the client, then we make the appropriate DNS changes and shortly after that the site becomes available to the world at large to interact with.
We raise a final invoice for any further work requested during the Final Population after Design Signoff.
The site serves pages and is updated by the client and the public interact with it. 6 months after the Project Start (and every 12 months after that), then we raise the first annual hosting invoice.