Over the past few years, the number of web frameworks available to us has exploded. In some ways, the breadth of choice is a clear win for our ecosystem. However, for many of us, it also comes with harsh drawbacks: - Have you ever used a popular open-sourced component built for framework A, and wished it existed in framework B? What about a design system library? - Does your company have frontends built in different frameworks, and your web teams are frustrated about the wasted hours needed to achieve a consistent design system? - Does your team build SDKs for web frameworks, and must manually re-write them for each framework? The solution to all 3 of these problems exists today. To fully understand it, we must first examine today’s web frameworks, re-think what a component should look like, and introduce a new Intermediate Representation of our components. This is what we have done at Builder.io when we created Mitosis, and we’re excited to share it with everyone.
Check out more articles and videos
We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career

28 min
Web Components, Lit and Santa 🎅

33 min
Let's talk about Web Components

20 min
Immutable Web Apps

10 min
Web Components are awesome!

20 min
Web Components in React

12 min
Bringing Ionic (and Web Components) to React
Workshops on related topic

185 min
Web Components in Action
Workshop

111 min
Deploy a Web Component App and Set Up a Continuous Integration Workflow
Workshop
Upcoming events