Change Details

==== Background/Goal At 2022-06-07 DST task refinement, we decided to prioritize scoping an MVP for the Card Codex component since it is needed for us to deprecate WVUI (task?). The existing Card component task (T256036) is ~2 years old and contains a lot of back-and-forth, so it's worth considering whether to update T256036 or create a new task. ===== User stories As a contributor interested in the Card Codex component, I want to understand what the scope looks like for an MVP version of this component, so that I can more effectively plan and communicate about our work. ===== Considerations - We could potentially use this as an opportunity to test our new component epic template (T309417). - Could we identify one DST engineer and one DST designer to be directly responsible individuals (DRIs) for 1) ensuring this component is moving along, surfacing risks, etc, and 2) serve as points of contact for our partner teams? ===== Development considerations [to come] ===== Acceptance criteria [] MVP scope is defined for Card component in Codex [] Epic task is created (or T256036 is updated) ===== Open questions [to come]

==== Background/Goal At 2022-06-07 DST task refinement, we decided to prioritize scoping an MVP for the Card Codex component since it is needed for us to deprecate WVUI (task?). The existing Card component task (T256036) is ~2 years old and contains a lot of back-and-forth, so it's worth considering whether to update T256036 or create a new task. ===== User stories As a contributor interested in the Card Codex component, I want to understand what the scope looks like for an MVP version of this component, so that I can more effectively plan and communicate about our work. ===== Considerations - We could potentially use this as an opportunity to test our new component epic template (T309417). - Could we identify one DST engineer and one DST designer to be directly responsible individuals (DRIs) for 1) ensuring this component is moving along, surfacing risks, etc, and 2) serve as points of contact for our partner teams? ===== Development considerations [to come] ===== Acceptance criteria [] MVP scope is defined for Card component in Codex [x] Epic task is created (or T256036 is updated) ===== Open questions [to come]

==== Background/Goal At 2022-06-07 DST task refinement, we decided to prioritize scoping an MVP for the Card Codex component since it is needed for us to deprecate WVUI (task?). The existing Card component task (T256036) is ~2 years old and contains a lot of back-and-forth, so it's worth considering whether to update T256036 or create a new task. ===== User stories As a contributor interested in the Card Codex component, I want to understand what the scope looks like for an MVP version of this component, so that I can more effectively plan and communicate about our work. ===== Considerations - We could potentially use this as an opportunity to test our new component epic template (T309417). - Could we identify one DST engineer and one DST designer to be directly responsible individuals (DRIs) for 1) ensuring this component is moving along, surfacing risks, etc, and 2) serve as points of contact for our partner teams? ===== Development considerations [to come] ===== Acceptance criteria [] MVP scope is defined for Card component in Codex [x] Epic task is created (or T256036 is updated) ===== Open questions [to come]