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 2024-01-13 23:15:03 +01:00
parent 162b468d8d
commit 5e50df8613
1 changed files with 19 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -89,15 +89,27 @@
<section> <section>
<h2>Why use this base class?</h2> <h2>Why use this base class?</h2>
<p> <p>
Writing Web Components directly from Often times, when simple websites need a quick
<code-block inline>HTMLElement</code-block> can seem confusing and <a
hard to maintain, especially when coming from popular JS frameworks href="https://developer.mozilla.org/en-US/docs/Web/API/Web_Components/Using_custom_elements"
and other projects that recommend complex setups. target="_blank"
>custom element</a
>, the best way is still to create one extending from
<code-block inline>HTMLElement</code-block>. However, it can quickly
reach a point where writing the code from scratch can seem confusing
and hard to maintain especially when compared to other projects with
more advanced setups.
</p> </p>
<p> <p>
This project aims to address this with virtually zero tooling required Also, when coming from frameworks with an easy declarative coding
and thin abstractions from vanilla custom element APIs – giving you experience (using templates), the default imperative way (e.g.,
only the bare minimum code to be productive. declaring elements, manually attaching event handlers, and other DOM
manipulations) is a frequent pain point we see.
</p>
<p>
This project aims to address these with virtually zero tooling
required and thin abstractions from vanilla custom element APIs –
giving you only the bare minimum code to be productive.
</p> </p>
<p> <p>
It works on current-day browsers without needing compilers, It works on current-day browsers without needing compilers,