# Fluent Cards

#### Goal: Deliver a common Card control and its primitives (Button, Image, Avatar, Text, Icon) built using the new compose architecture model with tokens ingested.

(These are rough dates - not deadlines/prescribed schedule. The point of this doc is to simply figure out the order in which we build these converged controls & so we can tell Design when we need each spec by. Also helps raise questions around resourcing & consumption plan.)

* Office.com ready to consume as soon as we finish: end of Aug possibly
* Ignite is in Sept 2020 but there are no concrete plans as of August 5th for sessions/etc where this work is being shown
* Consume from react-foo package. V7 has experimental card so less replacing. TBD: current card in uifabric domain space.
* TODO for Aneesha: confirm consumption plan with Office. are they showing any of these surfaces at Ignite?
* Teams features consume in Q4
* TODO for Aneesha: define process: design spec -> built -> vet in products: at least Office and Teams -> proven it's converged -> what happens to react-foo package.
* Definition & agreement on stages -> work with Justin & engineers to figure out who's doing XYZ resourcing/timeline. Same as for design tokens: spreadsheet matrix.
* concerns: product teams depending too much on us.
* each of the react-foo packages reexported in react-northstar:
* put button into react-northstar, help Teams update all their buttons -> parallelize: base Card component can be vetted along with primitives and once those are done, fuller Card scenarios can be made.
* differences in components: individual plan to replace each one in northstar - our engineers go into products & validate each control.
* A converged component is one that works in multiple products - test like what's being done in Ribbon & styling in Teams.
* Requirement for each converged package: ship criteria - we can hoist things into react-next as its being validated.
* Is button ready? menubutton & splitbutton go in same package as menu.
* because it takes over a month to upgrade Fluent version - we might consider going into their code & updating to use new stuff
* Q3 Teams feature Cards is needed in Calls app but it needs to be out by Sept so they can't consume before.
* OWA & Word don't seem to have Card scenarios, at least in this [Figma walkthrough](https://www.figma.com/proto/lvcCLRv2XnVRRKHj1L8uqp/Week-5---Consolidation?node-id=195%3A84048&scaling=min-zoom) of what's expected by Ignite

react-foo packages: end of September. Milestone driven - proven in Office, Teams rather than finished.
* Link possibly too
* Tooltip
* Badge/Status - presence
* common Card (as templates in react-cards package)
* Design spec ready for implementation
* react-card package merged into master
* Icon (TBD: complications? Check with David & Paul)
* Design spec ready for implementation
* react-icon package merged into master
* Text - September
* Design spec ready for implementation
* react-text package merged into master
* Avatar - August
* Design spec ready for implementation
* [Entity Layout spec](https://www.figma.com/file/CxKjrhFAX9R5spusiKrePj/Entity-Layout?node-id=47%3A0)
* react-avatar package merged into master
* primitive Card
* [Design spec](https://www.figma.com/file/berhUBA6mJV9sCPpjgfKRj/Card) ready for implementation
* react-card package merged into master
* [Design spec](https://www.figma.com/file/05wt6TAsEmgsCVZfPrpcWx/Image) ready for implementation
* react-image package merged into master on: week of July 27th
* Button - Mak
* [Design spec](https://www.figma.com/file/Nj9EBBvOZmS11zKNJfilVR/Buttons) ready for implementation
* [Button in react-button package](https://github.com/microsoft/fluentui/pull/13769) merged into master
* [MenuButton in react-button package](https://github.com/microsoft/fluentui/pull/13812) merged into master
* SplitButton in react-button package merged into master on: week of July 27th

Consumption:
- Teams: individual packages (react-cards, react-button, etc) get deployed to react-northstar which Teams consumes from
- Office Online: from master