4 ms·

Frontend developers really like their designers to have versions, because it handles the eternal: Designer: Hey, I filed a bug for this, it doesn't look like t

Frontend developers really like their designers to have versions, because it handles the eternal: Designer: Hey, I filed a bug for this, it doesn't look like the design. <screenshot of design they changed yesterday> Developer: Um, we released that like two weeks ago; it's correct according to the design I had at the time. Designer: Yeah, but this is the design <link to continuously updated document in web editor with no history> Maybe you can just fix it really quick today? Doesn't have to be git, but some way to match up releases to the design document that was current at that time is quite useful.

u801e 5y ago
A timestamp would be sufficient in that case. If you think of most editors and word processors, they have undo and redo features that allow users to go back and forth in terms of the history of their edits. Those features normally don't support branches and if you make a change in the middle of a redo, you lose access the rest of the other redo steps. So you could tell the designer that you have the version they sent you on Friday August 13, 2021 at 3:12 PM EDT. Did they make any changes after that, or did they mean to send you a version they made prior to that?