ampproject · cramforce · Feb 24, 2017 · Feb 23, 2017 · Feb 23, 2017 · Feb 23, 2017
diff --git a/README.md b/README.md
@@ -1,158 +1,48 @@
-<!---
-Copyright 2015 The AMP HTML Authors. All Rights Reserved.
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-      http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS-IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-
 [![Build Status](https://travis-ci.org/ampproject/amphtml.svg?branch=master)](https://travis-ci.org/ampproject/amphtml)
 
 # AMP HTML ⚡
 
-[AMP HTML](https://www.ampproject.org/docs/get_started/about-amp.html) is a way to build web pages for static content that render with reliable, fast performance. It is our attempt at fixing what many perceive as painfully slow page load times – especially when reading content on the mobile web.
-
-AMP HTML is entirely built on existing web technologies. It achieves reliable performance by restricting some parts of HTML, CSS and JavaScript. These restrictions are enforced with a validator that ships with AMP HTML. To make up for those limitations AMP HTML defines a set of [custom elements](http://www.html5rocks.com/en/tutorials/webcomponents/customelements/) for rich content beyond basic HTML. Learn more about [how AMP speeds up performance](https://www.ampproject.org/docs/get_started/technical_overview.html).
-
-# How does AMP HTML work?
-
-AMP HTML works by including the AMP JS library and adding a bit of boilerplate to a web page, so that it meets the AMP HTML Specification. The simplest AMP HTML file looks like this:
-
-```html
-<!doctype html>
-<html ⚡>
-  <head>
-    <meta charset="utf-8">
-    <link rel="canonical" href="hello-world.html" >
-    <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1">
-    <style amp-boilerplate>body{-webkit-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-moz-animation:-amp-start 8s steps(1,end) 0s 1 normal both;-ms-animation:-amp-start 8s steps(1,end) 0s 1 normal both;animation:-amp-start 8s steps(1,end) 0s 1 normal both}@-webkit-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-moz-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-ms-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@-o-keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}@keyframes -amp-start{from{visibility:hidden}to{visibility:visible}}</style><noscript><style amp-boilerplate>body{-webkit-animation:none;-moz-animation:none;-ms-animation:none;animation:none}</style></noscript>
-    <script async src="https://cdn.ampproject.org/v0.js"></script>
-  </head>
-  <body>Hello World!</body>
-</html>
-```
-
-This allows the AMP library to include:
-* The AMP JS library, that manages the loading of external resources to ensure a
-  fast rendering of the page.
-* An AMP validator that provides a way for web developers to easily validate
-  that their code meets the AMP HTML specification.
-* Some custom elements, called AMP HTML components, which make common patterns
-  easy to implement in a performant way.
-
-Get started [creating your first AMP page](https://www.ampproject.org/docs/get_started/create_page.html).
-
-[Full docs and reference.](https://www.ampproject.org/docs/get_started/about-amp.html)
-
-## The AMP JS library
-
-The AMP JS library provides [builtin](builtins/README.md) AMP Components, manages the loading of external resources, and ensures a reliably fast time-to-paint.
-
-## The AMP Validator
-
-[The AMP Validator](validator/README.md) allows a web developer to easily
-identify if the web page doesn't meet the
-[AMP HTML specification](https://www.ampproject.org/docs/reference/spec.html).
+[AMP HTML](https://www.ampproject.org/docs/get_started/about-amp.html) is a way to build web pages that render with reliable and fast performance. It is our attempt at fixing what many perceive as painfully slow page load times – especially when reading content on the mobile web.  AMP HTML is built on existing web technologies; an AMP page will load (quickly) in any modern browser.
 
-Adding "#development=1" to the URL of the page instructs the AMP Runtime to run
-a series of assertions confirming the page's markup meets the AMP HTML
-Specification.  Validation errors are logged to the browser's console when the
-page is rendered, allowing web developers to easily see how complex changes in
-web code might impact performance and user experience.
+You can learn more at [ampproject.org](https://www.ampproject.org/) including [what AMP is](https://www.ampproject.org/learn/about-amp/), [how it works](https://www.ampproject.org/learn/how-amp-works/) and the importance of [validation in AMP](https://www.ampproject.org/docs/guides/validate).  You can also walk through [creating an AMP page](https://www.ampproject.org/docs/get_started/create) and read through the [reference docs](https://www.ampproject.org/docs/reference/components).
 
-It also allows apps that integrate web content to validate the web page against
-the specification.  This allows an app to make sure the page is fast and
-mobile-friendly, as pages adhering to the AMP HTML specification are reliably
-fast.
+## Help make AMP better!
+**There are a lot of ways you can [contribute](CONTRIBUTING.md) to making AMP better!**  You can [report bugs and feature requests](CONTRIBUTING.md#filing-issues) or ideally become an [ongoing participant](CONTRIBUTING.md#ongoing-participatiion) in the AMP Project community and [contribute some code](CONTRIBUTING.md#contributing-code).
 
-Learn more about
-[validating your AMP pages](https://www.ampproject.org/docs/guides/validate.html).
-Also see [additional choices to invoke the validator](validator/README.md).
+We **_⚡⚡⚡ enthusiastically ⚡⚡⚡_ welcome new contributors** to the AMP Project **_even if you have no experience being part of an open source project_**.  We've got some [tips for new contributors](https://github.com/ampproject/amphtml/blob/master/CONTRIBUTING.md#tips-for-new-open-source-contributors) and guides to getting started (both a [detailed version](contributing/getting-started-e2e.md) and a [TL;DR](contributing/getting-started-quick.md)).
 
-## AMP HTML Components
+If you're new here, sign up for our [Slack](https://docs.google.com/forms/d/e/1FAIpQLSd83J2IZA6cdR6jPwABGsJE8YL4pkypAbKMGgUZZriU7Qu6Tg/viewform?fbzx=4406980310789882877) and say "Hi!" in the appropriately named [#welcome-contributors](https://amphtml.slack.com/messages/welcome-contributors/) channel.
 
-AMP HTML Components are a series of extended custom elements that supplement
-or replace functionality of core HTML5 elements to allow the runtime to ensure
-it is solely responsible for loading external assets and to provide for shared
-best practices in implementation.
-
-See our [docs and reference](https://www.ampproject.org/docs/get_started/about-amp.html) for more info.
-
-# Releases
-
-We push a new release of AMP to all AMP pages every week on Thursday. The more detailed schedule is as follows:
-
-- Every Wednesday we cut a green release from our `master` branch.
-- On Thursday this is pushed to users of AMP who opted into the [AMP Dev Channel](#amp-dev-channel).
-- On Monday we check error rates for opt-in users and bug reports and if everything looks fine, we push this new release to 1% of AMP pages.
-- We then continue to monitor error rates and bug reports throughout the week.
-- On Thursday the "Dev Channel" release from last Thursday is then pushed to all users.
-
-You can always follow the current release state of AMP on our [releases page](https://github.com/ampproject/amphtml/releases). The release used by most users is marked as `Latest release` and the current Dev Channel release is marked as `Pre-release`.
-
-## AMP Dev Channel
-
-AMP Dev Channel is a way to opt a browser into using a newer version of the AMP JS libraries.
-
-This release **may be less stable** and it may contain features not available to all users. Opt into this option if you'd like to help test new versions of AMP, report bugs or build documents that require a new feature that is not yet available to everyone.
-
-Opting into Dev Channel is great to:
-
-- test and play with new features not yet available to all users.
-- use in Q&A to ensure that your site is compatible with the next version of AMP.
-
-If you find an issue that appears to only occur in the Dev Channel version of AMP, please [file an issue](https://github.com/ampproject/amphtml/issues/new) with a description of the problem. Please always include a URL to a page that reproduces the issue.
-
-To opt your browser into the AMP Dev Channel, go to [the AMP experiments page](https://cdn.ampproject.org/experiments.html) and activate the "AMP Dev Channel" experiment. Please subscribe to our [low-volume announcements](https://groups.google.com/forum/#!forum/amphtml-announce) mailing list to get notified about important/breaking changes about AMP.
-
-# Further Reading
+## Further reading
 
 If you are creating AMP pages,
 check out the docs on [ampproject.org](https://www.ampproject.org/) and samples on [ampbyexample.com](https://ampbyexample.com/).
 
-These docs are public and open-source: [https://github.com/ampproject/docs/](https://github.com/ampproject/docs/).
-See something that's missing from the docs, or that could be worded better?
-[Create an issue](https://github.com/ampproject/docs/issues) and
-we will do our best to respond quickly.
 
 Resources:
 * [AMP HTML samples](examples/)
 * [AMP-HTML on StackOverflow](https://stackoverflow.com/questions/tagged/amp-html)
+* [Release schedule](contributing/release-schedule.md)
 
-<!--
-Not yet done.
-* [Integrating your AMP HTML page](docs/integrating.md)
-* [Extending AMP HTML with new elements](docs/extending.md)
-* [Embedding AMP HTML content in your app](docs/embedding.md)
--->
 
 Reference:
 * [AMP HTML core built-in elements](builtins/README.md)
-* [AMP HTML optional extended elements](extensions/README.md)
+* [AMP HTML extensions](extensions/README.md)
 
 Technical Specifications:
 * [AMP HTML format specification](spec/amp-html-format.md)
 * [AMP HTML custom element specification](spec/amp-html-components.md)
 
-# Who makes AMP HTML?
-
-AMP HTML is made by the [AMP Project](https://www.ampproject.org/), and is licensed
-under the [Apache License, Version 2.0](LICENSE).
+## Who makes AMP HTML?
 
-## Contributing
+AMP HTML is made by the [AMP Project](https://www.ampproject.org/).  If you're a contributor to the open source community this includes you!
 
-We strongly encourage contributions from the community, whether it's reporting bugs, suggesting features or diving in and implementing changes to the AMP Project.  Please see [the CONTRIBUTING file](CONTRIBUTING.md) for information on contributing to the AMP Project.
+AMP HTML is licensed under the [Apache License, Version 2.0](LICENSE).
 
-### Security disclosures
+## Security disclosures
 
 The AMP Project accepts responsible security disclosures through the [Google Application Security program](https://www.google.com/about/appsecurity/).
 
-### [Code of conduct](CODE_OF_CONDUCT.md)
+## Code of conduct
+
+The AMP Project strives for a positive and growing project community that provides a safe environment for everyone.  All members, committers and volunteers in the community are required to act according to the [code of conduct](CODE_OF_CONDUCT.md).
diff --git a/contributing/getting-started-e2e.md b/contributing/getting-started-e2e.md
@@ -437,7 +437,7 @@ You can set your browser to use the Dev Channel build by enabling `dev-channel`
 
 You can verify the AMP version your browser is using for a given page by looking at your browser's developer console.  After loading an AMP page (e.g. [https://ampproject.org](https://ampproject.org)) the console will have a message like `Powered by AMP ⚡ HTML – Version <build number>`).  The `<build number>` will match one of the build numbers on the [amphtml Releases page](https://github.com/ampproject/amphtml/releases).
 
-The [Releases section of README.md](../README.md#releases) has more details on the release process.
+The [Release Schedule](release-schedule.md) doc has more details on the release process.
 
 # ⚡⚡⚡...
 

diff --git a/contributing/great-first-issues-template.md b/contributing/great-first-issues-template.md
@@ -52,7 +52,7 @@ Ideally suggest a reviewer for the Pull Request; not knowing who to set as the r
 <!--
 If this issue is a change that won't go out with a push (e.g. a doc change, a fix to the build, etc.) update the sentence about how to see their change is live.
 -->
-Once approved, your changes will be merged.  **⚡⚡⚡Congrats on making your first contribution to the AMP Project!⚡⚡⚡**  You'll be able to see it [live across the web soon](https://github.com/ampproject/amphtml/blob/master/README.md#releases)!
+Once approved, your changes will be merged.  **⚡⚡⚡Congrats on making your first contribution to the AMP Project!⚡⚡⚡**  You'll be able to see it [live across the web soon](https://github.com/ampproject/amphtml/blob/master/contributing/release-schedule.md)!
 
 Thanks, and we hope to see more contributions from you soon.
 

diff --git a/contributing/release-schedule.md b/contributing/release-schedule.md
@@ -0,0 +1,26 @@
+# Release Schedule
+
+We push a new release of AMP to all AMP pages every week on Thursday. The more detailed schedule is as follows:
+
+- Every Wednesday we cut a green release at the latest commit that passed all tests.
+- On Thursday this is pushed to users of AMP who opted into the [AMP Dev Channel](#amp-dev-channel).
+- On Monday we check error rates for opt-in users and bug reports and if everything looks fine, we push this new release to 1% of AMP pages.
+- We then continue to monitor error rates and bug reports throughout the week.
+- On Thursday the "Dev Channel" release from last Thursday is then pushed to all users.
+
+You can always follow the current release state of AMP on our [releases page](https://github.com/ampproject/amphtml/releases). The release used by most users is marked as `Latest release` and the current Dev Channel release is marked as `Pre-release`.
+
+### AMP Dev Channel
+
+AMP Dev Channel is a way to opt a browser into using a newer version of the AMP JS libraries.
+
+This release **may be less stable** and it may contain features not available to all users. Opt into this option if you'd like to help test new versions of AMP, report bugs or build documents that require a new feature that is not yet available to everyone.
+
+Opting into Dev Channel is great to:
+
+- test and play with new features not yet available to all users.
+- use in Q&A to ensure that your site is compatible with the next version of AMP.
+
+If you find an issue that appears to only occur in the Dev Channel version of AMP, please [file an issue](https://github.com/ampproject/amphtml/issues/new) with a description of the problem. Please always include a URL to a page that reproduces the issue.
+
+To opt your browser into the AMP Dev Channel, go to [the AMP experiments page](https://cdn.ampproject.org/experiments.html) and activate the "AMP Dev Channel" experiment. Please subscribe to our [low-volume announcements](https://groups.google.com/forum/#!forum/amphtml-announce) mailing list to get notified about important/breaking changes about AMP.