---
# System prepended metadata

title: Card scenario (September)
tags: [pitch]

---

---
robots: noindex, nofollow
tags: pitch
---

# Card scenario (September)

### 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`.

### Appetite

The project should take 2-3 weeks.

### Solution

The solution is to build a converged component for `Text` and `Link` and to finish the implementation of a converged component for `Avatar` based on the design specs provided and accounting for the needs of both v0 and v7.

Part of this solution should also entail moving forward with the base `Card` component and finishing the final touches of the `Button` component, which is expected to ship in v8.

### 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. A stretch goal here would be to start creating these templates as examples but it is left as out of the solution for the moment because there are more pressing action items that have to do with the v8 release.

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.