Simplify Deletion Flow For Entities And Submissions
Introduction
In the world of data management, deletion is a crucial aspect of maintaining data integrity. However, the current deletion flow for entities and submissions in Central can be improved to provide a more user-friendly experience. This article proposes a simplified deletion flow that includes a confirmation toast message, undo functionality, and a clear indication of deleted entities' fate.
Current Deletion Flow
The current deletion flow in Central involves a straightforward process of deleting an entity or submission. However, this process lacks a crucial aspect of user experience: confirmation and undo functionality. When a user deletes an entity or submission, there is no clear indication of what happens next, leaving the user uncertain about the fate of their data.
Proposed Deletion Flow
To address this issue, we propose a simplified deletion flow that includes the following features:
Confirmation Toast Message
When a user deletes an entity or submission, a confirmation toast message should appear, asking the user if they are sure they want to delete the entity or submission. This message should include an action to undo the deletion.
Undo Functionality
If the user clicks the undo button, the entity or submission should be restored to its original state. This ensures that users have a chance to recover their deleted data.
Deleted Page
On the deleted page, a line of copy should be added to inform users that deleted entities will be purged after 30 days. This provides clarity on the fate of deleted data and helps users understand the consequences of their actions.
Restoration Confirmation
When a user restores an entity or submission, a confirmation toast message should appear, ensuring that the user is aware of the action they are taking.
Benefits of the Proposed Deletion Flow
The proposed deletion flow offers several benefits, including:
- Improved User Experience: The confirmation toast message and undo functionality provide a more user-friendly experience, reducing the risk of accidental deletions.
- Increased Data Integrity: The clear indication of deleted entities' fate helps users understand the consequences of their actions, reducing the risk of data loss.
- Enhanced Transparency: The confirmation toast message and deleted page copy provide transparency into the deletion process, helping users make informed decisions.
Design Considerations
To implement the proposed deletion flow, the following design considerations should be taken into account:
- Visual Design: The confirmation toast message and deleted page copy should be designed to be visually appealing and easy to understand.
- Accessibility: The deletion flow should be accessible to users with disabilities, ensuring that all users can navigate the process easily.
- Consistency: The deletion flow should be consistent with the overall design of Central, ensuring a cohesive user experience.
Implementation
To implement the proposed deletion flow, the following steps should be taken:
- Design the Confirmation Toast Message: Design a visually appealing confirmation toast message that includes an action to undo the deletion.
- Implement Undo Functionality: Implement the undo functionality, ensuring that the entity or submission is restored to its original state when the undo button is clicked.
- Add Deleted Page Copy: Add a line of copy to the deleted page to inform users that deleted entities will be purged after 30 days.
- Implement Restoration Confirmation: Implement a confirmation toast message when a user restores an entity or submission.
Conclusion
The proposed deletion flow for entities and submissions in Central offers several benefits, including improved user experience, increased data integrity, and enhanced transparency. By implementing the proposed deletion flow, Central can provide a more user-friendly experience for its users, reducing the risk of accidental deletions and data loss.
Future Work
Future work should focus on refining the proposed deletion flow, ensuring that it meets the needs of Central's users. This may involve:
- User Testing: Conduct user testing to ensure that the proposed deletion flow is user-friendly and meets the needs of Central's users.
- Feedback Mechanism: Implement a feedback mechanism to gather user feedback on the proposed deletion flow, ensuring that it is refined to meet the needs of Central's users.
Related Issues
This proposal is related to the following issues on GitHub:
Design File
The design file for this proposal can be found on Figma:
- https://www.figma.com/design/ULpCuTKkIys6Y99YGyMcrF/Central?node-id=298-469&t=ahjLYxhqPjsf4tEk-1
Simplify Deletion Flow for Entities and Submissions: Q&A =====================================================
Introduction
In our previous article, we proposed a simplified deletion flow for entities and submissions in Central. This article provides a Q&A section to address common questions and concerns related to the proposed deletion flow.
Q: What is the purpose of the confirmation toast message?
A: The confirmation toast message is designed to provide a clear indication of what will happen when an entity or submission is deleted. It also includes an action to undo the deletion, giving users a chance to recover their deleted data.
Q: How does the undo functionality work?
A: When a user clicks the undo button, the entity or submission is restored to its original state. This ensures that users have a chance to recover their deleted data.
Q: What happens to deleted entities after 30 days?
A: Deleted entities will be purged after 30 days. This is indicated on the deleted page, providing clarity on the fate of deleted data.
Q: Why is the restoration confirmation necessary?
A: The restoration confirmation is necessary to ensure that users are aware of the action they are taking when restoring an entity or submission.
Q: How will the proposed deletion flow affect user experience?
A: The proposed deletion flow will improve user experience by providing a more user-friendly experience, reducing the risk of accidental deletions, and increasing data integrity.
Q: What design considerations should be taken into account when implementing the proposed deletion flow?
A: The following design considerations should be taken into account:
- Visual Design: The confirmation toast message and deleted page copy should be designed to be visually appealing and easy to understand.
- Accessibility: The deletion flow should be accessible to users with disabilities, ensuring that all users can navigate the process easily.
- Consistency: The deletion flow should be consistent with the overall design of Central, ensuring a cohesive user experience.
Q: How will the proposed deletion flow be implemented?
A: The proposed deletion flow will be implemented through the following steps:
- Design the Confirmation Toast Message: Design a visually appealing confirmation toast message that includes an action to undo the deletion.
- Implement Undo Functionality: Implement the undo functionality, ensuring that the entity or submission is restored to its original state when the undo button is clicked.
- Add Deleted Page Copy: Add a line of copy to the deleted page to inform users that deleted entities will be purged after 30 days.
- Implement Restoration Confirmation: Implement a confirmation toast message when a user restores an entity or submission.
Q: What is the timeline for implementing the proposed deletion flow?
A: The timeline for implementing the proposed deletion flow will depend on the resources available and the priority of the project. However, we aim to implement the proposed deletion flow within the next 6-8 weeks.
Q: How will the proposed deletion flow be tested?
A: The proposed deletion flow will be tested through user testing and feedback mechanisms to ensure that it meets the needs of Central's users.
Q: What is the next step in implementing the proposed deletion flow?
A: The next step in implementing the proposed deletion flow is to design the confirmation toast message and implement the undo functionality.
Conclusion
The proposed deletion flow for entities and submissions in Central offers several benefits, including improved user experience, increased data integrity, and enhanced transparency. By implementing the proposed deletion flow, Central can provide a more user-friendly experience for its users, reducing the risk of accidental deletions and data loss.
Related Issues
This proposal is related to the following issues on GitHub:
Design File
The design file for this proposal can be found on Figma: