From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BEB961383E0 for ; Thu, 1 Oct 2015 11:22:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6659121C025; Thu, 1 Oct 2015 11:22:32 +0000 (UTC) Received: from homiemail-a43.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) by pigeon.gentoo.org (Postfix) with ESMTP id 553E721C002 for ; Thu, 1 Oct 2015 11:22:31 +0000 (UTC) Received: from homiemail-a43.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a43.g.dreamhost.com (Postfix) with ESMTP id 7D4E68C05F for ; Thu, 1 Oct 2015 04:22:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=libertytrek.org; h=subject :to:references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=libertytrek.org; bh=T d20RzqmQP4xQo1Lw9VOPMZTUhM=; b=0DUymMWO+LlnQRIYngVeZLK5nnf/Z6lNM o9rEhxsDO7R0cxVv2D+hVwg2s8zdHVVpas9+QCyrnwy1rkngjTtpXUibP1llJsOF JsMRbhjTOrT1VTsWCg9LnqVH/BYyKs5hD7yBc6uz9vEF2vTO2lqhEM07EkHhqW+I 2yLx+mhWOs= Received: from [192.168.1.110] (unknown [159.63.145.4]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: tanstaafl@libertytrek.org) by homiemail-a43.g.dreamhost.com (Postfix) with ESMTPSA id 5DF968C057 for ; Thu, 1 Oct 2015 04:22:29 -0700 (PDT) Subject: Re: [gentoo-user] Re: Major site redesign, SEO, and 301 redirects To: gentoo-user@lists.gentoo.org References: <560AEDFA.9000706@libertytrek.org> <560AF6ED.4010404@gmail.com> From: Tanstaafl Message-ID: <560D1774.2070800@libertytrek.org> Date: Thu, 1 Oct 2015 07:22:28 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Archives-Salt: dc2c2ac3-1c73-4de6-8e97-79ea69af645d X-Archives-Hash: 5b9fc04c883704988c97fb85a61cc89e On 9/29/2015 8:02 PM, James wrote: > Another point of concern. When radically changing infrastructure like this, > why not just do the entire thing under a new DNS and have both online for a > while, until the new site if vetted and the actual real bugs worked out? Well... not sure how that would work, since we are not changing domain names, only redesigning the site. What I would do if I was a web dev is just set up a test site, then set up the development site for the customer under a subdirectory, ie: https://mycustomtestingsite.com/customer-a/index.html > Also, your company should force this contractor to take a large liability > policy, in the name of your company, should things go really fubar.... Interesting idea. Not sure how well it would go over. Is that a common thing in the industry for large corporate redesigns like this? Thanks James