I do something similar. I have:
1. a live site of site in dev
2. a test site of site in dev
3. a local ’playground’ for all site testing
Whenever I have to create a new site for a client (as opposed to refactoring an existing one) the first thing I (try to) do is to make a "paper copy" together with the client. This forces them to concentrate on and think about the content. Afterall that’s what we want people to see/read right? (Well mostly anyway)
In the past we would discuss the brief, figure out the site structure and technical needs and trust the client to provide the content. Then start doing all the graphic design and technical stuff. That done and after adding some content we’d get back to the client and get them to check the site. 9 out of 10 times the comments coming back would be about the heading color or the classic "this page looks empty! can you splice it up with an image or two?"
Nowadays I prefer to setup MODx with an empty template, just basic navigation and the content area, Get the client to do as much of the entering of content as practicle so by the time we get to introducing snippets, TV’s and the like they already know the basics of working with MODx. Once all the content is ready and approved we set up the gadgets and eye candy.
In the mean time we will have presented and discussed the site design, but mostly as static examples and while the client is entering content we will have finalized the templates, the css and the graphics.
Working with MODx makes this process smooth as butter... Once all the content is in we simply plonk in the templates and configure the last TV’s and snippets.
Toby,
Great workflow. I believe I will be adopting this as well. As this also solves the problem with clients not realizing that the programming backend needs to come before the design. This way they can see the backend/programming improvements before the design is completed and implemented.
Thanks,
Chuck
MODX Staff
