Skip to main content

Component Library

A component library is living, breathing implementation of your style guide.​

Why doe we need a component library?

  1. Having a component library means less custom code for consumers.

  2. Since there's a central location, you can ensure all components meet accessibility requirements.

  3. Components become more robust with multiple contributors submitting bug fixes and improvements in a single place.

  4. Less duplication of code allows you to ship new products and rewrite legacy code faster.

  5. It's a shared set of UI components that developers can consume to build applications reflecting your brand. Some notable benefits:

Component libraries are broadly categorized under:​

  1. Basic Primitives
  2. Advanced Components
  3. Layout primitives
  4. Accessible Headless UI Primitives

There two levels of implementation​

Foundational - Abstract implementation ( html and css)​

It lays down the founddation which becomes the base for framework specific implementation to extend from. It becomes the single source of truth for any framework to extend from.

Foundation will be created purely on vanilla css and javascript(not all components require it)

High level - Rich or Framework based ( WebComponent + others)​

A high level implementation that extends the foundational implementation.

Currently first class webcomponents implementation will be supported by default.

Framework specific impelmenation for React and Angular will be done in coming future.