saiorama / ses-email-client Goto Github PK

Show subject and text version

Code changes made to lambda functions in github should be deployed to AWS.

Link to this github

Users should be able to retrieve emails for any prior date.

Users should be able to send test emails

Minimize touches
Minimize disruptions due to erroneous deployments

1. add one set of valid credentials
2. download all templates
3. change the used credentials

Expected: since the credentials have changed,

• the previously downloaded credentials should be removed
• Get Templates cta should be enabled

Allow users to see their send stats on the templates page

After clicking on template name, the template is loaded on screen but template name is never shown on screen. Users should be shown the name of the template currently being displayed.

Add ids to elements in the AWS Credentials modal

Back to ses v1 api

Old blog posts from zeer0.com should be ported over

Update the README file to reflect latest design.

1. Include newest screenshot of email client
2. Explain how email attachments are extracted from email, stored in S3, and returned to the user
3. Add link to beta page @ https://shared-inbox.landen.co/beta

should work for /email/templates AND /email/templates/ (without and with trailing forward slash)

It is slowing down page load and adding bloat.

Publish the utility which extract Mozilla Public Suffix List as a lambda utility

Replace Frontendor's logo and icon.

I'm sorry I have to do this...

If a domain does not have subdomains, use the domain name as the root prefix name
If it has subdomains, use the subdomains in reverse order as sub-prefix inside the root prefix by replacing . with /
Ignore port numbers in domain names

(Use Mozilla's Public Suffix List to solve the last requirement.)
--OR--
I've created an API to extract tld from a domain based on the PSL linked above.

Use the API so -
curl -H 'x-api-key: ' 'https://api.zeer0.com/v001/tools/public-suffix?domain=https://janata.in'

I'll send you the API key separately.

How is it useful?

The domain prefix is the last dot separated segment prior to the TLD. Therefore, for www.my-website.co.in, co.in is TLD, my-website is domain prefix, and www is the subdomain.

The root prefix will be my-website.co.in
The sub-prefix will be www.

How is this useful?
Once we move to this format, we can provide a cloud based shared inbox under a single domain to any user who does not already have web hosting. Say our cloud client is called shared-inbox.com. If a user wants to create a shared inbox on their personal domain - like my-domain.com - they can see their emails at com.my-domain.shared-inbox.com.

Right now, a user can either read the email using my-email/index.html or compose emails using the inline email editor. This means that the user can't read emails and reply to them from one window.

Show loader when user clicks on "Get my SES templates".
Show loader when user clicks on template name.

MOVE the following to ENV variables -

• domain vars
• redirect vars
• bucket names
• region names
• urls
• keys & tokens

Users should be able to supply a JSON object to see what the template looks like with actual data

This is super basic issue just to work out the kinks in the issue tracking and PR process.

1. The file needs to be renamed to include the .js extension without which GH's syntax highlighting doesn't seem to work.

Create a simple way to view SES Templates in the browser

The modal should cover more of the screen and minimize scroll bars

Deployment should happen as soon as you merge to master.

1. Add disclaimer to the templates page that this page not optimized for mobile.
2. Use modals to show templates on desktop and mobile

If the user is on mobile, add some text indicating that it the page will look awful on mobile.
The user should be able to use the templates page

1. Open the /templates in incognito
2. Click on Add AWS Credentials
3. Observe the modal

Expected: "Use Demo Keys" button should be enabled and clickable
Actual: "Use Demo Keys" button is not enabled or clickable