--- robots: noindex, nofollow tags: pitch --- # Card scenario (August) ### Problem We have scenarios in multiple products including Office.com and Teams that require the use of a `Card` component as part of the product experience. These scenarios also include the use of a variety of other componets to be hosted inside the `Card`. These include both the `Avatar` and the `Image` components. ### Appetite The project should take 3-4 weeks to come up with something close to what we're targeting in the design specs: - [Avatar](https://www.figma.com/file/3SlxyaJA3tpLs5rVZ4oTVj/Avatar?node-id=0%3A1) - [Image](https://www.figma.com/file/05wt6TAsEmgsCVZfPrpcWx/Image?node-id=1%3A1802) ### Solution The solution is to build converged components for the `Avatar` and `Image` based on the design specs outlined above and accounting for the needs of both v0 and v7. ### Risks (Rabbit holes) We're iterating quickly on our technology stack so we should make sure we're using the latest patterns and try to close on things quickly so PRs are not stuck on conflict-land. There is also a risk of building this component in isolation, both from the standpoint of Engineering without Design/PM input and from the standpoint of not thinking about the component as something that's going to be consumed in real-world applications. As said before, we should strive for constant back-and-forth between teams while always keeping in mind how this will be integrated in product. ### Out of scope (No-gos) While the end-goal is to have these components hosted inside a `Card` this iteration will focus on the individual components, with the integration coming later on. Creating higher value templates is the end goal of this project. However, we don't want to create, export and own these templates because it could get overwhelming really fast. We'll use these scenarios to influence the project direction and, at most, base the examples we create on them. There is a need to keep in mind how the product is going to be integrated into real-world application experiences, however, for the sake of this project the integration into an actual product should be a stretch goal given the shorter time we have for this project with holidays early in the month and the OneWeek Hackathon at the end of it.