Versions Compared

Version Old Version 1 New Version Current
Changes made by

Robert Ruszczyk

Robert Ruszczyk

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

\uD83D\uDDD3Date

🔴 Meeting recording

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

...

\uD83D\uDC65Participants

  • 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

\uD83E\uDD45Goals

Discuss the following based on the button component example:

  • What the component is for and how it is expected to be used - @Mckean, Nathan

  • Dos and don'ts for the component - team

  •  What is the component category - Atom, Molecule, Organism - @Ploneczka, Pawel (Contractor)

  • Design review and comments - DA, @Mckean, Nathan

  • What are component variations - team

  • Are there any accessibility watch outs? - team 

  • What are our assumptions around code? (HTML, CSS, JS & progressive enhancement) - DA, @Ploneczka, Pawel (Contractor)

  • Are there any analytics considerations? - team

  • What naming conventions do we need to consider? - probably one time discussion

  • What might trigger the need for the component to change (eg. responsive CSS, media queries, etc) - team

✅Action items

  •  DA to schedule meetings for components prioritization

⤴Key takeaways

...

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

  • Button component won’t make a good POC, it’s better to use more complex component consisting of more atoms
  • let's discuss components case by case - we might not be able to decide on the approach beforehand
  • it will be easier to discuss the code when compared to discussing just the design
  • let's start with the interfaces, it will show how components are meant to be used/extended/customized
  • when possible use CSS instead of JS logic (for example layout direction)
  • 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
  • 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)
  • 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.

.