Webcomponents

In the early years of web development, there were three standard fundamentals upon which every website was built: HTML, CSS, and JavaScript. As time...

Day five of a series of interactive posts that explores the world of web components.

Web components won't take web development by storm, or show us the One True Way to build websites. What they will do is let us collectively build a rich ecosystem of dynamic components that work with any web stack.

Write components once, run everywhere.

Writing about the big beautiful mess that is making things for the world wide web.

In a recent post I answered a general question about Web Components and their lack of widespread adoption. I’m back with what is probably the most frequently asked question about Web Components:

Typically, when integrating emails into websites, I obfuscate the email address to prevent spam bots from collecting them. For React, there were already components that handled this task; however, without React, I couldn't find a suitable solution. Therefore, I created a web component: obfuscate-wc that now provides an HTML element capable of obfuscating your email

An extremely fast React-like javascript library for building modern user interfaces.

Frequently, we are asked by React developers why patterns they have learned while writing components using JSX do not translate to writing web components. In this post, I'll try to capture some common gotchas that developers coming from React or other JavaScript view frameworks may run into when writing plain vanilla web components.

This guide examines the core concepts, differences, features, and benefits of two frontend frameworks: Lit and React.