Merge pull request #91 from Polymer/twitter-rename

update twitter handle from polymer -> polymerLibrary

app/authors.yaml

@@ -74,7 +74,7 @@ polymer-team:
   gplus: +PolymerProject
   profile_pic: /images/logos/p-author-logo.png
   web: https://www.polymer-project.org/
-  twitter: polymer
+  twitter: polymerLibrary
   github: polymer
 
 taylor:

app/blog/2015-05-29-one-dot-oh.md

@@ -2,7 +2,7 @@
 title:  "1.0"
 
 ---
-_We announce significant releases here on the blog, highlighting the major new features as well as breaking changes. As always, we'd love to get your feedback, issues, and PR's, so tweet us [@polymer](https://twitter.com/polymer) or contribute to the [Github](https://github.com/Polymer)._
+_We announce significant releases here on the blog, highlighting the major new features as well as breaking changes. As always, we'd love to get your feedback, issues, and PR's, so tweet us [@polymerLibrary](https://twitter.com/polymerLibrary) or contribute to the [Github](https://github.com/Polymer)._
 
 Today we’re incredibly excited to announce the 1.0 release of the Polymer library.
 

app/blog/2015-08-13-1.1-release.md

@@ -2,7 +2,7 @@
 title:  "1.1 Release"
 
 ---
-_We announce significant releases here on the blog, highlighting the major new features as well as breaking changes. As always, we'd love to get your feedback, issues, and PR's, so tweet us [@polymer](https://twitter.com/polymer) or contribute to the [Github](https://github.com/Polymer)._
+_We announce significant releases here on the blog, highlighting the major new features as well as breaking changes. As always, we'd love to get your feedback, issues, and PR's, so tweet us [@polymerLibrary](https://twitter.com/polymerLibrary) or contribute to the [Github](https://github.com/Polymer)._
 
 It's been a while since our last post - we've been heads-down on follow-up from the 1.0 release! A big thank you to everyone for the excellent and extremely helpful Github issues and pull requests. Lots of bug fixes and perf improvements have been going in, as well as a number of updated 1.0 components (more on these soon). But today we're especially pleased to announce:
 

app/blog/2015-11-02-release-1.2.0.md

@@ -2,7 +2,7 @@
 title:  "Introducing Polymer 1.2.0"
 ---
 
-_We announce significant releases here on the blog, highlighting the major new features as well as breaking changes. As always, we'd love to get your feedback, issues, and PR's, so tweet us [@polymer](https://twitter.com/polymer) or contribute to the [Github](https://github.com/Polymer)._
+_We announce significant releases here on the blog, highlighting the major new features as well as breaking changes. As always, we'd love to get your feedback, issues, and PR's, so tweet us [@polymerLibrary](https://twitter.com/polymerLibrary) or contribute to the [Github](https://github.com/Polymer)._
 
 
 The [1.2.0 release](https://github.com/polymer/polymer/releases/tag/v1.2.0) includes two significant new features:
@@ -197,4 +197,4 @@ To detect those changes, `<simple-carousel>` would have to check its child list
 The `observeNodes` method handles this complexity for you. It uses mutation observers internally to track DOM changes, and handles the extra bookkeeping required to track local DOM distributions. Unlike a mutation observer, the `observeNodes` callback is only invoked when nodes are added or removed &mdash; it doesn't handle attribute changes or character data changes.
 
 
-As always, we'd love to get your feedback on this release, so please tweet [@Polymer](https://twitter.com/polymer) or check out the [Polymer library on Github](https://github.com/polymer).
+As always, we'd love to get your feedback on this release, so please tweet [@polymerLibrary](https://twitter.com/polymerLibrary) or check out the [Polymer library on Github](https://github.com/polymer).

app/blog/2016-09-09-polymer-2.0.md

@@ -90,7 +90,7 @@ We've done some refactoring of Polymer and the webcomponentsjs polyfills to impr
 
 ### Feedback requested!
 
-For more detailed documentation on the `2.0` branch as it evolves, see the [README](https://github.com/Polymer/polymer/blob/2.0-preview/README.md) included in the repository. We’d love your feedback on this early development release - please leave issues directly on the repository, or shoot us a tweet [@Polymer](https://www.twitter.com/polymer).
+For more detailed documentation on the `2.0` branch as it evolves, see the [README](https://github.com/Polymer/polymer/blob/2.0-preview/README.md) included in the repository. We’d love your feedback on this early development release - please leave issues directly on the repository, or shoot us a tweet [@polymerLibrary](https://www.twitter.com/polymerLibrary).
 
 Over the next couple months, we’ll be continuing to iterate on the API. We’ll also be upgrading the [elements built by the Polymer team](https://elements.polymer-project.org) to be built on top of 2.0.
 

app/blog/2016-10-03-1.7-release.md

@@ -2,19 +2,19 @@
 title:  "1.7 Release"
 
 ---
-_We announce significant releases here on the blog, highlighting the major new features as well as breaking changes. As always, we'd love to get your feedback, issues, and PR's, so tweet us [@polymer](https://twitter.com/polymer) or contribute to the [Github](https://github.com/Polymer)._
+_We announce significant releases here on the blog, highlighting the major new features as well as breaking changes. As always, we'd love to get your feedback, issues, and PR's, so tweet us [@polymerLibrary](https://twitter.com/polymerLibrary) or contribute to the [Github](https://github.com/Polymer)._
 
 The primary goal of the upcoming Polymer 2.0 release is to take advantage of native, cross-browser support for Web Components. With this in mind, we're pleased to release Polymer 1.7, which introduces features allowing you to use 2.0-compatible syntax in 1.x elements.
 
 ## Polymer 1.7
 
-Polymer 1.7.0 provides forward compatibility features that let you build elements that run under both 1.0 and 2.0. 
+Polymer 1.7.0 provides forward compatibility features that let you build elements that run under both 1.0 and 2.0.
 
 While you can use these features now, the team intends to release a tool to help automate these changes. If you have a large project, you might want to wait for the migration tool to be available.
 
 The new syntax is not required for current Polymer 1.x elements, but using the new syntax will make it easier to port elements to 2.0, which requires it.
 
-### `<slot>` element 
+### `<slot>` element
 
 Elements can opt-in to using the new `<slot>` element and `::slotted()` CSS selector from shadow DOM v1.
 

app/blog/2017-05-17-summit-2017.md

@@ -21,4 +21,4 @@ To be notified when registration opens, sign up with your email address at [g.co
 
 If you can't make it to Copenhagen, don't worry. The talks will be livestreamed and recorded for later, and the codelabs will be available online so you can try them out from anywhere.
 
-Follow us on Twitter [@polymer](https://twitter.com/polymer) for regular updates.
+Follow us on Twitter [@polymerLibrary](https://twitter.com/polymerLibrary) for regular updates.

app/blog/2017-05-26-polymer-at-io-17.md

@@ -43,7 +43,7 @@ Learn to build a web component with plain JavaScript, and how to publish it on W
 
 #### Cheese
 
-While we build the App Toolbox to help developers build web component based progressive web apps more efficiently and simply, we also build reference apps and case studies. Our most recent Apps project came out of a challenge to our team: to build an awesome mobile experience that we would only expect from native, in a tiny fraction of the size. Out of that came Cheese, a photo editing app powered by Google’s Vision APIs which detects your facial features and expression, and smartly decorates your photo with silly emoji combinations. Try it out at <a href="https://cheese.polymer-project.org">cheese.polymer-project.org</a> and share your best photos with [@polymer](https://twitter.com/polymer).
+While we build the App Toolbox to help developers build web component based progressive web apps more efficiently and simply, we also build reference apps and case studies. Our most recent Apps project came out of a challenge to our team: to build an awesome mobile experience that we would only expect from native, in a tiny fraction of the size. Out of that came Cheese, a photo editing app powered by Google’s Vision APIs which detects your facial features and expression, and smartly decorates your photo with silly emoji combinations. Try it out at <a href="https://cheese.polymer-project.org">cheese.polymer-project.org</a> and share your best photos with [@polymerLibrary](https://twitter.com/polymerLibrary).
 
 #### Polymon Global Scavenger Hunt
 

app/blog/2017-07-31-speaker-spotlight-josh.md

@@ -54,4 +54,4 @@ To be notified when registration opens, sign up with your email address at [g.co
 
 If you can't make it to Copenhagen, don't worry. The talks will be livestreamed and recorded for later, and the codelabs will be available online so you can try them out from anywhere.
 
-Follow us on Twitter [@polymer](https://twitter.com/polymer) for regular updates.
+Follow us on Twitter [@polymerLibrary](https://twitter.com/polymerLibrary) for regular updates.

app/blog/2017-08-03-speaker-spotlight-chad.md

@@ -20,7 +20,7 @@ We chose Polymer for the UI layer because of how close it was to the actual plat
 
 Extremely quickly--and it's very important.
 
-The theming is all tightly coupled to the same theming variables that our mobile clients already used. 
+The theming is all tightly coupled to the same theming variables that our mobile clients already used.
 
 The ability to not only get rid of, but realizing you don't need a CSS preprocessor is fabulous. CSS variables and shadow DOM give you everything you need to build a highly themeable app.
 
@@ -80,4 +80,4 @@ Tickets are free! [Register on the Polymer Summit 2017 website](https://summit.p
 
 If you can't make it to Copenhagen, don't worry. The talks will be livestreamed and recorded for later, and the codelabs will be available online so you can try them out from anywhere.
 
-Follow us on Twitter [@polymer](https://twitter.com/polymer) for regular updates.
+Follow us on Twitter [@polymerLibrary](https://twitter.com/polymerLibrary) for regular updates.

app/blog/2017-08-09-speaker-spotlight-maria.md

@@ -44,4 +44,4 @@ Tickets are free! [Register on the Polymer Summit 2017 website](https://summit.p
 
 If you can't make it to Copenhagen, don't worry. The talks will be livestreamed and recorded for later, and the codelabs will be available online so you can try them out from anywhere.
 
-Follow us on Twitter [@polymer](https://twitter.com/polymer) for regular updates.
+Follow us on Twitter [@polymerLibrary](https://twitter.com/polymerLibrary) for regular updates.

app/blog/2017-08-16-speaker-spotlight-kunal.md

@@ -8,7 +8,7 @@ One of my earliest projects at Netflix a couple of years ago was to build a dash
 
 **When and how did you first start using Polymer?**
 
-I had read about Web Components briefly a few years ago, and got another glimpse of the technology during the 2014 Chrome Dev Summit, but I hadn't actually used Web Components for anything at the time. When I joined Netflix in late 2015, one of my fellow engineers on a related team, John Tregoning, had just started using Polymer for one of the apps that he was building. I was curious to try it out too, so I decided to experiment with it and enjoyed the experience. Several of us have been building a number of apps with it since then! 
+I had read about Web Components briefly a few years ago, and got another glimpse of the technology during the 2014 Chrome Dev Summit, but I hadn't actually used Web Components for anything at the time. When I joined Netflix in late 2015, one of my fellow engineers on a related team, John Tregoning, had just started using Polymer for one of the apps that he was building. I was curious to try it out too, so I decided to experiment with it and enjoyed the experience. Several of us have been building a number of apps with it since then!
 
 **Could you tell me what excites you most about Progressive Web Apps?**
 
@@ -36,4 +36,4 @@ Tickets are free! [Register on the Polymer Summit 2017 website](https://summit.p
 
 If you can't make it to Copenhagen, don't worry. The talks will be livestreamed and recorded for later, and the codelabs will be available online so you can try them out from anywhere.
 
-Follow us on Twitter [@polymer](https://twitter.com/polymer) for regular updates.
+Follow us on Twitter [@polymerLibrary](https://twitter.com/polymerLibrary) for regular updates.

app/blog/2017-08-30-speaker-spotlight-bede.md

@@ -70,6 +70,6 @@ This year's summit took place August 22–23 in beautiful downtown [Copenhagen,
 
 If you missed it, you can catch up on all the talks on [the Polymer Summit 2017 website](https://summit.polymer-project.org/).
 
-Follow us on Twitter [@polymer](https://twitter.com/polymer) for regular updates.
+Follow us on Twitter [@polymerLibrary](https://twitter.com/polymerLibrary) for regular updates.
 
 

app/blog/2019-02-05-lit-element-and-lit-html-release.md

@@ -20,7 +20,7 @@ const myTemplate = (name) => html`
 `;
 ```
 
-It's simple to render a lit-html template: 
+It's simple to render a lit-html template:
 
 ```js
 render(myTemplate('Ada'), document.body);
@@ -68,9 +68,9 @@ This creates an element you can use anywhere you'd use a regular HTML element:
 
 `<name-tag name="Ida"></name-tag>`
 
-If you use Web Components already, you'll be happy to hear that they're now natively supported in Chrome, Safari and Firefox. Edge support is coming soon, and polyfills are only needed for legacy browser versions. 
+If you use Web Components already, you'll be happy to hear that they're now natively supported in Chrome, Safari and Firefox. Edge support is coming soon, and polyfills are only needed for legacy browser versions.
 
-If you're new to Web Components, you should give them a try! Web Components let you extend HTML in a way that interoperates with other libraries, tools, and frameworks. This makes them ideal for sharing UI elements within a large organization, publishing components for use anywhere on the web, or building UI design systems like Material Design. 
+If you're new to Web Components, you should give them a try! Web Components let you extend HTML in a way that interoperates with other libraries, tools, and frameworks. This makes them ideal for sharing UI elements within a large organization, publishing components for use anywhere on the web, or building UI design systems like Material Design.
 
 You can use custom elements anywhere you use HTML: in your main document, in a CMS, in Markdown, or in views [built with frameworks](https://custom-elements-everywhere.com/) like React and Vue. You can also mix and match LitElement components with other Web Components, whether they've been written using vanilla web technologies or made with the help of tools like [Salesforce Lightning Web Components](https://developer.salesforce.com/blogs/2018/12/introducing-lightning-web-components.html), Ionic's [Stencil](https://stenciljs.com/), [SkateJS](https://skatejs.netlify.com/) or the [Polymer library](https://polymer-library.polymer-project.org).
 
@@ -84,7 +84,7 @@ If you're interested in using lit-html by itself, or integrating lit-html templa
 
 * [lit-html docs](https://lit-html.polymer-project.org/)
 
-As always, let us know what you think. You can reach us on [Slack](/slack-invite) or [Twitter](https://twitter.com/polymer). Our projects are open source (of course!) and you can report bugs, file feature requests or suggest improvements on GitHub:
+As always, let us know what you think. You can reach us on [Slack](/slack-invite) or [Twitter](https://twitter.com/polymerLibrary). Our projects are open source (of course!) and you can report bugs, file feature requests or suggest improvements on GitHub:
 
 * [lit-html on GitHub](https://github.com/Polymer/lit-html)
 * [LitElement on GitHub](https://github.com/Polymer/lit-element)

app/summit-2015/index.html

@@ -59,7 +59,7 @@
                             <a href="https://plus.google.com/+PolymerProject" target="_blank" aria-label="Follow Polymer on G Plus">
                                 <iron-icon class="header-social-icon" icon="summit:post-gplus"></iron-icon>
                             </a>
-                            <a href="https://twitter.com/polymer" target="_blank" aria-label="Follow Polymer on Twitter">
+                            <a href="https://twitter.com/polymerLibrary" target="_blank" aria-label="Follow Polymer on Twitter">
                                 <iron-icon class="header-social-icon" icon="summit:post-twitter"></iron-icon>
                             </a>
                             <iron-icon role="button" aria-label="Open menu" on-keyup="_toggleDrawer" class="menu-icon narrow-only" icon="menu" drawer-toggle="" tabindex="0"></iron-icon>
@@ -151,7 +151,7 @@ <h3>Can’t make it this year?</h3>
                                             <paper-button class="anchor-button blue" raised="">
                                                 <iron-icon class="extended-icon" icon="summit:post-gplus"></iron-icon>Google+</paper-button>
                                         </a>
-                                        <a class="flex" tabindex="-1" target="_blank" href="https://twitter.com/polymer">
+                                        <a class="flex" tabindex="-1" target="_blank" href="https://twitter.com/polymerLibrary">
                                             <paper-button class="anchor-button blue" raised="">
                                                 <iron-icon class="extended-icon" icon="summit:post-twitter"></iron-icon>Twitter</paper-button>
                                         </a>

app/summit-2016/index.html

@@ -19,7 +19,7 @@
     <meta itemprop="startDate" content="2016-10-17T00:00:00Z">
     <meta itemprop="endDate" content="2016-10-18T23:59:59Z">
     <meta name="twitter:card" content="summary_large_image">
-    <meta name="twitter:site" content="@Polymer">
+    <meta name="twitter:site" content="@PolymerLibrary">
     <meta name="twitter:title" content="Polymer Summit 2016">
     <meta name="twitter:description" content="Two days of sessions and codelabs on all things Polymer and Web Components - building great components and apps, scaling within an organization, and more.">
     <meta name="twitter:image" content="https://www.polymer-project.org/summit-2016/images/badge-2016-banner.png">
@@ -75,7 +75,7 @@
                             <a href="https://plus.google.com/+PolymerProject" target="_blank" aria-label="Follow Polymer on G Plus">
                                 <iron-icon class="header-social-icon" icon="summit:post-gplus"></iron-icon>
                             </a>
-                            <a href="https://twitter.com/polymer" target="_blank" aria-label="Follow Polymer on Twitter">
+                            <a href="https://twitter.com/polymerLibrary" target="_blank" aria-label="Follow Polymer on Twitter">
                                 <iron-icon class="header-social-icon" icon="summit:post-twitter"></iron-icon>
                             </a>
                             <iron-icon role="button" aria-label="Open menu" on-keyup="_toggleDrawer" class="menu-icon narrow-only" icon="menu" drawer-toggle="" tabindex="0"></iron-icon>
@@ -199,7 +199,7 @@ <h3>Can’t make it this year?</h3>
                                           <paper-button class="anchor-button blue" raised="">
                                               <iron-icon class="extended-icon" icon="summit:post-gplus"></iron-icon>Google+</paper-button>
                                       </a>
-                                      <a class="flex" tabindex="-1" target="_blank" href="https://twitter.com/polymer">
+                                      <a class="flex" tabindex="-1" target="_blank" href="https://twitter.com/polymerLibrary">
                                           <paper-button class="anchor-button blue" raised="">
                                               <iron-icon class="extended-icon" icon="summit:post-twitter"></iron-icon>Twitter</paper-button>
                                       </a>