From 5dcf341354db3c0699dc33c898512cad3ccd10c4 Mon Sep 17 00:00:00 2001 From: Arthur Evans Date: Mon, 3 Oct 2016 22:20:16 -0700 Subject: [PATCH 01/16] Initial 2.0 content, plus detritus. --- app/2.0/404.html | 69 + app/2.0/500.html | 69 + app/2.0/about.html | 135 ++ app/2.0/authors.yaml | 66 + app/2.0/blog.yaml | 150 ++ app/2.0/blog/2015-05-29-one-dot-oh.md | 46 + app/2.0/blog/2015-08-13-1.1-release.md | 69 + .../2015-08-20-polymer-summit-schedule.md | 11 + ...mmunicate-with-nearby-bluetooth-devices.md | 145 ++ .../blog/2015-09-20-polymer-summit-recap.md | 116 ++ .../2015-10-16-polymer-roadmap-and-repo.md | 13 + app/2.0/blog/2015-11-02-release-1.2.0.md | 200 +++ app/2.0/blog/2015-12-01-deprecating-deep.md | 72 + app/2.0/blog/2016-02-17-2016-roadmap.md | 96 ++ ...16-03-10-community-highlights-predix-ui.md | 13 + .../blog/2016-03-28-carbon-route-released.md | 33 + app/2.0/blog/2016-05-19-Polymer-IO-2016.md | 129 ++ app/2.0/blog/2016-05-26-IO-2016-Recap.md | 46 + ...8-18-polymer-starter-kit-or-polymer-cli.md | 104 ++ app/2.0/blog/2016-09-09-polymer-2.0.md | 95 ++ app/2.0/blog/es6.md | 288 ++++ app/2.0/blog/index.html | 6 + app/2.0/blog/routing.md | 151 ++ app/2.0/blog/routing/demo1.html | 59 + app/2.0/blog/routing/demo2.html | 64 + app/2.0/blog/routing/demo3.html | 157 ++ app/2.0/blog/routing/resizer.js | 9 + app/2.0/blog/shadydom.md | 198 +++ app/2.0/docs/about_10.md | 200 +++ app/2.0/docs/api/Polymer.Base.html | 7 + app/2.0/docs/api/Polymer.Templatizer.html | 7 + app/2.0/docs/api/array-selector.html | 7 + app/2.0/docs/api/custom-style.html | 7 + app/2.0/docs/api/dom-bind.html | 7 + app/2.0/docs/api/dom-if.html | 7 + app/2.0/docs/api/dom-repeat.html | 7 + app/2.0/docs/api/dom-template.html | 7 + app/2.0/docs/browsers.md | 143 ++ app/2.0/docs/community.md | 48 + app/2.0/docs/devguide/behaviors.md | 157 ++ app/2.0/docs/devguide/custom-elements.md | 342 ++++ app/2.0/docs/devguide/data-binding.md | 648 +++++++ app/2.0/docs/devguide/data-system.md | 788 +++++++++ app/2.0/docs/devguide/dom-template.md | 85 + app/2.0/docs/devguide/events.md | 232 +++ app/2.0/docs/devguide/experimental.md | 96 ++ app/2.0/docs/devguide/feature-overview.md | 82 + app/2.0/docs/devguide/gesture-events.md | 130 ++ app/2.0/docs/devguide/instance-methods.md | 116 ++ app/2.0/docs/devguide/local-dom.md | 557 ++++++ app/2.0/docs/devguide/model-data.md | 293 ++++ app/2.0/docs/devguide/moved-to-obs | 35 + app/2.0/docs/devguide/observers.md | 610 +++++++ app/2.0/docs/devguide/properties.md | 443 +++++ app/2.0/docs/devguide/quick-tour.md | 177 ++ app/2.0/docs/devguide/registering-elements.md | 205 +++ .../configurable-name-tag.html | 29 + .../samples/configurable-name-tag/index.html | 12 + .../custom-element/custom-element.html | 17 + .../samples/custom-element/index.html | 10 + .../samples/dom-element/dom-element.html | 15 + .../devguide/samples/dom-element/index.html | 10 + .../editable-name-tag/editable-name-tag.html | 28 + .../samples/editable-name-tag/index.html | 10 + .../docs/devguide/samples/name-tag/index.html | 10 + .../devguide/samples/name-tag/name-tag.html | 20 + .../devguide/samples/picture-frame/index.html | 12 + .../samples/picture-frame/picture-frame.html | 28 + app/2.0/docs/devguide/settings.md | 43 + app/2.0/docs/devguide/styling.md | 751 ++++++++ app/2.0/docs/devguide/templates.md | 531 ++++++ app/2.0/docs/migration.md | 1466 ++++++++++++++++ app/2.0/docs/release-notes.md | 1510 +++++++++++++++++ app/2.0/docs/tools/advanced.md | 152 ++ app/2.0/docs/tools/documentation.md | 352 ++++ app/2.0/docs/tools/index.html | 35 + app/2.0/docs/tools/optimize-for-production.md | 289 ++++ app/2.0/docs/tools/overview.md | 17 + app/2.0/docs/tools/polymer-cli.md | 381 +++++ app/2.0/docs/tools/reusable-elements.md | 191 +++ app/2.0/docs/tools/services.md | 61 + app/2.0/docs/tools/tests.md | 403 +++++ .../homepage/contact-card/contact-card.html | 47 + app/2.0/homepage/contact-card/index.html | 13 + app/2.0/homepage/google-map/index.html | 19 + app/2.0/index.html | 441 +++++ app/2.0/nav.yaml | 227 +++ app/2.0/samples/test.html | 12 + app/2.0/start/first-element/intro.md | 125 ++ app/2.0/start/first-element/step-2.md | 241 +++ app/2.0/start/first-element/step-3.md | 139 ++ app/2.0/start/first-element/step-4.md | 62 + app/2.0/start/first-element/step-5.md | 178 ++ app/2.0/start/index.html | 123 ++ app/2.0/start/toolbox/add-elements.md | 80 + app/2.0/start/toolbox/create-a-page.md | 203 +++ app/2.0/start/toolbox/deploy.md | 149 ++ app/2.0/start/toolbox/set-up.md | 102 ++ app/2.0/start/what-is-polymer.md | 80 + app/2.0/test.md | 55 + app/2.0/toolbox/app-layout.md | 454 +++++ app/2.0/toolbox/app-storage.md | 37 + app/2.0/toolbox/case-study.md | 269 +++ app/2.0/toolbox/getstarted.md | 22 + app/2.0/toolbox/index.md | 40 + app/2.0/toolbox/localize.md | 74 + app/2.0/toolbox/routing.md | 164 ++ app/2.0/toolbox/server.md | 167 ++ app/2.0/toolbox/service-worker.md | 102 ++ app/2.0/toolbox/templates.md | 61 + .../2.0/toolbox/starter-kit-checkbox.png | Bin 0 -> 40973 bytes 111 files changed, 18121 insertions(+) create mode 100644 app/2.0/404.html create mode 100644 app/2.0/500.html create mode 100644 app/2.0/about.html create mode 100644 app/2.0/authors.yaml create mode 100644 app/2.0/blog.yaml create mode 100644 app/2.0/blog/2015-05-29-one-dot-oh.md create mode 100644 app/2.0/blog/2015-08-13-1.1-release.md create mode 100644 app/2.0/blog/2015-08-20-polymer-summit-schedule.md create mode 100644 app/2.0/blog/2015-09-10-discover-and-communicate-with-nearby-bluetooth-devices.md create mode 100644 app/2.0/blog/2015-09-20-polymer-summit-recap.md create mode 100644 app/2.0/blog/2015-10-16-polymer-roadmap-and-repo.md create mode 100644 app/2.0/blog/2015-11-02-release-1.2.0.md create mode 100644 app/2.0/blog/2015-12-01-deprecating-deep.md create mode 100644 app/2.0/blog/2016-02-17-2016-roadmap.md create mode 100644 app/2.0/blog/2016-03-10-community-highlights-predix-ui.md create mode 100644 app/2.0/blog/2016-03-28-carbon-route-released.md create mode 100644 app/2.0/blog/2016-05-19-Polymer-IO-2016.md create mode 100644 app/2.0/blog/2016-05-26-IO-2016-Recap.md create mode 100644 app/2.0/blog/2016-08-18-polymer-starter-kit-or-polymer-cli.md create mode 100644 app/2.0/blog/2016-09-09-polymer-2.0.md create mode 100644 app/2.0/blog/es6.md create mode 100644 app/2.0/blog/index.html create mode 100644 app/2.0/blog/routing.md create mode 100644 app/2.0/blog/routing/demo1.html create mode 100644 app/2.0/blog/routing/demo2.html create mode 100644 app/2.0/blog/routing/demo3.html create mode 100644 app/2.0/blog/routing/resizer.js create mode 100644 app/2.0/blog/shadydom.md create mode 100644 app/2.0/docs/about_10.md create mode 100644 app/2.0/docs/api/Polymer.Base.html create mode 100644 app/2.0/docs/api/Polymer.Templatizer.html create mode 100644 app/2.0/docs/api/array-selector.html create mode 100644 app/2.0/docs/api/custom-style.html create mode 100644 app/2.0/docs/api/dom-bind.html create mode 100644 app/2.0/docs/api/dom-if.html create mode 100644 app/2.0/docs/api/dom-repeat.html create mode 100644 app/2.0/docs/api/dom-template.html create mode 100644 app/2.0/docs/browsers.md create mode 100644 app/2.0/docs/community.md create mode 100644 app/2.0/docs/devguide/behaviors.md create mode 100644 app/2.0/docs/devguide/custom-elements.md create mode 100644 app/2.0/docs/devguide/data-binding.md create mode 100644 app/2.0/docs/devguide/data-system.md create mode 100644 app/2.0/docs/devguide/dom-template.md create mode 100644 app/2.0/docs/devguide/events.md create mode 100644 app/2.0/docs/devguide/experimental.md create mode 100644 app/2.0/docs/devguide/feature-overview.md create mode 100644 app/2.0/docs/devguide/gesture-events.md create mode 100644 app/2.0/docs/devguide/instance-methods.md create mode 100644 app/2.0/docs/devguide/local-dom.md create mode 100644 app/2.0/docs/devguide/model-data.md create mode 100644 app/2.0/docs/devguide/moved-to-obs create mode 100644 app/2.0/docs/devguide/observers.md create mode 100644 app/2.0/docs/devguide/properties.md create mode 100644 app/2.0/docs/devguide/quick-tour.md create mode 100644 app/2.0/docs/devguide/registering-elements.md create mode 100644 app/2.0/docs/devguide/samples/configurable-name-tag/configurable-name-tag.html create mode 100644 app/2.0/docs/devguide/samples/configurable-name-tag/index.html create mode 100644 app/2.0/docs/devguide/samples/custom-element/custom-element.html create mode 100644 app/2.0/docs/devguide/samples/custom-element/index.html create mode 100644 app/2.0/docs/devguide/samples/dom-element/dom-element.html create mode 100644 app/2.0/docs/devguide/samples/dom-element/index.html create mode 100644 app/2.0/docs/devguide/samples/editable-name-tag/editable-name-tag.html create mode 100644 app/2.0/docs/devguide/samples/editable-name-tag/index.html create mode 100644 app/2.0/docs/devguide/samples/name-tag/index.html create mode 100644 app/2.0/docs/devguide/samples/name-tag/name-tag.html create mode 100644 app/2.0/docs/devguide/samples/picture-frame/index.html create mode 100644 app/2.0/docs/devguide/samples/picture-frame/picture-frame.html create mode 100644 app/2.0/docs/devguide/settings.md create mode 100644 app/2.0/docs/devguide/styling.md create mode 100644 app/2.0/docs/devguide/templates.md create mode 100644 app/2.0/docs/migration.md create mode 100644 app/2.0/docs/release-notes.md create mode 100644 app/2.0/docs/tools/advanced.md create mode 100644 app/2.0/docs/tools/documentation.md create mode 100644 app/2.0/docs/tools/index.html create mode 100644 app/2.0/docs/tools/optimize-for-production.md create mode 100644 app/2.0/docs/tools/overview.md create mode 100644 app/2.0/docs/tools/polymer-cli.md create mode 100644 app/2.0/docs/tools/reusable-elements.md create mode 100644 app/2.0/docs/tools/services.md create mode 100644 app/2.0/docs/tools/tests.md create mode 100755 app/2.0/homepage/contact-card/contact-card.html create mode 100755 app/2.0/homepage/contact-card/index.html create mode 100755 app/2.0/homepage/google-map/index.html create mode 100644 app/2.0/index.html create mode 100644 app/2.0/nav.yaml create mode 100644 app/2.0/samples/test.html create mode 100644 app/2.0/start/first-element/intro.md create mode 100644 app/2.0/start/first-element/step-2.md create mode 100644 app/2.0/start/first-element/step-3.md create mode 100644 app/2.0/start/first-element/step-4.md create mode 100644 app/2.0/start/first-element/step-5.md create mode 100644 app/2.0/start/index.html create mode 100644 app/2.0/start/toolbox/add-elements.md create mode 100644 app/2.0/start/toolbox/create-a-page.md create mode 100644 app/2.0/start/toolbox/deploy.md create mode 100644 app/2.0/start/toolbox/set-up.md create mode 100644 app/2.0/start/what-is-polymer.md create mode 100644 app/2.0/test.md create mode 100644 app/2.0/toolbox/app-layout.md create mode 100644 app/2.0/toolbox/app-storage.md create mode 100644 app/2.0/toolbox/case-study.md create mode 100644 app/2.0/toolbox/getstarted.md create mode 100644 app/2.0/toolbox/index.md create mode 100644 app/2.0/toolbox/localize.md create mode 100644 app/2.0/toolbox/routing.md create mode 100644 app/2.0/toolbox/server.md create mode 100644 app/2.0/toolbox/service-worker.md create mode 100644 app/2.0/toolbox/templates.md create mode 100644 app/images/2.0/toolbox/starter-kit-checkbox.png diff --git a/app/2.0/404.html b/app/2.0/404.html new file mode 100644 index 0000000000..7df8494e60 --- /dev/null +++ b/app/2.0/404.html @@ -0,0 +1,69 @@ + + + + +404 - Polymer Project +{% include 'templates/head-meta.html' %} + + + + {% include 'templates/site-nav.html' %} + + +
+
+
+ Offline Polymer dinosaur +
+
+

Not found.

+

We're sorry, but the polymerosaurus can't find the page you were looking for.

+

Maybe head back to the homepage or use one of the menu links instead?

+
+
+
+ + + + + diff --git a/app/2.0/500.html b/app/2.0/500.html new file mode 100644 index 0000000000..31e0fb9543 --- /dev/null +++ b/app/2.0/500.html @@ -0,0 +1,69 @@ + + + + +500 - Polymer Project +{% include 'templates/head-meta.html' %} + + + + + {% include 'templates/site-nav.html' %} + +
+
+
+ Offline Polymer dinosaur +
+
+

EEEEK...500!

+

There was an issue on our end :(

+

Maybe head back to the homepage or use one of the menu links instead?

+
+
+
+ + + + + diff --git a/app/2.0/about.html b/app/2.0/about.html new file mode 100644 index 0000000000..06413a499e --- /dev/null +++ b/app/2.0/about.html @@ -0,0 +1,135 @@ + + + + +About the Polymer Project +{% include 'templates/head-meta.html' %} + + + + {% include 'templates/site-nav.html' %} + + +
+
+

About the Polymer Project

+
+
+ +
+
+

Who we are

+ +

The Polymer Project is an open-source project led by a team of front-end developers working within the Chrome organization at Google.

+ +

Our mission

+ +

Our mission is to make life better for users and developers, by helping developers unlock the web platform’s full potential and by spurring the web platform to evolve and improve.

+ +

In pursuit of this mission, we work on libraries, tools and patterns to help developers build modern Progressive Web Apps, taking full advantage of cutting-edge platform features like Web Components, Service Workers and HTTP/2.

+ +

We also collaborate closely with our colleagues on the Chrome development team, identifying pain points, putting new platform features to the test and doing our part to ensure that front-end developers have a strong voice in the evolution of the platform.

+ +

Our motto, reflecting our unique mission, is #UseThePlatform. It’s worth explaining what that means to us.

+ +

Why #UseThePlatform?

+ +

tl;dr: We believe that embracing the modern web platform is the best way to give users and developers what they deserve.

+ +

Users deserve apps that launch quickly, respond instantly and can be accessed from anywhere—on devices of all types and sizes, under any network conditions.

+ +

Developers deserve a platform they can work with, not around—one that makes it easy to build, deliver and maintain these universally accessible, reliable, delightful, high-performing apps.

+ +

But we haven’t always gotten what we deserve from the web, especially when it comes to mobile.

+ +
    +

  • From a user point of view, too many mobile web apps launch slowly, perform poorly compared to native apps, and don’t work at all when network conditions are poor.

    • +

  • For app developers, the web platform has been frustratingly slow to evolve. For years, we’ve had to plug holes in the platform and build layers on top of it to meet basic needs like defining components and loading modules.

    • +
+ +

Credit where credit is due

+ +

The libraries, tools and frameworks we’ve built to fill the gaps in the web platform are a testament to the web’s fundamental extensibility and to the endlessly innovative spirit of the web community.

+ +

These innovations have been instrumental in the web’s transition from a content platform to a platform that supports powerful, feature-rich applications. There’s no doubt that the path forward will continue to be cleared and illuminated by our collective efforts in “user space.”

+ +

That said, there are real costs to doing too much outside and above the platform itself—costs that both developers and users pay.

+ +

Developer costs

+ +

Developer costs come in the form of complexity and lock-in.

+ +

Over time, the stacks we’ve built on top of the platform have pushed web development further and further from the simplicity of view-source and shift-refresh, to a place where every project begins with an overwhelming sea of choices.

+ +

And when we rely on libraries and frameworks for even our most basic needs, we end up writing code that depends on opinionated abstractions rather than universal platform primitives. Because it’s expensive to migrate from one abstraction to another, these dependencies limit our future choices and make our code costlier to maintain.

+ +

User costs

+ +

More importantly, users pay a performance penalty when the layers we build above the platform become too thick.

+ +

Every byte of code that we send over the wire consumes bandwidth that could be used for content and data, and every tick we spend executing JavaScript on the client reduces our apps’ responsiveness. This is especially true on the far reaches of the mobile web, where poor connections and underpowered devices are the norm.

+ +

Many of the development patterns that we use today originated in an era when we used the web mostly from the desktop. Now that the web is mobile-first, we need to reconsider those patterns. Giving our users the experience they deserve in the hyper-constrained mobile environment means aggressively minimizing bandwidth and execution cost, leaning heavily on the platform and saving our limited budget for things that only our applications can provide.

+ +

For example, the browser specializes in loading resources, parsing native web formats like HTML and CSS, and caching them for maximum efficiency. Similarly, the browser has highly optimized native code for instantiating elements, inserting them in the DOM, updating their properties and attributes, managing the flow of events between them, and eventually tearing them down.

+ +

When we write our own code to do these things, send that code over the network and execute it on the client, we are doing work we shouldn’t have to do; and in some cases, we are also negating current and future browser-side optimizations.

+ +

A platform-centric path forward

+ +

Thanks to new web platform primitives, many of the needs we’ve addressed by building over and around the platform can now be met by the platform itself:

+ +
    +

  • Web Components let us extend the browser’s built-in component model—the DOM—rather than bring our own.

    • + +

  • In combination with HTTP/2 and server push, standard module formats like HTML Imports and ES6 Modules let us declare fine-grained dependencies and efficiently deliver them to the client in optimally cacheable form, without relying on complicated packaging tools and loaders.

    • + +

  • Service Workers let us build pure web apps that users can access even when their devices are offline or network conditions are poor, whereas previously we might have had to resort to manually installable native or “hybrid” apps.

    • +
+ +

We believe that in the next era, the best-performing apps will be those that take full advantage of these modern web platform features and let the browser do the heavy lifting wherever it can. Similarly, the least costly, most future-proof apps will be those that build as much as possible on platform primitives, maximizing interoperability and minimizing switching costs.

+ +

Rethinking libraries and frameworks

+ +

Using the platform doesn’t mean leaving libraries and frameworks behind; it just means making them lighter, and designing them to complement the strengths of the platform itself.

+ +

At their best, libraries and frameworks make our jobs easier. They provide off-the-shelf solutions for hard problems; broadly applicable abstractions that save us from reinventing the wheel; and useful patterns and constraints to help us structure our apps intelligently and avoid shooting ourselves in the foot.

+ +

The challenge is to achieve these benefits while minimizing the weight of our solutions and making the most of what the platform provides.

+ +

Within this problem space, as always, there’s plenty of room for innovation and opinion. For our part, we aim to treat the platform as the framework, adding value in the form of lightweight, optional “sugaring” of platform APIs; loosely coupled, interoperable modules; and effective patterns for composing components and applications from smaller building blocks.

+ +

Our role

+ +

Returning to our mission, here’s how we see our role:

+ +
    +

  • Strongly advocate a platform-centric approach to building modern web apps

    • + +

  • Build libraries and tools to support app developers in adopting a platform-centric approach

    • + +

  • In doing so, explore and exemplify best practices for designing platform-centric libraries and tools

    • + +

  • Based on our own experiences and those of the broader community, continue to influence the evolution of the platform from within the Chrome organization

    • +
+ +

We believe the patterns, libraries and tools we work on are beneficial, and we're happy to see them widely adopted.

+ +

But our campaign to #UseThePlatform is ultimately not about driving people to use the stuff the Polymer Project builds. It’s about promoting the use of the web platform to deliver the best apps possible, and helping to ensure that web users and developers get everything they deserve from the platform in the future.

+
+
+ + + + + + diff --git a/app/2.0/authors.yaml b/app/2.0/authors.yaml new file mode 100644 index 0000000000..cba33b9d12 --- /dev/null +++ b/app/2.0/authors.yaml @@ -0,0 +1,66 @@ +--- +ebidel: + full_name: Eric Bidelman + gplus: +EricBidelman + profile_pic: https://lh5.googleusercontent.com/-kgFnix5akCc/AAAAAAAAAAI/AAAAAAAAOqk/IVG-V3nJ8jM/s40-c/photo.jpg + web: http://www.ericbidelman.com + twitter: ebidel + github: ebidel + +addyosmani: + full_name: Addy Osmani + gplus: 115133653231679625609 + profile_pic: https://lh3.googleusercontent.com/-riQH0F3Zb2k/AAAAAAAAAAI/AAAAAAAAyyI/A0ynkSbO-nM/s40-c/photo.jpg + web: http://addyosmani.com/ + twitter: addyosmani + github: addyosmani + +robdodson: + full_name: Rob Dodson + gplus: +RobDodson + profile_pic: https://lh3.googleusercontent.com/-0IG6advy6qg/AAAAAAAAAAI/AAAAAAAAAJM/pivb_QaIJjQ/s40-c/photo.jpg + web: http://robdodson.me + twitter: rob_dodson + github: robdodson + +alice: + full_name: Alice Boxhall + gplus: 111975973972817482025 + profile_pic: https://lh5.googleusercontent.com/-nS21Q4tD1R4/AAAAAAAAAAI/AAAAAAAAAp4/ixMudlaPGDs/s40-c/photo.jpg + twitter: sundress + github: alice + +sjmiles: + full_name: Scott Miles + gplus: 116100920359918112000 + profile_pic: https://lh3.googleusercontent.com/-7uiizITSXzc/AAAAAAAAAAI/AAAAAAAAAH0/qiZVhp4C0i8/s40-c/photo.jpg + twitter: scottjmiles + github: sjmiles + +rictic: + full_name: Peter Burns + gplus: +PeterBurnsrictic + profile_pic: https://lh3.googleusercontent.com/-JcCDjeNJTuk/AAAAAAAAAAI/AAAAAAAAJo0/wZSCEJGEacI/s120-c/photo.jpg + twitter: rictic + github: rictic + +polymer-team: + full_name: Polymer Team + gplus: +PolymerProject + profile_pic: /images/logos/p-author-logo.png + web: https://www.polymer-project.org/ + twitter: polymer + github: polymer + +taylor: + full_name: Taylor Savage + gplus: 102507331653262188696 + profile_pic: https://lh3.googleusercontent.com/-3m6T7W06bm4/AAAAAAAAAAI/AAAAAAAAAW8/RulK3UZPplI/s120-c/photo.jpg + github: tjsavage + twitter: taylorthesavage + +fbeaufort: + full_name: François Beaufort + gplus: +FrancoisBeaufort + profile_pic: https://lh3.googleusercontent.com/-jHvqK47b3F4/AAAAAAAAAAI/AAAAAAAA-0w/fayGhfYcgrk/s120-c/photo.jpg + github: beaufortfrancois diff --git a/app/2.0/blog.yaml b/app/2.0/blog.yaml new file mode 100644 index 0000000000..1234146b3f --- /dev/null +++ b/app/2.0/blog.yaml @@ -0,0 +1,150 @@ +--- +- title: "Polymer 2.0 Preview" + path: /1.0/blog/2016-09-09-polymer-2.0 + published: 2016-09-09 + author: polymer-team + description: "Check out the preview branch of the forthcoming Polymer 2.0 release." + tags: + - blog + - announcements +- title: "Should I Use Polymer Starter Kit or Polymer CLI" + path: /1.0/blog/2016-08-18-polymer-starter-kit-or-polymer-cli + published: 2016-08-22 + author: polymer-team + description: "A new, updated Polymer Starter Kit is now available through the Polymer CLI." + tags: + - blog + - announcements +- title: "I/O 2016 Recap: #UseThePlatform" + path: /1.0/blog/2016-05-26-IO-2016-Recap + published: 2016-05-26 + author: polymer-team + description: "A look back at Google I/O 2016, and some background on the Polymer Project's call to #UseThePlatform." + tags: + - blog + - announcements +- title: "Polymer at Google I/O 2016" + path: /1.0/blog/2016-05-19-Polymer-IO-2016 + published: 2016-05-19 + author: polymer-team + description: "At Google I/O 2016, we launched the brand-new Polymer App Toolbox for building Progressive Web Apps." + tags: + - blog + - announcements +- title: " gets its beta release!" + path: /1.0/blog/2016-03-28-carbon-route-released + published: 2016-03-28 + author: polymer-team + description: "The app-route element has made its beta debut - we'd love your feedback on this modular approach to routing." + tags: + - blog + - announcements +- title: "Encapsulated Routing with Elements" + description: "An overview to doing distributed routing in an application, as well as an introduction to and ." + published: 2016-03-25 + author: rictic + polymer_version: 1.4.0 + path: /1.0/blog/routing + tags: + - routing + - urls +- title: "Community Highlights - GE Predix UI" + description: "GE's Predix UI provides Polymer-based components for building dashboards for the industrial Internet of Things." + published: 2016-03-10 + author: polymer-team + path: /1.0/blog/2016-03-10-community-highlights-predix-ui + tags: + - blog + - featured +- title: 2016 Roadmap + description: "A spin through the Polymer project roadmap for the beginning of 2016." + published: 2016-02-16 + author: polymer-team + path: /1.0/blog/2016-02-17-2016-roadmap + tags: + - blog + - announcements +- title: "Deprecating /deep/" + path: /1.0/blog/2015-12-01-deprecating-deep + published: 2015-12-01 + author: polymer-team + description: "We're updating elements to remove usage of /deep/ and ::shadow. This might cause some unexpected changes if you were relying on side-effects of these selectors." + tags: + - blog + - announcements +- title: "Introducing Polymer 1.2.0" + path: /1.0/blog/2015-11-02-release-1.2.0 + published: 2015-11-02 + author: polymer-team + description: "Polymer 1.2 introduces some exciting, long-awaited new features: compound bindings and observing light DOM children." + tags: + - blog + - releases +- title: "Introducing the Polymer Project Roadmap and Repo" + path: /1.0/blog/2015-10-16-polymer-roadmap-and-repo + published: 2015-10-16 + author: taylor + description: "We're excited to open up the project's near-term roadmap. The roadmap is available in new repo - Polymer/project - to help enable project-level discussion and collaboration." + tags: + - blog + - announcements +- title: "Polymer Summit Recap" + path: /1.0/blog/2015-09-20-polymer-summit-recap + published: 2015-09-29 + author: taylor + description: "In case you missed any of the action at this year's Polymer Summit, we focused on three key themes: Develop, Design, and Deploy, giving concrete advice on how you can build your web app from start to finish. Here's a recap of all the highlights." + tags: + - blog + - announcements +- title: "Building web components using ES6 classes" + description: "How to build vanilla custom elements and Polymer elements using ES2015 features." + published: 2015-09-24 + author: ebidel + path: /1.0/blog/es6 + polymer_version: 1.1.0 + tags: + - es2015 + - es6 + - javascript +- title: "Discover and communicate with nearby Bluetooth devices" + path: /1.0/blog/2015-09-10-discover-and-communicate-with-nearby-bluetooth-devices + published: 2015-09-10 + author: fbeaufort + categories: announcements + description: "Introducing a new set of Polymer elements that simplify discovering and communicating with nearby Bluetooth devices, powered behind the scenes by the experimental Web Bluetooth API." + tags: + - blog + - announcements +- title: "Polymer Summit Schedule" + path: /1.0/blog/2015-08-20-polymer-summit-schedule + published: 2015-08-20 + author: polymer-team + description: "The schedule for the first ever Polymer summit is now live!" + tags: + - blog + - announcements +- title: "1.1 Release" + path: /1.0/blog/2015-08-13-1.1-release + published: 2015-08-13 + author: polymer-team + description: "We've added our first, small minor release. This includes a new way of sharing styles between elements and the main document." + tags: + - blog + - announcements +- title: "1.0" + path: /1.0/blog/2015-05-29-one-dot-oh + published: 2015-05-29 + author: polymer-team + description: "Today we’re incredibly excited to announce the 1.0 release of the Polymer library." + tags: + - blog + - announcements +- title: "What is shady DOM?" + description: "Why do we need a new kind of DOM?" + published: 2015-05-28 + author: sjmiles + polymer_version: 1.0 + path: /1.0/blog/shadydom + tags: + - shadowdom + - shadydom diff --git a/app/2.0/blog/2015-05-29-one-dot-oh.md b/app/2.0/blog/2015-05-29-one-dot-oh.md new file mode 100644 index 0000000000..7e2d25d8fe --- /dev/null +++ b/app/2.0/blog/2015-05-29-one-dot-oh.md @@ -0,0 +1,46 @@ +--- +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)._ + +Today we’re incredibly excited to announce the 1.0 release of the Polymer library. + +Since the 0.5 “Developer Preview” release, we’ve re-written the library from the ground up, focusing on cross-browser performance while keeping the developer-friendly ergonomics. The new library is 3x faster on Chrome, 4x faster on Safari, and 36% less code than in developer preview. And it’s ready to be used in production applications. + +For 0.9 users, this release has no breaking changes. Lots has changed under the hood, including major bug fixes and performance updates. We recommend updating all of your element dependencies to match this new version: `#^1.0.0` + +In addition to the library, we’re officially releasing new “product lines” of elements, all updated to work with the 1.0 release of the library. The element product lines built by the Polymer team include: + +* **paper-elements** - the reference implementation for material design on the web +* **iron-elements** - the core building blocks useful for any web application +* **google-web-components** - elements that wrap a multitude of Google services, making it easy to leverage maps, drive, signin, translate, and many more in your app with a single element. +* **platinum-elements** - add push notifications or offline caching to your app with a single element. The platinum product line wraps the new re-engagement API’s like service worker as easy-to-use elements. +* **gold-elements** - checkout flows are hard on the web, especially on mobile. The gold-elements make checkout easy with auto-validating elements for credit card fields, phone number fields, and more. + +This is just the beginning of these product lines - we'll be refining the elements, evolving the set, and adding new product lines to solve more and more problems that come up when building applications. + +### Get started with the new library + +We’ve updated the [polymer-project.org](https://www.polymer-project.org) site with documentation for the 1.0 release. Major new and updated features since the 0.5 “Developer Preview” release include: + +* Brand-new, fast, and easy-to-use data binding system +* Element theming and styling using custom CSS properties - no more messy `/deep/` and `::shadow` +* Fast and lightweight shadow DOM shim named shady DOM, for non-supporting browsers +* "Behaviors” mechanism for sharing behavior between elements + +It’s easier than ever to create high-quality, production-ready elements using Polymer, to use in your app or share with other developers. + +### Browse, demo, and learn how to use the latest elements built by the Polymer team + +Check out the many brand-new element product lines built by the Polymer team with the [Polymer elements catalog](https://elements.polymer-project.org). There you can browse for elements to help create or add features to your web app - whether you need buttons or layouts, Google maps or push notifications. For just about any problem you might need to solve on the web, there’s an element for that. + +### Kick off your app with the Polymer Starter Kit + +Looking for a fast and easy way to get started building a production-ready web application using Polymer? Use the [Polymer starter kit](https://github.com/polymerelements/polymer-starter-kit). Packed with the latest elements, ready-to-use boilerplate, and an end-to-end toolchain to use from development through production deployment, the starter kit works out of the box so you can focus on adding features right away. + +### Most importantly, thank you! + +This release and improvement from 0.5 to 1.0 would truly not have been possible without the immensely helpful, insightful, rapid feedback from you, the community. We don't mean this as a platitude - seriously on a daily basis we're deeply appreciative of the [awesome bug reports](https://github.com/webcomponents/webcomponentsjs/issues/299), [incredible tools](http://chuckh.github.io/road-to-polymer/), and [amazing GDE's](https://plus.sandbox.google.com/+ErikIsaksen/posts/BcBFZvdxLhs) that make this project and community truly special. + +We’re incredibly excited about this release and the present and future of the Polymer project, and can’t wait to see what you’ll build! diff --git a/app/2.0/blog/2015-08-13-1.1-release.md b/app/2.0/blog/2015-08-13-1.1-release.md new file mode 100644 index 0000000000..95fbde296b --- /dev/null +++ b/app/2.0/blog/2015-08-13-1.1-release.md @@ -0,0 +1,69 @@ +--- +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)._ + +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: + +## Polymer 1.1 + +This is a relatively small, **minor** release - no breaking changes, and only one feature addition: + +### New style recommendations and features + +We've built a new way to share styles between elements. The impetus stemmed from [this issue](https://github.com/Polymer/polymer/issues/1876): that given a user has made a `custom-style` for something like layout, it would be useful to use these same styles at the document-level as well as within an element itself. + +Previously, for example, if I wanted to share the following style: + + .warning { + color: red; + font-weight: bold; + } + +in both the main document as well as within elements and have it shimmed correctly, I would have needed to duplicate the exact CSS. + +This was particularly painful for CSS being used for something like layout classes, as well as for general "theme" CSS. If I wanted the styles to apply both in the document as well as in elements, I needed to duplicate the style. + +So we set out to find an ergonomic way to "include" a shared chunk of style directly into an element, as well as into a document-level ` + + + +This chunk of DOM - identified by its `shared-styles` id - can now be included into an element using the following syntax: + + + + + + + + +You can also include a shared style in a `custom-style` - that is, including shared styles to be used in the main document. The syntax for this is: + + + + + +
My App
+ + +
+ … +
+ + +``` + +The `id` attribute specifies the name you'll use to reference +your shared styles. Style module names use the same namespace as elements, +so your style modules must have unique names. + +Using the shared styles is a two-step process: you need to use a `` tag +to _import_ the module, and a ` + + Hi + + + +``` + +You can also use a shared style module in a `custom-style` element. + +```html + + + + +``` + +A single style tag can both `include` shared styles +and define local rules: + +```html + +``` + +(This works for both `custom-style` elements and ` +
This is local DOM
+ + +``` + +To specify a local DOM template now, use a `dom-module` tag, with your custom element name as its `id`: + +``` + + + + + + + + +``` + +**Note:** Prior to Polymer 1.1, we recommended placing +element styles **outside** of the `