ayo/wcb
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(site): update why section

Browse source
This commit is contained in:
Ayo 2023-12-11 20:20:40 +01:00
parent 48bf30ea7b
commit 5cc52e66f4
1 changed files with 8 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
site/src/pages/index.html
View file

@ -88,15 +88,18 @@
<section> <section>
<p>Why use this base class?</p> <p>Why use this base class?</p>
<p> <p>
Writing Web Components from the vanilla Writing Web Components directly from
<code-block inline>HTMLElement</code-block> can seem confusing and <code-block inline>HTMLElement</code-block> can seem confusing and
hard to maintain, especially when coming from popular JS frameworks. hard to maintain, especially when coming from popular JS frameworks.
</p> </p>
<p> <p>
This project aims to ease this with virtually zero tooling required This project aims to address this with virtually zero tooling required
and working closest to vanilla custom element APIs. It works on and thin abstractions from vanilla custom element APIs – giving you
current-day browsers without needing compilers, transpilers, or only the bare minimum code to be productive.
polyfills. </p>
<p>
It works on current-day browsers without needing compilers,
transpilers, or polyfills.
</p> </p>
<p> <p>
Here's an interactive custom element: Here's an interactive custom element: