<p>Most sites are either fully released, or in beta.</p>

<p>But what happens if you have a large site, and some of the parts are still in Beta, and other parts aren't. </p>

<p>How do you effectively communicate this to the customer?</p>

[{'answer_id': 51525, 'author': 'Giovanni Galbo', 'author_id': 4050, 'author_profile': 'https://Stackoverflow.com/users/4050', 'pm_score': 0, 'selected': False, 'text': "<p>If there's a certain way you enter the part of the beta site, maybe you can have a modal that pops up that they have to agree to every time.  I wouldn't have it on every page since it gets annoying, so I would only use this approach if there is a definitive way to get into that part of the site (e.g. people won't be coming to random parts of the beta section through Google or something).</p>\n"}, {'answer_id': 51529, 'author': 'Nick Fortescue', 'author_id': 5346, 'author_profile': 'https://Stackoverflow.com/users/5346', 'pm_score': 0, 'selected': False, 'text': '<p>One way I\'ve used for non-web software is a change to background. So for example if your normal site tended to have a plain white background, you could have the beta site have a repeating beta text in a background image. You want to make it fairly faint so it is present  but doesn\'t detract from the overall experience.</p>\n\n<p>Another subtle but present option would just be to change the title bar.</p>\n\n<p>Or you could do what google does, which is a large site with some of it in beta. Check out <a href="http://www.google.com/experimental/" rel="nofollow noreferrer">Google experimental search</a>. Basically the site is no different, but it is hard to get to accidentally.</p>\n'}, {'answer_id': 51534, 'author': 'seanyboy', 'author_id': 1726, 'author_profile': 'https://Stackoverflow.com/users/1726', 'pm_score': 0, 'selected': False, 'text': '<p>There are a few ways. </p>\n\n<ol>\n<li><p>Provide access to the site via two domains (e.g. <em>www.domain.com</em> and <em>beta.domain.com</em>) and only allow access to beta parts of the site when going in via <em>beta.domain.com</em>. </p>\n\n<p>People will be accessing the same code base, but will only get access to the beta sections if they\'ve specified the beta subdomain. Trying to access beta sections of the site will explain this &amp; tell them how to access the beta. </p></li>\n<li><p>Strongly Flag the beta sections of the application as being beta, and force the user to acknowledge that they\'re OK using beta features with some kind of agreement screen. The first time they try to use the beta feature, they\'ll be shown the agreement screen. Subsequent uses of the feature will prominently deisplay that "thios part of the site is in beta and is used at your own peril."</p></li>\n</ol>\n'}, {'answer_id': 51536, 'author': 'svrist', 'author_id': 86, 'author_profile': 'https://Stackoverflow.com/users/86', 'pm_score': 1, 'selected': False, 'text': '<p>Maybe take a look at how Facebook, Bloglines, Gmail did it?</p>\n\n<p>Like "We have this beta thing going on, come on over and see the same site with new stuff, but if it doesnt work, use the old parts"</p>\n\n<p>Maybe gmail labs where you can sign up for "beta features"</p>\n'}]
['https://Stackoverflow.com/questions/51519', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/5350/']