The editor above holds two roles in one window. As the designer, edit the card and send it as a proof. As the customer, click an element, comment on it, and approve the proof or ask for changes. Back as the designer, the comments show as numbered pins on the card, and the next proof becomes the next version.
How it's built
- Versions: each proof is the design JSON, a thumbnail and a status: waiting, approved or changes requested.
- Review without editing: the customer sees the same editor without the side panel, toolbar and hotkeys, and every element locked with element locking, so they can select an element but not edit it.
- Comments: a comment belongs to an element. Its pin is an element too, marked not to export and removed before a version is saved.
Adapting it to your product
- Your server: the demo keeps versions in memory, so a reload starts over. Store them with your orders and send the customer a link to the proof.
- Your rules: require approval before an order goes to print, or ask for a second approver above an order size.
- Your audit trail: keep who approved which version and when, next to the exact JSON that was printed.
For the pipeline behind proofs in variable data printing, read proofing and approvals in web-to-print.
