Following our technical conversation on how we can best prepare for Project Darwin, we said that we would look at the new designs and annotate them to agree on scope, definitions and clarify terminology for components.
Why
We want to understand:
• What existing components do we have already
• What changes might we need to make to elements to support new designs
• What changes might we want to make to the new design to make the best use of elements
• Accessibility considerations
Done when
[x] We have deconstructed new components and / or new configurations to existing components
[x] We have agreed on any changes to elements to support the new designs
[x] We have reviewed the any new changes or components with the accessibility team
Taking examples from the darwin design proposals, we will deconstruct the designs in order to understand how to modify or create new components that can work at scale.
What
Following our technical conversation on how we can best prepare for Project Darwin, we said that we would look at the new designs and annotate them to agree on scope, definitions and clarify terminology for components.
Why
We want to understand:
• What existing components do we have already • What changes might we need to make to elements to support new designs • What changes might we want to make to the new design to make the best use of elements • Accessibility considerations
Done when
Anything else
Rolling docs for Oscar + Elements teams: https://docs.google.com/document/d/13Fzfk0nUygJCmG5bcQPI2kSw95i5tIjDoySUGtxcszM/edit
Design review: https://miro.com/app/board/uXjVPvH2H9M=/
Component definition https://docs.google.com/document/d/1K6TIKK05XpWUN8u-UMwUevg6zoUDg147ZkuZyizLZIo/edit#heading=h.z0syvbcrqr89