I was on a call this morning with a potential client. My firm would very much enjoy working on the project but we need to sort out a few things first.
The current site is built in 1.7 MSM. They would like the new site to be built within the current MSM instance. I understand the benefits of building this new microsite within the current MSM (shared content, authors, etc etc) but I am not excited (nor do I want to add extra expense to the client) to build a 1.7 site or make any of our internal modules/plugins backward compatible for this one project.
I am selling the client on the benefits of upgrading to 2.X, wether we do it, or they do it internally. I would hate to build the site in 1.7x then have to come back in and upgrade less than 12 months down the road.
We could set up the new site in 2.X MSM, and configure the main site in the MSM as the current main site, and just leave it empty for now, and then set up the new site as an additional site. Then the install will be ready for when they do want to upgrade. We could run it on a separate subdomain for now, and use RSS to pull in any shared content for the time being.
Anyone have any experience in similar situations?
thanks
-A