Reusable Web Components and Design Systems are hardBuilding, Maintaining and Sharing reusable Web Components or Design Systems are expensive tasks. The build setup is a PhD project, the tooling is straigth out of FisherPrice® and packaging everything together requires knowledge that goes way beyond useful front-end development skills.We believe there is a better way...WebComponents Studio is on a mission to streamline and empower the creation of Web Components and Design Systems. Reusable components are about productivity and agility. Let's forget about the unnecessary complexity and slowdown of the underlying plumbing and let's focus on coding beautiful components with built-in quality, accessibility, user-experience and developer-experience.Join the discuss on Slack
Why I use web componentsThis is some sort of answer to recent posts regarding Web Components, where more than a few misconceptions were delivered as fact.Let's start by defining what we are talking about.
As someone who makes stuff on the web, there are two things that I’ve been seeing quite a bit lately: Web Component discussion and CSS debates. I think that Web Components, or more specifically the Shadow DOM, is poised to solve some long-standing CSS problems. I’m a big fan of Web Components. In fact, I’m just wrapping up a book with Manning Publications now, called Web Components in Action.
Few things in the frontend world are as hot as Design Systems, the idea of building a design spec or library of reusable components that can be shared across a team or company. Design Systems enforce style and branding guidelines, reduce design fatigue for engineers, and consolidate component engineering to one single set of components and a team that builds them. Basically, they help teams manage design at scale.