馃幆 Improve alerting experience when incorrect file names don't allow for replacing designs, or rethink the experience entirely
馃攷 Insight
Currently we don't allow users to replace a design if it doesn't have the same file name. We also only display an alert banner after a user has tried to replace a design with a design of a different file name. This doesn't prevent users from making an error, and could cause users to mistakenly think their designs are updating when they aren't (as one of our participants did).
Because I didn't want to override the file. I wanted to create a copy.
I have the export of the same file name. I've just happened to have picked this up after using this before I know the need the same file name in order to write the same one.
I think, updating versus replacing. So I made a mistake there
Current banner experience:
Proposal
- MVC: Make the alert more contextual to the design. Locate the design management related alerts in-page within the design management area instead of using page-level placement. #299928[Design_management_update.png]
- Investigate if there are any bugs here. Currently, updating a design seems to fail even if it has the same file name.
Resources
Edited by Alexis Ginsberg