todo.txt

* User heirarchy
    - User
        - Comentar en articulos
        - Ver los eventos
        - Ver replays de eventos pasados
    - Miembro
        - Asistir a los eventos (entrevistas, etc)
    - Lideres
        - Crear articulos
        - Crear eventos/entrevistas
    - Admin
        - Mandar correos masivos
        - Borrar articulos/eventos/entrevistas
        - Ver informacion de Usuarios
        - Cambiar nivel de Usuarios
    - Dev
        - All permissions

*** SECURITY ***
1. Prevent <select> elements from sending unexpected information (validate information, maybe '.equals()')
2. Validate number fields as numbers (.isNumeric())
3. Prevent <select disabled> from modifying db info

==============================================
                MEDIA QUERIES
==============================================
Portrait:
  0px - Small Screens
  360px - MotoG4
  540px - Surface Duo
  768px - iPad
  1024px - iPad Pro

Landscape:
  0px - Small Screens
  640px - MotoG4
  653px - Galaxy Fold # ONLY OPENING LOGO MOD #
  720px - Surface Duo
  812px - iPhoneX
  1024px - iPad
  1366px - iPad Pro

Laptop:
  0px - 600px
  800px - 600px
  1200px - 600px
  1366px - 600px
  1600px - 900px


========================================
X. homepage 
X    - Change text for mailing list
X. Migrate to Atlas
1. Mails:
X    - contacto@mexicogira.com -> Contact for questions, etc. WorkMail: q@nVOX9#8M1b
    - eventos@mexicogira.com -> Notification for events, SES
X    - no-reply@mexicogira.com -> automated mail service, notifications, etc. SES
1. Registro a eventos
    - Mandar correo un dia antes a los registrados con link
    - Solo usuarios se pueden registrar

2. Download mailing list
2. Mailing list
    - Send mass emails

3. Noticias y articulos
    - Media upload
3. SEO
    - Google ads, etc.
    - Google analytics
3. Documentation

TOMORROW:
* FIX: User change email (production), does not change email in interface, causes error

#Registro a eventos#
X Add user array to event schema
X Add zoom link to event schema
* Add "occurred" attribute to event schema (or check if event has occurred in backend)
X Add event array to user schema
** Ask about zoom link visibility (website & email || only website || only email)
* Add conditional "Register"/"Attend" button to all events -> Prompt to user login || Register to user events & send email
* Create event email template (replyto: contacto@mexicogira.com)
* Function to send email 3 days before event automatically? (probably serverless lambda function or cognito) [can lead to solution for user deletion if not registered]

X Event name must be unique
*** Validate event name is unique before creating event
*** Validate user email in login
*** Send error message if wrong user email or password
*** User delete account
*** Recommend terms and conditions and privacy policy to team
*** Investigate on delete user after x days if not verified

============================
       Reference SES
============================
# SES #
https://beefree.io/editor/?template=empty (Email templater)
https://pandeysoni.medium.com/how-can-we-use-amazon-ses-template-to-send-email-in-node-js-fb162bd8152e (SES Bulk tutorial)
https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/ses-examples-sending-email.html (AWS SES NodeJS)
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-concepts-process.html (SES Email Concepts)
https://aws.amazon.com/blogs/messaging-and-targeting/introducing-email-templates-and-bulk-sending/ (AWS SES Bulk tutorial)
https://aritic.com/blog/aritic-mail/best-practices-to-handle-password-reset-emails/ (Password email reset good practices)