Hi All,

We have been contracted to upgrade a custom magnolia site to a new
version with new functionality.  We haven't used Magnolia before and
I'm having a few problems imagining how this will work.

First the current site is running on Magnolia 2.1 and we plan to
upgrade to Magnolia 3.0 EE.  Is there any documentation on gotchas and
changes that will be needed when doing this?  I can't give specific
details of the customizations yet because the source is still being
delivered.  Is there any extant documentation on this?

Second,  What is generally the process of rolling out Magnolia sites?
It seems that the rollout contains both templates and functionality
artifacts as well as content structure and configuration.  How do you
move from a testing environment which will have both deliverable
content (possibly modified during testing) and testing content to the
production environment?  Any extent documents, horror stories, tips,
etc. etc. would be gratefully read and digested.

Thank you for you time and help,
Matthew Denson

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to