| ppelberg | |
| May 22 2024, 11:12 PM |
| F54167974: image.png | |
| May 22 2024, 11:12 PM |
Notes to future self: this task was borne out of editing team's 22 may team discussion wherein we decided design + eng to work together to define: 1) what initial component will be 2) what they will each do/mean and 3) how they will interact so that we can "compose" new checks with them, and ultimately, become more clear about the multi-check UX (T347530).
| Name | Description | Mobile | Desktop | Notes |
|---|---|---|---|---|
This work is happening in the Edit Check – UI System (WIP) deck.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T265163 Create a system to encode best practices into editing experiences | |||
| Open | None | T345472 Offer Edit Check(s) within new article creation | |||
| Open | None | T366743 Enable multiple Edit Checks to be presented within a single edit | |||
| Open | None | T360799 [EPIC] Empower developers to author new Edit Checks and Structured Tasks | |||
| Open | None | T364505 Develop a design framework that empowers people to author new Edit Checks and Structured Tasks | |||
| Open | nayoub | T365660 Define initial set of Edit Check UI components |
Next step: per today's team meeting, @nayoub is going to update this ticket with the base set of components we converged on and then resolve.
Next steps
@nayoub to...