RE: when to implement a CMS

> 
> If you're just talking about a look-and-feel change, you can
> do it at any time. If you're going to do anything more
> substantial (i.e. coming up with new site templates, navigation,
> etc) then you'd save some effort by waiting until the CMS is
> implemented, otherwise you may find yourself doing it all again.
> 

Yeah, we tried the old "install a new CMS and do a sitewide redesign at the
same time" trick and it was awful (OK, in part because we had layoffs right
in the middle of it all). We wound up launching the redesign first, then
implemented the CMS. I think this approach worked better for us because by
the time we were done with the redesign we knew exactly what we needed to
get the CMS to do. Had we done the reverse, we might have had to make
compromises on the design because of "oh, the CMS can't do that"
considerations - instead, we just hunkered down and figured out how to make
the CMS do what we wanted.

Adam Gaffin
Executive Editor, Network World Fusion
[email protected] / (508) 490-6433 / http://www.nwfusion.com 
"I programmed my robotic dog to bite the guy who delivers the electronic
mail." -- Kibo 
--
http://cms-list.org/
more signal, less noise.