Closed ericerway closed 5 years ago
Blocking till the moment we decide which solution is acceptable from the technical perspective by @zetlen
@ericerway , @zetlen, @awilcoxa Probably we need a find a solution as a 1st step
For now, email templates should be implemented manually using the same original assets used to build the PWA. We need to talk about what kind of email workflow is acceptable; Magento frontend developers who maintain local instances can edit email templates directly, but if you're working from a remote instance in our new workflow, the story is less clear. Adding labels to indicate that further discussion is required.
This issue is for the following packages:
[X]
venia-concept
[ ]pwa-buildpack
[ ]peregrine
[ ]pwa-module
[ ]pwa-devdocs
Description
As a shopper, I want a Venia branded email for password reset and subscriptions so that I can trust that it's coming from a trusted source.
Assumptions
Tasks
[ ] Find and replace LUMA artwork and text/copy instances with Venia (Magento 2) [ ] Review and update links to password, account and others with Venia storefront [ ] Testing and documentation (https://github.com/magento-research/pwa-studio/wiki/Documentation-Guidelines)