Challenge Overview
This is another challenge in the series for Cloud Hub, where we want to add some email alert jobs to our API project. These APIs are a series of endpoints built using swagger, nodeJS and mongodb. Right now we are using AWS Elastic Beanstalk for our job scheduler. We plan to add multiple emails and want to make sure this setup takes a long term view, even though we are only building 1 alert now. Right now we have an existing job for creating an event for a pending renewal and we want to send all admin users an alert when that happens.
Requirements
1. Build HTML for email using provided PNG design. Email layout should be responsive for multiple screen sizes.
2. Trigger email send to any admin user for company inside of jobService.renewCompanyApps.
3. Send email using sendgrid API.
4. Submission should show email layout in common browser and iPhone sizes.
2. Provide your code and documentation in a single zip file. Please include a git patch for easier integration of changes.
3. The bulk of your documentation should be in the Readme.md and you should assume that this will be open source so make sure you cover all the steps to set up, If you have specific information that should not be included in a public readme (like links to your video) put them in a file called submission.txt and they will be omitted from the project if it is open sourced.
4. Provide a quick video of your solution in action (feel free to annotate your video if you are not comfortable with spoken English or don’t like the sound of your own voice). Video may be private on youtube or added to the submission files.
Requirements
1. Build HTML for email using provided PNG design. Email layout should be responsive for multiple screen sizes.
2. Trigger email send to any admin user for company inside of jobService.renewCompanyApps.
3. Send email using sendgrid API.
4. Submission should show email layout in common browser and iPhone sizes.
Final Submission Guidelines
1. Any additions or modifications to the code project pass on "npm run lint" and "npm run test".2. Provide your code and documentation in a single zip file. Please include a git patch for easier integration of changes.
3. The bulk of your documentation should be in the Readme.md and you should assume that this will be open source so make sure you cover all the steps to set up, If you have specific information that should not be included in a public readme (like links to your video) put them in a file called submission.txt and they will be omitted from the project if it is open sourced.
4. Provide a quick video of your solution in action (feel free to annotate your video if you are not comfortable with spoken English or don’t like the sound of your own voice). Video may be private on youtube or added to the submission files.