Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create folder fro Email templates #118

Open
jacebenson opened this issue Jan 22, 2022 · 3 comments
Open

Create folder fro Email templates #118

jacebenson opened this issue Jan 22, 2022 · 3 comments

Comments

@jacebenson
Copy link
Contributor

Email should use brand from the site settings.
Keep in mind that someday multiple brands might be at play here.

@jacebenson
Copy link
Contributor Author

jacebenson commented Jan 22, 2022

Create a folder ./api/emails for email messages. Messages should contain a string template, and some incomfing variables e.g. sender, recipient, send-to, brand,
Create a folder ./api/brands for branding. Brands should contain the wrapping html for messages, and their color shceme, text, etc.
Create a build task to copy ./api/src/brands/default.js to ./web/src/brand.js and import it into ./web/src/App.js for use on Chakra Provider.
Add ./web/src/brands/* to .gitignore

@jacebenson
Copy link
Contributor Author

jacebenson commented Jan 23, 2022

Created ./api/emails
Created a testEmails function to test this. This should probably be disabled, but it can render the "template" for the one email until then here. https://demo.tskr.io/.netlify/functions/testEmail

  • Typos
  • Tskr is a pet project to alloy you and anyone to own their work, from the database to the front end at the best possible value. It has a few guiding principals.

  • Becomes
  • Tskr is a pet project to allow you and anyone to own their work, from the database to the front end at the best possible value. It has a few guiding principals.

  • Learn how it works here (video) needs to be updated to point to a video. (depends on Create a video - for the about page and take a screenshot to replace the unsplash image on about component. #120)
    • should this be on the project, or on a hosting platform /shrug
  • Link to the contributors on github and remove "permission" question from about me.
  • fix typo on "technoligies" to "technologies"
  • Link to github issues should be to a new github issue, not the list.

This doesn't help the idea of "brands".
A brands folder still needs to be created or included in ./api/src/emails/
brands will likely just be literal strings built from data on the web-side.

Next actions.

  • Correct typos
  • Move other emails to use MJML
  • create brand folder/files
  • Update emails to import brand details
  • Update the docs

@jacebenson
Copy link
Contributor Author

Updated the "forgot password" email but failed at the subject... update the subject future self.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant