🖼📋 Pair Hour Thread - Epic 1 Onboarding flow (Encrypting Data at Rest)

[manishapriya94]

User Story:

The next 12 weeks we're focusing on an Epic (set of features) which makes it easier for any climate based issue to self serve and onboard to the Amplify Platform. In order to meet compliance, HIPAA requires that things be encrypted at rest as information is stored so we will be updating API ecosystem and database (PostgreSQL) to meet these requirements.

Navigating Project Board and Resources

This project board will be most up to date for each task.

• Onboarding: these tasks will take you week 1-3
• Ramping: these tasks will take you week 4-6
• Finalizing: theses tasks will take you week 7-10

Below are the batches (features that are sets of tasks) and big picture of functionality criteria to meet and resources.

What is the workflow we're optimizing?

• Today climate groups will fill out this form
• Devs take this and put it into our database instance
• Lob holds the campaign information such as
  • contents of Letter
  • User constituent engagement (who sent what and when)

Batches
a. Update data models for Climate groups
b. Update data models for Constituents
b. Lob cardinality: Encrypting contents of letter
e. Feature Flags

Before each pair hour

Each week we will have a thread where you can drop your questions for your pair hour mentor (week 0 is an example). You will break down tasks with your pair mentor in the issue.

[manishapriya94]

Week 0:
QA:
Frontend:
Backend

Please prepare questions

cc: pair hour mentors and fellows

[manishapriya94]

QA:

• what data do I need to mock?
• best practices for jest?

Here's my issue to direct feedback

[manishapriya94]

Week 1: Documentation