The journey of creating a design systems and how to scape the common pitfalls to reach success implementing a design system in your company.

Design systems are often seen as essential in growing organizations. However, where design team is under-resourced, maintaining and evolving a coherent system becomes a challenge. This talk presents a pragmatic, engineer-led approach to promoting, using concrete React patterns and architecture.

Each component property in your design system serves as an entry point to your component library and its developer experience is largely influenced by their structure and implementation. In this talk, we'll explore multiple ideas to refine your thought process when working on components and make your libraries more user-friendly for other developers.

There have been many react component patterns used over the years to facilitate the composition of frontend software.

However, React has evolved over the years especially with the introduction of hooks and context. Newer ways to do things clash with the so-called "older ones". In my talk, I want to take a relook the patterns from the perspective of a developer's needs for implementation, be it extracting logic, combining props, handling hierarchy, or inverting control of state.

Once the need is established, it is helpful to compare the new and the old patterns, if they exist, for the same goal and understand the pros and cons of each.