1 - Initialization
This post is the first in the series. It talks about avoiding the Web Components constructor, events and life-cycle methods while rolling your approach.
2 - As a variable bucket
In this post I was trying to automatically declare new tags as they get written in the DOM. Here I introduce container elements, which allow their child tags to have any name by assuming that they will all be using the same Web Component class.
3 - Reversing Shadow DOM visibility
Once a Shadow DOM is used the browser assumes it to be the source of truth and the holder of the content that is going to be displayed. What if it was the other way around? In this post the child tags of a Web Component get displayed by default while the Shadow DOM is used to keep hidden state.
4 - Declarative State
This post uses the variable buckets from part 2 to declare complex app state.
5 - Getting tested
Trying to test Web Components without any bigger knowledge of its related best-practices. Just thoughts about trying it out and seeing where it goes.
A graphics framework that makes use of the Web Component techniques in this series.
Did you enjoy what you read? Was it inspiring or compelling in any way?
I can send you one e-mail per month with a quick recap of the posts I have written.
You can subscribe here.