Front-end template staging

Not neccesarily in strict order

Finalisation of anticipated content/functionality for front page & secondary pages

Expected content that will go on the front page and secondary pages. Functionality such as search boxes and forms.

HTML skeleton

Expected sample html which will be generated by the CMS, including ordering of sections. This is what we will expect browsers to gracefully degenerate towards if they cannot support particular features. Essential for accessibility.

Wire frames

Layouts for what content will go where

Colour schemes/palettes

Unified colour schemes for the site, and sections. Some sections may benefit from a slightly different scheme to signal which section the user is in (eg. red, burgundy & grey for Find a church, green, burgundy & grey for courses and training)

CSS type-style sets

Type face choices for heading levels, body text, menu text. Leading and paragraph spacing.

Mockups (photoshop etc)

Mockups of the styling, including colour schemes, graphics, sample content, typography

Slices, graphics and CSS

Spinning the mockups into standards compliant, semantically correct html/css

Trials and tweaking

Attach template to CMS. Make adjustments as neccesary.