We want to provide the community with well-known and experience-tested recommendations for their web component projects. Everything we do here is to encourage and support development with these open standards.
We want web component development to be accessible and approachable for everyone, regardless of their background. Therefore, our recommendations aim to be easy to use, be ready to use, and provide that “it just works” developer experience we all crave for the various aspects of web component development.
Best practices/recommendations and examples may change and evolve over time.
Why Web Components
We believe that web components provide a standards-based solution to problems like reusability, interoperability, and encapsulation.
What if you could remove code, gain performance, and streamline implementation across everything you build? Web components provide this through the power of subtraction.
- Increase your app’s performance.
- Write using a streamlined component API that combines the best bits of popular libraries and frameworks!
Just like querySelector reduces developers’ dependence on jQuery, the web components standards reduces the size and complexity of component libraries and frameworks. This ultimately benefits users by decreasing page load times and increasing app performance.
Using the browser’s standards-based component model will increase the longevity of your application. The web has an extremely strong tradition of backwards-compatibility. Standards bodies have consistently gone out of their way to maintain legacy APIs.
The web components standards are fairly low-level, letting library authors build upon them with innovative APIs. By using such libraries you can build your app in the style you want while still leveraging built-in browser features.
Feel free to critique, ask questions and join the conversation, we’d love to hear your opinions and feedback. You can reach us by creating an issue on our github or on the #open-wc channel in the Polymer slack.