In coming to an agreement to change how the sidebar behaves for Edit Checks while people are editing [i], we are needing to reassess how Edit Checks are presented to people in the "Pre-Publish" moment and ultimately, define what that user experience will be.
Decision(s) to be made
- 1. How will we present Edit Check in the Pre-Save moment?
| Approach #1 | Present Checks in a static location, people can navigate between Checks by tapping ← / →, document scrolls in response | Current approach | |
Requirements
- Implement Approach #1
- Implement underlying sidebar infrastructure that will enable Approach #1
Approaches
| Approach | Description | Screenshot/demo | Notes |
|---|---|---|---|
| Approach #1 | Present Checks in a static location, people can navigate between Checks by tapping ← / →, document scrolls in response | Current approach | |
| Approach #1a | Present Checks in a static location, people can navigate between Checks by tapping ↑ / ↓, document scrolls in response | Slight deviation on "Current approach" | |
| Approach #2 | Present Checks in variable locations, depending on where in the document the content they are relevant to exists | TBD how navigation between Checks would work in this model | |
i. (to a more "Google docs like") I don't think we consider the implication on post-save check. We have two options: