Skip to content

Commit

Permalink
Tweak wording.
Browse files Browse the repository at this point in the history
  • Loading branch information
kevinpschaaf committed May 4, 2018
1 parent fc0ce18 commit fb7630c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

[![Build Status](https://travis-ci.org/Polymer/polymer.svg?branch=master)](https://travis-ci.org/Polymer/polymer)

> ℹ️ Note: This is the current stable version of the Polymer library. At Google I/O 2018 we announced a new Web Component base class, [`LitElement`](https://github.com/PolymerLabs/lit-element), as a successor to the `PolymerElement` base class in the Polymer library, and we recommend new users consider using LitElement instead. The Polymer 3.0 library will be maintained for the foreseeable future, and we recommend existing users of Polymer 2.0 to [migrate](#about-polymer-30) elements to 3.0 for best compatibility with the JS ecosystem. Thanks to the interoperability of Web Components, elements built with Polymer 3.0 and LitElement can be mixed and matched in the same app, so developers can choose to migrate elements from Polymer 3.0 to LitElement incrementally. See our blog post on the [Polymer Project roadmap](https://www.polymer-project.org/blog/2018-05-02-roadmap-update.html) for more information.
> ℹ️ Note: This is the current stable version of the Polymer library. At Google I/O 2018 we announced a new Web Component base class, [`LitElement`](https://github.com/PolymerLabs/lit-element), as a successor to the `PolymerElement` base class in the Polymer library, and we recommend users consider starting new projects using LitElement instead. The Polymer 3.0 library will be maintained for the foreseeable future, and we recommend existing users of Polymer 2.0 to [migrate](#about-polymer-30) elements to 3.0 for best compatibility with the JS ecosystem. Thanks to the interoperability of Web Components, elements built with Polymer 3.0 and LitElement can be mixed and matched in the same app, so developers can choose to migrate elements from Polymer 3.0 to LitElement incrementally. See our blog post on the [Polymer Project roadmap](https://www.polymer-project.org/blog/2018-05-02-roadmap-update.html) for more information.
Polymer lets you build encapsulated, reusable [Web Components](https://www.webcomponents.org/introduction) that work just like standard HTML elements, to use in building web applications. Using a Web Commponent built with Polymer is as simple as importing its definition then using it like any other HTML element:

Expand Down

0 comments on commit fb7630c

Please sign in to comment.