[support] Tips & Tricks while taking over a website

[Hummel, Tracey S - (thummel)]

I would expect a good development company to provide documentation, comment a lot within any custom code and provide a live or remote training session on how everything was built.  When I do hire out site development, those expections are very clear in the contract. When I build a complex site, I create a separate site just for the docs so it is easy to hand over a manageable finished product.

I've dealt with  some companies that don't provide any documentation at all and then they ask for a separate contract for all tech support.

Tracey


Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: Afan Pasalic
Date:04/24/2014 6:56 PM (GMT-07:00)
To: support at drupal.org
Subject: [support] Tips & Tricks while taking over a website

I got a D7 website to take care of. Since the website is still "in charge" of the old/current/outside web development company, I don’t want to do anything on the production website to avoid any possible conflict with the web development company.
I installed copy of the website on my localhost and trying to figure it out what they were doing. The website is rather complex with tons of content types, webforms and custom modules.
Anybody already had exact or similar experience with taking over a website? Any tips and trick would be appreciated.

Thanks for any help.
--
[ Drupal support list | http://lists.drupal.org/ ]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20140425/3dd8ede8/attachment.html