feat(docs): clarify & emphasize alternative options
This commit is contained in:
parent
6f11f6fe85
commit
b6104ad1a1
1 changed files with 1 additions and 3 deletions
|
@ -12,7 +12,7 @@ When you extend the WebComponent class for your custom element, you only have to
|
|||
|
||||
The result is a reactive UI on property changes.
|
||||
|
||||
There's a trade off between productivity & lightweight-ness here and it is somewhere between [Microsoft's FASTElement](https://fast.design/) & [Google's LitElement](https://lit.dev/).
|
||||
Note that there's a trade off between productivity & lightweight-ness here, and the project aims to help in writing custom elements in the same way more mature and better maintained projects already do. Please look into popular options such as [Microsoft's FASTElement](https://fast.design/) & [Google's LitElement](https://lit.dev/) as well.
|
||||
|
||||
## Project Status
|
||||
|
||||
|
@ -26,8 +26,6 @@ For building advanced interactions, there is an in-progress work on smart diffin
|
|||
If you have some complex needs, we recommend using the `WebComponent` base class with a more mature rendering approach like `lit-html`, and here's a demo for that: [View on CodePen](https://codepen.io/ayoayco-the-styleful/pen/ZEwNJBR?editors=1010).
|
||||
</Aside>
|
||||
|
||||
...or you can even [use just parts](/just-parts) of it for your own base class.
|
||||
|
||||
## Installation
|
||||
|
||||
The library is distributed as complete ECMAScript Modules (ESM) and published on [NPM](https://ayco.io/n/web-component-base). Please
|
||||
|
|
Loading…
Reference in a new issue