/
2022-02-21 - Component library approach discussion

2022-02-21 - Component library approach discussion

Owned by Robert Ruszczyk (Unlicensed)
Last updated: Feb 23, 2022
2 min read

Date

Feb 21, 2022

Meeting recording

Link: https://rbcom-my.sharepoint.com/:v:/g/personal/robert_ruszczyk_rb_com/Efu3b1E7IKpAkkGnuj3FlTkBHrSQe1OgzhYXTaLPyvQKLA

Participants

  • Reckitt (RB):

    Radosław Kowalewski
    Bartłomiej Kuśmierczuk
    Janusz Paprzycki
    Pawel Ploneczka
    Robert Ruszczyk

  • DataArt (DA):
    Julia Boyarshchikova
    Sergey Gromskiy
    Sergey Kiselyov
    Anton Merkulov
    Nikita Puzyrenko

Goals

Discuss the approach to component library

Action items

RB & DA to confirm hero banner as the POC component instead of a button
RB to share an example code

 

Key takeaways

  1. Button component won’t make a good POC, it’s better to use more complex component consisting of more atoms
  2. let's discuss components case by case - we might not be able to decide on the approach beforehand
  3. it will be easier to discuss the code when compared to discussing just the design
  4. let's start with the interfaces, it will show how components are meant to be used/extended/customized
  5. when possible use CSS instead of JS logic (for example layout direction)
  6. CSS in JS vs SCSS - requires POC (HeroBanner was proposed as a component that should be implemented in both approaches) - the main idea is to provide an easy approach for theming and keeping the great performance
  7. there might be some components that will require injecting the logic in order to avoid linking the Design System to the particular framework (for example we can't use Link coming from gatsby, however, the implementation of Link or logic behind could be injected into the component in the runtime)
  8. we might consider components connected to frameworks: Image vs GatsbyImage. Of course, it will imply organisms since the organism will have to know which version of the Image component should be rendered.

 

 

 

 

 

 

 

.