Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

\uD83D\uDDD3Date

đź”´ Meeting recording

Link:

TBC

\uD83D\uDC65Participants

  • Reckitt (RB):

    Bartłomiej Kuśmierczuk
    Janusz Paprzycki
    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

  • Button should be used for actions & links used for links. Do not style links as buttons and buttons as links, we should restrict the freedom of content editors
  • Let’s not reinvent the wheel - we can use already existing design systems as the inspiration/foundation for ours. We should find the best suitable ones and not reinvent the wheel.

.

  • No labels