| layout | default |
|---|---|
| load_polymer | true |
{% include alpha.html %}
{{site.project_title}} is a new type of library for the web, built on top of Web Components, and designed to leverage the evolving web platform on modern browsers. {: .lead }
{% include downloadbutton.html %}
<iframe src="/https/github.com/images/architecture-diagram.svg?{{'now' | date: "%Y%m%d"}}"></iframe> Architectural diagram
- A set of polyfills for emerging web platform features. Initially, these core features are enabled as polyfills but go away over time as browsers implement them.
- A next-generation web application framework built upon these core technologies.
- A set of comprehensive UI and utility components for building web applications. {: id="what-is" }
- Download the latest .zip from above or get the code.
- Fire up a web server. Include
<script src="polymer.min.js"></script>in your page. - Read the Getting Started guide.
- Learn how to soup-up your web components using the Polymer core.
- Play with the polymer-elements, polymer-ui-elements, and toolkit-ui.
Join the mailing list. Ask questions and give feedback!
The overall aim of {{site.project_title}} is to manage the complexity of building web applications.
Use the platform — Use as much or as little of the framework as you wish. An application can choose to load platform.js for just the polyfills or use polymer.js to give web components extra batteries. We call these types of elements "{{site.project_title}} elements".
Everything is an element — Encapsulation is the key to creating scalable, maintainable applications. All {{site.project_title}} resources are components, even ones that are non-visual. To construct an app, a developer creates new components, or uses ones {{site.project_title}} provides, and assembles them together. Focusing on individual, composable building blocks allows developers to "think locally" about their application, reducing complexity. With this divide-and-conquer approach, applications can simultaneously be simple and arbitrarily complicated.
Eliminate boilerplate — Developers should write the minimum amount of code possible to create their application. Anything repetitive should be re-factored into a component, handled by {{site.project_title}} itself, or added into the browser platform itself. {{site.project_title}} provides simple syntax without reducing features, and avoids boilerplate wherever possible.