Fix links

app/1.0/docs/about_10.md

@@ -72,7 +72,7 @@ that don’t support shadow DOM natively. The shadow DOM polyfill was optimized
 for correctness, though it remained impossible to perfectly polyfill shadow DOM.
 Shady DOM is optimized for speed.
 
-If you're curious about the motivation behind creating shady DOM, see [What is shady dom?](../articles/shadydom.html).
+If you're curious about the motivation behind creating shady DOM, see [What is shady dom?](https://www.polymer-project.org/blog/shadydom).
 
 In the immediate future we’ll be exploring improvements to the shady DOM system to improve interoperability with other frameworks.  Shadow DOM is of course the ultimate primitive to allow for interoperability, but with shady DOM we may be able to shim such interoperability to a significant degree, focusing on common interoperability use cases.
 

app/1.0/docs/apps/app-layout.md

@@ -447,7 +447,7 @@ shows a simple version of this transition.
 
 <a href="https://polymerelements.github.io/app-layout/patterns/transform-navigation/" class="blue-button">Launch Demo</a>
 
-<a href="https://github.com/polymerelements/app-layout/blob/master/patterns/transform-navigation/x-app.html" class="blue-button">View full source</a>
+<a href="https://github.com/PolymerElements/app-layout/blob/1.x/patterns/transform-navigation/x-app.html" class="blue-button">View full source</a>
 
 The [Shop app](https://shop.polymer-project.org/). uses a slightly more sophisticated version of this pattern, using conditional templates
 to avoid creating the navigation elements until they're needed. This means that the app doesn't need

app/1.0/docs/apps/case-study.md

@@ -64,7 +64,7 @@ the category "Shoes" to the browse view.
 
 More information:
 
--   [Encapsulated routing with elements](/1.0/blog/routing)
+-   [Encapsulated routing with elements](https://www.polymer-project.org/blog/routing)
 -   [`<app-route>` API reference](https://elements.polymer-project.org/elements/app-route)
 
 ## Views

app/1.0/docs/apps/news-case-study.md

@@ -46,10 +46,10 @@ subfolders.
 
 Views in the News app use the same implementation as the Shop app. [See the Shop app case study for
 more information on views and
-routing](https://www.polymer-project.org/1.0/toolbox/case-study#views).
+routing](/1.0/docs/apps/case-study#views).
 
 For more information on encapsulated routing, see [Encapsulated routing with
-elements](https://www.polymer-project.org/1.0/blog/routing).
+elements](https://www.polymer-project.org/blog/routing).
 
 For more information on the `<app-route>` Polymer element used in these implementations, see the
 [`<app-route>` API reference](https://www.webcomponents.org/element/PolymerElements/app-route).
@@ -80,7 +80,7 @@ to the URL that the user selects.
 
 Polymer's data system allows for data to flow one-way (downward-only, from host element to target
 element) or two-way (from host to target and target to host). For more information on data binding
-in Polymer, see [Data binding](../docs/devguide/data-binding).
+in Polymer, see [Data binding](/{{{polymer_version_dir}}}/docs/devguide/data-binding).
 
 The News app uses both one-way and two-way binding to transfer data between elements.
 

app/1.0/docs/apps/routing.md

@@ -14,7 +14,7 @@ application's routes, individual components manage some portion of the route, an
 to other components.
 
 **Why modular routing?** For background on `<app-route>` and modular routing, see
-[Encapsulated routing with elements](/1.0/articles/routing).
+[Encapsulated routing with elements](https://www.polymer-project.org/blog/routing).
 {.alert .alert-info}
 
 ## Install app-route
@@ -159,6 +159,6 @@ _viewChanged: function(view) {
 
 ## More resources
 
--   [Encapsulated routing with elements](/1.0/blog/routing)
+-   [Encapsulated routing with elements](https://www.polymer-project.org/blog/routing)
 -   [`<app-route>`
     API reference](https://elements.polymer-project.org/elements/app-route)

app/1.0/docs/browsers.md

@@ -92,7 +92,7 @@ Notes:
 #### Should I use webcomponents-lite.js or webcomponents.js?
 
 We recommend using the `webcomponents-lite.js` version of the polyfills with Polymer 1.0+. This
-version is designed to be used with [Shady DOM](https://www.polymer-project.org/1.0/blog/shadydom.html),
+version is designed to be used with [Shady DOM](https://www.polymer-project.org/blog/shadydom.html),
 and does not contain the full Shadow DOM polyfill.
 
 Although the full `webcomponents.js` polyfill works with Polymer 1.0+, we do not recommend using it.

app/1.0/docs/devguide/quick-tour.md

@@ -229,5 +229,5 @@ element; the element name is `iron-input`, and it _extends_ the native `<input>`
 
 Now that you understand these fundamental Polymer concepts:
 
--   Explore more with the [Build an element tutorial](first-element/intro).
--   Or [Install Polymer 3.x](install-3-0) to get started on a new project.
+-   Explore more with the [Build an element tutorial](/1.0/docs/first-element/intro).
+-   Or [Install the Polymer CLI](/1.0/docs/tools/polymer-cli) to get started on a new project.

app/1.0/docs/devguide/registering-elements.md

@@ -441,7 +441,7 @@ and `registered`.
 
 Use the `beforeRegister` callback to transform an element's prototype before
 registration. This is useful when registering an element using an ES6 class,
-as described in the article, [Building web components using ES6 classes](/1.0/blog/es6).
+as described in the article, [Building web components using ES6 classes](https://www.polymer-project.org/blog/es6).
 
 You can implement the `registered` callback to perform one-time initialization
 when an element is registered. This is primarily useful when implementing

app/1.0/docs/devguide/templates.md

@@ -290,7 +290,7 @@ different name for the index property.
 
 ### Forcing synchronous renders {#synchronous-renders}
 
-Call [`render`](/{{{polymer_version_dir}}}/docs/api/dom-repeat#method-render)
+Call [`render`](/{{{polymer_version_dir}}}/api/elements/dom-repeat#method-render)
 to force a `dom-repeat` template to synchronously render any changes to its
 data. Normally changes are batched and rendered asynchronously. Synchronous
 rendering has a performance cost, but can be useful in a few scenarios:
@@ -323,22 +323,22 @@ By default, `dom-repeat` tries to render all of the list items at once. If
 you try to use `dom-repeat` to render a very large list of items, the UI may
 freeze while it's rendering the list. If you encounter this problem, enable
 "chunked" rendering by setting
-[`initialCount`](/{{{polymer_version_dir}}}/docs/api/dom-repeat#property-initialCount).
+[`initialCount`](/{{{polymer_version_dir}}}/api/elements/dom-repeat#property-initialCount).
 In chunked mode,
 `dom-repeat` renders `initialCount` items at first, then renders the rest of
 the items incrementally one chunk per animation frame. This lets the UI thread
 handle user input between chunks. You can keep track of how many items have
 been rendered with the
-[`renderedItemCount`](/{{{polymer_version_dir}}}/docs/api/dom-repeat#property-renderedItemCount)
+[`renderedItemCount`](/{{{polymer_version_dir}}}/api/elements/dom-repeat#property-renderedItemCount)
 read-only property.
 
 `dom-repeat` adjusts the number of items rendered in each chunk to try and
 maintain a target framerate. You can further tune rendering by setting
-[`targetFramerate`](/{{{polymer_version_dir}}}/docs/api/dom-repeat#property-targetFramerate).
+[`targetFramerate`](/{{{polymer_version_dir}}}/api/elements/dom-repeat#property-targetFramerate).
 
 You can also set a debounce time that must pass before a `filter` or `sort`
 function is re-run by setting the
-[`delay`](/{{{polymer_version_dir}}}/docs/api/dom-repeat#property-delay)
+[`delay`](/{{{polymer_version_dir}}}/api/elements/dom-repeat#property-delay)
 property.
 
 ## Data bind an array selection (array-selector) {#array-selector}

app/1.0/docs/migration.md

@@ -10,9 +10,8 @@ element from 0.5 to 1.0.
 ## Polyup Tool
 
 We have been working on a tool called `polyup` to automatically
-perform many of the changes detailed in this guide. See an interactive demo
-[here](http://polymerlabs.github.io/polyup/), and check out the list of current
-and planned upgrades that it performs on its
+perform many of the changes detailed in this guide. Check out the list of current
+that it performs on its
 [README at github](https://github.com/PolymerLabs/polyup#html).
 
 ## Migration
@@ -935,7 +934,7 @@ For more details on the `vulcanize` arguments, see the [README](https://github.c
 ## Element & helper method changes {#methods}
 
 Some element methods and helper methods have been renamed, moved, or changed signatures.
-For a complete list of element methods, see the [API reference](http://polymer.github.io/polymer/).
+For a complete list of element methods, see the [API reference](https://polymer-library.polymer-project.org/1.0/api/classes/Polymer.Base).
 
 ### Element methods: job renamed to debounce
 

app/1.0/docs/tools/polymer-cli.md

@@ -146,7 +146,7 @@ which is the most basic starting point for a Polymer-based application,
 as well as others that introduce more complex layout and application patterns.
 
 This chapter teaches you more about `basic` app projects.  See
-[Polymer App Toolbox templates]({{{polymer_version_dir}}}/docs/apps/templates) for more details on
+[Polymer App Toolbox templates](/{{{polymer_version_dir}}}/docs/apps/templates) for more details on
 other templates.
 
 ### App project architecture {#app-architecture}
@@ -155,7 +155,7 @@ Polymer CLI is designed for apps that follow the [app shell
 architecture](https://developers.google.com/web/updates/2015/11/app-shell).
 
 There are fundamental concepts of the app shell architecture that you should understand before creating your app project with Polymer CLI: the entrypoint,
-the shell, and fragments. See [App structure](/1.0/toolbox/server#app-structure)
+the shell, and fragments. See [App structure](/1.0/docs/apps/server#app-structure)
 from the App Toolbox docs for an in-depth overview of these concepts.
 
 ### Set up basic app project {#basic-app}

app/1.0/nav.yaml

@@ -142,9 +142,6 @@
   - title: Global settings
     path: /1.0/docs/devguide/settings
     indent: True
-  - title: Community
-    path: /community/
-    indent: True
   - title: Browser compatibility
     path: /1.0/docs/browsers
     indent: True

app/2.0/docs/apps/app-layout.md

@@ -453,7 +453,7 @@ shows a simple version of this transition.
 
 <a href="https://polymerelements.github.io/app-layout/patterns/transform-navigation/" class="blue-button">Launch Demo</a>
 
-<a href="https://github.com/polymerelements/app-layout/blob/master/patterns/transform-navigation/x-app.html" class="blue-button">View full source</a>
+<a href="https://github.com/PolymerElements/app-layout/blob/2.x/patterns/transform-navigation/x-app.html" class="blue-button">View full source</a>
 
 The [Shop app](https://shop.polymer-project.org/). uses a slightly more sophisticated version of this pattern, using conditional templates
 to avoid creating the navigation elements until they're needed. This means that the app doesn't need

app/2.0/docs/apps/case-study.md

@@ -63,7 +63,7 @@ the category "Shoes" to the browse view.
 
 More information:
 
--   [Encapsulated routing with elements](/blog/routing)
+-   [Encapsulated routing with elements](https://www.polymer-project.org/blog/routing)
 -   [`<app-route>` API reference](https://www.webcomponents.org/element/PolymerElements/app-route)
 
 ## Views
@@ -125,7 +125,7 @@ _pageChanged(page, oldPage) {
 In the logic above, the home view is built into the app shell, but the other
 views are demand-loaded fragments.
 
-Shop also uses [`dom-if`](/{{{polymer_version_dir}}}/docs/api/elements/Polymer.DomIf) templates to lazily create views:
+Shop also uses [`dom-if`](/{{{polymer_version_dir}}}/api/elements/Polymer.DomIf) templates to lazily create views:
 
 ```html
 <!-- Lazy-create the tabs for larger screen sizes. -->

app/2.0/docs/apps/news-case-study.md

@@ -49,7 +49,7 @@ more information on views and
 routing](case-study#views).
 
 For more information on encapsulated routing, see [Encapsulated routing with
-elements](/blog/routing).
+elements](https://www.polymer-project.org/blog/routing).
 
 For more information on the `<app-route>` Polymer element used in these implementations, see the
 [`<app-route>` API reference](https://www.webcomponents.org/element/PolymerElements/app-route).
@@ -80,7 +80,7 @@ to the URL that the user selects.
 
 Polymer's data system allows for data to flow one-way (downward-only, from host element to target
 element) or two-way (from host to target and target to host). For more information on data binding
-in Polymer, see [Data binding](../docs/devguide/data-binding).
+in Polymer, see [Data binding](/{{{polymer_version_dir}}}/docs/devguide/data-binding).
 
 The News app uses both one-way and two-way binding to transfer data between elements.
 

app/2.0/docs/apps/prpl.md

@@ -102,7 +102,7 @@ The shell (including its static dependencies) should contain everything needed f
 
 By default, the Polymer CLI build process produces an unbundled build designed for server/browser combinations that support HTTP/2 and HTTP/2 server push to deliver the resources the browser needs for a fast first paint while optimizing caching.
 
-To generate a bundled build, designed to minimize the number of round-trips required to get the application running on server/browser combinations that don't support server push, you will need to pass a command line option or configure your [polymer.json file](polymer-json) appropriately.
+To generate a bundled build, designed to minimize the number of round-trips required to get the application running on server/browser combinations that don't support server push, you will need to pass a command line option or configure your [polymer.json file](/{{{polymer_version_dir}}}/docs/tools/polymer-json) appropriately.
 
 If you have multiple builds, your server logic must deliver the appropriate build for each browser.
 

app/2.0/docs/apps/routing.md

@@ -11,7 +11,7 @@ application's routes, individual components manage some portion of the route, an
 to other components.
 
 **Why modular routing?** For background on `<app-route>` and modular routing, see
-[Encapsulated routing with elements](/blog/routing).
+[Encapsulated routing with elements](https://www.polymer-project.org/blog/routing).
 {.alert .alert-info}
 
 ## Install app-route
@@ -161,6 +161,6 @@ _viewChanged(view) {
 
 ## More resources
 
--   [Encapsulated routing with elements](/blog/routing)
+-   [Encapsulated routing with elements](https://www.polymer-project.org/blog/routing)
 -   [`<app-route>`
     API reference](https://www.webcomponents.org/element/PolymerElements/app-route)

app/2.0/docs/apps/templates.md

@@ -36,7 +36,7 @@ and composes them in a common left-hand drawer arrangement with a toolbar.
 The template provides navigation between a series of views that load and
 are rendered in the main content area.
 
-The template is also set up to use the [PRPL pattern](server) for efficient
+The template is also set up to use the [PRPL pattern](prpl) for efficient
 and progressive loading of the application, where views are loaded on-demand
 and will be pre-cached for offline and subsequent use.
 

app/2.0/docs/devguide/custom-css-properties.md

@@ -311,7 +311,7 @@ Note that the font family is inherited, but the text color is not. This is becau
 Polymer's custom property shim evaluates and applies custom property values once
 at element creation time.  In order to have an element (and its subtree) re-
 evaluate custom property values due to dynamic changes such as application of
-CSS classes, call the [`updateStyles`](/2.0/docs/api/elements/Polymer.Element#method-updateStyles)
+CSS classes, call the [`updateStyles`](/2.0/api/elements/Polymer.Element#method-updateStyles)
 method on the element. To update _all_ elements on the page, you can also call
 `Polymer.updateStyles`.
 
@@ -370,7 +370,7 @@ if (ShadyCSS) {
 ```
 
 Elements using the legacy API can use the
-[`getComputedStyleValue`](/2.0/docs/api/mixins/Polymer.LegacyElementMixin#method-getComputedStyleValue)
+[`getComputedStyleValue`](/2.0/api/mixins/Polymer.LegacyElementMixin#method-getComputedStyleValue)
 instance method instead of testing for `ShadyCSS`.
 
 
@@ -393,7 +393,7 @@ dynamism will continue to be explored.
 Only property definitions which match the element at *creation time* are applied.
 Any dynamic changes that update property values are not applied automatically. You
 can force styles to be re-evaluated by calling the
-[`updateStyles`](/{{{polymer_version_dir}}}/docs/api/elements/Polymer.Element#method-updateStyles) method on a
+[`updateStyles`](/{{{polymer_version_dir}}}/api/elements/Polymer.Element#method-updateStyles) method on a
 Polymer element, or `Polymer.updateStyles` to update all element
 styles.
 

app/2.0/docs/devguide/custom-elements.md

@@ -172,7 +172,7 @@ Related topics:
 
 ### Defer non-critical work
 
-When possible, defer work until after first paint. [`Polymer.RenderStatus`](/{{{polymer_version_dir}}}/docs/api/namespaces/Polymer.RenderStatus) provides a utility for this purpose. `Polymer.RenderStatus` is included by default for hybrid elements. For class-style elements using the `polymer-element.html` import, you need to import `Polymer.RenderStatus` separately.
+When possible, defer work until after first paint. [`Polymer.RenderStatus`](/{{{polymer_version_dir}}}/api/namespaces/Polymer.RenderStatus) provides a utility for this purpose. `Polymer.RenderStatus` is included by default for hybrid elements. For class-style elements using the `polymer-element.html` import, you need to import `Polymer.RenderStatus` separately.
 
 ```js
 <link rel="import" href="/bower_components/polymer/polymer-element.html">
@@ -385,7 +385,7 @@ in Document your elements.
 When creating a mixin that you intend to share with other groups or publish, a couple of additional
 steps are recommended:
 
--   Use the [`Polymer.dedupingMixin`](/{{{polymer_version_dir}}}/docs/api/#function-Polymer.dedupingMixin)
+-   Use the [`Polymer.dedupingMixin`](/{{{polymer_version_dir}}}/api/#function-Polymer.dedupingMixin)
     function to produce a mixin that can only be applied once.
 
 -   Create a unique namespace for your mixins, to avoid colliding with other mixins or classes that

app/2.0/docs/devguide/data-system.md

@@ -165,8 +165,8 @@ this.push('users', { name: 'Maturin'});
 
 In some cases, you can't use the Polymer methods to mutate objects and arrays (for example, if
 you're using a third-party library). In this case, you can use  the
-[`notifyPath`](/{{{polymer_version_dir}}}/docs/api/elements/Polymer.Element#method-notifyPath) and
-[`notifySplices`](/{{{polymer_version_dir}}}/docs/api/elements/Polymer.Element#method-notifySplices)
+[`notifyPath`](/{{{polymer_version_dir}}}/api/elements/Polymer.Element#method-notifyPath) and
+[`notifySplices`](/{{{polymer_version_dir}}}/api/elements/Polymer.Element#method-notifySplices)
 methods to *notify* the element about changes that have **already taken place.**
 
 
@@ -362,7 +362,7 @@ maintains path linkages between an array and a selected item from that array. (`
 also works when selecting multiple items from an array.)
 
 For other use cases, there's an imperative method,
-[`linkPaths`](/{{{polymer_version_dir}}}/docs/api/elements/Polymer.Element#method-linkPaths) to
+[`linkPaths`](/{{{polymer_version_dir}}}/api/elements/Polymer.Element#method-linkPaths) to
 associate two paths. When two paths are *linked*, an [observable change](#observable-changes) to one
 path is observable on the other path, as well.
 
@@ -929,7 +929,7 @@ the following is true:
 *   You always use the Polymer data mutation methods to make granular changes.
 
 However, for apps that don't use immutable data and can't use the Polymer data methods, Polymer 2.0
-provides the [`Polymer.MutableData`](/{{{polymer_version_dir}}}/docs/api/mixins/Polymer.MutableData)
+provides the [`Polymer.MutableData`](/{{{polymer_version_dir}}}/api/mixins/Polymer.MutableData)
 mixin.
 
 ```js
@@ -1008,7 +1008,7 @@ If you're using the `dom-repeat` element, you can enable mutable data mode by se
 ### Optional mutable data for reusable elements {#optional-mutable-data}
 
 If you're building a reusable element that takes structured data, you can use the
-[`Polymer.OptionalMutableData`](/{{{polymer_version_dir}}}/docs/api/mixins/Polymer.OptionalMutableData)
+[`Polymer.OptionalMutableData`](/{{{polymer_version_dir}}}/api/mixins/Polymer.OptionalMutableData)
 mixin. This mixin lets the element user select `MutableData` mode by setting the `mutableData`
 property on the element.