Single-purpose extensions policy FAQ

R=asargent@chromium.org

Review URL: https://codereview.chromium.org/267303006

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@269109 0039d316-1c4b-4281-b951-d872f2087c98

3 files changed, 246 insertions, 0 deletions

diff --git a/chrome/common/extensions/docs/templates/articles/single_purpose.html b/chrome/common/extensions/docs/templates/articles/single_purpose.html
new file mode 100644
index 0000000..bd59826
--- /dev/null
+++ b/chrome/common/extensions/docs/templates/articles/single_purpose.html
@@ -0,0 +1,240 @@
+<h1>Extensions Quality Guidelines FAQ</h1>
+
+<h2 id="one">1.) Why did Google launch a “single purpose” Chrome extensions policy?</h2>
+
+<p>For an overview of the policy announcement, please read this
+<a href="http://blog.chromium.org/2013/12/keeping-chrome-extensions-simple.html">Chromium blog post</a>.</p>
+
+<p>We launched this policy because
+multi-purpose extensions can crowd your browser UI
+and slow down your web browsing - sometimes significantly.
+Speed and simplicity have always been part of Chrome's core principles,
+so this policy will help us get back to the design that was originally intended.
+Also, unexpected changes to browser functionality and
+settings have become the number one user complaint for Chrome users,
+and this policy helps minimize the problem by ensuring
+that users understand what extensions are doing.
+</p>
+
+<h2 id="two">2.) Where can I find the “single purpose” policy?</h2>
+
+<p>
+Please refer to the
+<a href="https://developer.chrome.com/webstore/program_policies?csw=1#extensions">Extensions Quality Guidelines</a>
+section of the Chrome Web Store Developer Program Policies.
+</p>
+
+<h2 id="three">3.) What does “single purpose” actually mean?</h2>
+
+<p>
+“Single purpose” can refer to one of two aspects of an extension: 
+</p>
+
+<p>
+An extension can have a single purpose limited to a narrow
+<strong>focus area or subject matter</strong>
+(for example, news headlines", "weather", "comparison shopping").
+If the extension has a narrow focus area or subject matter,
+then it can offer various functions related
+to that focus area or subject matter.
+For example, a news headlines extension could have a browser action button
+that allows users to see news stories and replace the new tab page
+with news-only content,
+so long as all of those functions are narrowly focused
+on the news headline focus area. 
+</p>
+
+<p>
+Or, an extension can have a single purpose limited
+to a narrow <strong>browser function</strong>
+(for example, "new tab page", "tab management", or "browser history").
+If the extension is implemented in a single function,
+then it can offer content or features related to different areas or subjects.
+For example, an extension that replaces the new tab page could offer
+multiple unrelated features on the new tab page
+(for example, weather forecast, news headlines, search engine, and so on),
+but it can’t also provide a browser action button,
+change the browser’s homepage, or
+make any other changes to browser functionality.
+</p>
+
+<h2 id="four">4.) Will this policy affect my extension?</h2>
+
+<p>
+It depends.
+Particularly if your extension offers multiple features,
+please make sure that it has a single purpose.
+Ask yourself these questions:
+</p>
+
+<ul>
+  <li>Does my extension have a narrow focus area
+  or a narrow function as described above?</li>
+  <li>If my extension has a narrow focus area,
+  are all of the features directly related to that single purpose?</li>
+  <li>If my extension has multiple features,
+  does it only affect a narrow function of the browser?</li>
+  <li>Does my extension modify Chrome’s behavior in a predictable way,
+  in line with the extension's narrow, stated purpose?</li>
+</ul>
+
+<p>
+If you’re unsure, you can email
+<a href="mailto:chromewebstore-policy@google.com">chromewebstore-policy@</a>
+with your extension ID,
+and we’ll take a look and try to provide feedback within a week.
+If your extension does not have a single purpose,
+then you will need to remove functionality
+or split your extension into different extensions. 
+</p>
+
+<h2 id="five">5.) What will happen
+if I don’t make my extension compliant with this policy?</h2>
+
+<p>
+If you created your extension after December 2013,
+your extension will not be permitted in the Chrome Web Store.
+If you created your extension prior to December 2013,
+your item may be removed from the Chrome Web Store starting July 15, 2014.
+You will still be able to update the extension and file appeals.
+Please keep in mind that
+your re-published item will not be immediately published live in the store.
+The re-published item will undergo a compliance review
+before it can be restored.
+</p>
+
+<p>
+In order to minimize disruption for users,
+we recommend that you take a moment to carefully review your extensions
+and make necessary updates as soon as possible.
+You can email us at
+<a href="mailto:chromewebstore-policy@google.com">chromewebstore-policy@</a>
+with your extension ID, and we’ll try to provide feedback within a week.
+</p>
+
+<h2 id="six">6.) Can my extension make changes to the start page,
+homepage, or new tab settings?</h2>
+
+<p>
+Yes.
+If the purpose of your extension is to modify one narrow function of the browser
+(either the start page, homepage or new tab page, for example),
+and it does only that,
+then it would be compliant with the single purpose policy.
+Additionally,
+if the purpose of your extension is limited to one focus area or subject matter,
+then you can have various functions related to that one area or subject matter,
+including changes to start page, homepage or new tab page.
+</p>
+
+<p>
+Please note that your extension will only be able to make changes
+to Chrome settings pursuant to Chrome policies, as applicable.
+Please see this
+<a href="http://blog.chromium.org/2014/03/protecting-user-settings-on-windows.html">Chromium blog post</a>
+for more information.
+</p>
+
+<h2 id="seven">7.) Can my extension make changes to the default search settings?</h2>
+
+<p>
+Yes.
+If the only purpose of the extension is to change the default search settings,
+then it would be compliant with the single purpose policy.
+Additionally,
+if the single purpose of your extension is search as the narrow focus area,
+and nothing else, then you can offer various functions related to search,
+including changes to default search settings.
+</p>
+
+<h2 id="eight">8.) Can I bundle ad injection with some other type of functionality?</h2>
+
+<p>
+No.
+This violates the single purpose policy.
+However, if injecting ads is the single purpose of the extension and
+the extension is otherwise compliant with Chrome policies,
+then it would be acceptable.
+For example, a “related articles” extension that adds sponsored links
+to articles related to a page the user is visiting would be compliant
+with the single purpose policy because it has a single purpose limited
+to a narrow function of the browser.
+You also might want to explore the other monetization options described
+<a href="https://developer.chrome.com/webstore/money">here</a>.
+</p>
+
+<h2 id="nine">9.) Are toolbars permitted under this policy?</h2>
+
+<p>
+It depends on what the toolbar does.
+As described in
+<a href="#three">answer #3</a>,
+it must adhere to the narrow single purpose of the extension.
+Broad, multi-purpose toolbars are not allowed and
+toolbars that are implemented using content scripts
+to inject UI into every page are not recommended because
+they slow down every page load, clutter the UI,
+and can lead to security problems for users.
+Instead, consider using a
+<a href="https://developer.chrome.com/extensions/browserAction">browser action popup</a>,
+which was designed to solve this very problem.
+It's a better user experience, with no performance or security downsides.
+</p>
+
+<h2 id="ten">10.) What will happen to non-compliant extensions
+that were already installed by users?</h2>
+
+<p>
+All extensions will need to comply with the Extension Quality Guidelines.
+If a user installed a non-compliant extension,
+then you will need to update them to a compliant extension
+that is hosted in the Chrome Web Store.
+If the user is not updated to a compliant extension
+that is hosted in the Chrome Web Store,
+then the extension will be automatically disabled.
+You can find more information
+<a href="http://blog.chromium.org/2014/02/make-sure-to-get-your-extension-in.html">here</a>.
+</p>
+
+<h2 id="eleven">11.) If my extension is rejected from the Chrome Web Store
+because it doesn’t comply with the single purpose policy,
+what will happen after the requirement to host extensions
+in the Chrome Web Store comes into effect?</h2>
+
+<p>
+If your extension is rejected from the Chrome Web Store,
+you will need to make changes or appeal the decision.
+After the requirement to host extensions
+in the Chrome Web Store comes into effect,
+your extension must be hosted in the Chrome Web Store or
+it will be automatically disabled from the users’ browsers. 
+</p>
+
+<h2 id="twelve">12.) If my extension gets flagged for review under the single purpose policy,
+what will happen?</h2>
+
+<p>
+Our team will review it,
+and it may be removed from the Chrome Web Store.
+You’ll have a chance to make changes and appeal the decision.
+As noted above,
+if you created your extension before we announced the policy in December 2013,
+you have until July 15, 2014 to make changes.
+If your extension was created after the policy was announced,
+it needs to be compliant now.
+You can temporarily unpublish it and contact us at
+<a href="mailto:chromewebstore-policy@google.com">chromewebstore-policy@</a>
+with your extension ID if you’d like feedback.
+We’ll try to respond within a week.
+</p>
+
+<h2 id="thirteen">13.) I need help. Who should I contact?</h2>
+
+<p>
+You can email
+<a href="mailto:chromewebstore-policy@google.com">chromewebstore-policy@</a>
+with your extension ID,
+and we’ll take a look and try to provide feedback within a week.
+This is a lightweight review intended to give you an indication
+of whether your extension will comply with the new policy.
+</p>
diff --git a/chrome/common/extensions/docs/templates/json/chrome_sidenav.json b/chrome/common/extensions/docs/templates/json/chrome_sidenav.json
index d53b351b..c7722af 100644
--- a/chrome/common/extensions/docs/templates/json/chrome_sidenav.json
+++ b/chrome/common/extensions/docs/templates/json/chrome_sidenav.json
@@ -521,6 +521,11 @@
                 "href": "/extensions/hosting_changes"
               },
               {
+                "title": "Extension Quality Guidelines FAQ",
+                "href": "/extensions/single_purpose"
+              },
+
+              {
                 "title": "Event Pages",
                 "href": "/extensions/event_pages"
               },
diff --git a/chrome/common/extensions/docs/templates/public/extensions/single_purpose.html b/chrome/common/extensions/docs/templates/public/extensions/single_purpose.html
new file mode 100644
index 0000000..e251308
--- /dev/null
+++ b/chrome/common/extensions/docs/templates/public/extensions/single_purpose.html
@@ -0,0 +1 @@
+{{+partials.standard_extensions_article article:articles.single_purpose removeToc:true/}}