A project website can be a good way to share updates, prototypes, files, etc with clients. They can also help share our work more widely within the client, and after the end of our project.
However, project websites are a considerable investment of time. Budget 4 hours per week for keeping it up to date.
Process & advice
- We generally use Squarespace, because anyone on a project team can use it. Other options are available.
- Buy a year’s subscription up front, and include the cost in the project expenses.
- Give the site a custom URL on Adaptive Lab’s domain (see below for instructions)
- Sketch out the site’s contents and structure as part of the project set-up. Think about the audience(s) for the site; what will they want to know?
Resist the urge to organise the website by project phase. This may be suitable during the project (maybe; our phases may not make sense to everyone at the client), but you’ll have to reorganise the site at the end of the project, when a chronology will be irrelevant. Visitors after this time will want the outputs first, and process info second, if at all..
- Make template pages during project set-up.
- Duplicate content as much as possible. If you’re making update decks, or reports on testing, or summaries of sprints, re-use that content on the website. Pull out key bits, and then upload the deck (on Slideshare) and embed it (on Squarespace).
- Budget 4 hours per week for keeping the site up to date.
Setting up project websites as subdomains of adaptivelab.com
So, you've made a snappy project site and you'd like it to have a URL like awesome-work.adaptivelab.com, instead of adaptive-lab-awesome.squarespace.com. You need to make it a subdomain of Adaptive Lab, like this: