genericlady / learnathon Goto Github PK

Mailgun isn't that great. Trying out Sparkpost instead.

-[x] workshop submission
-[x] sponsor submission
-[x] add email to newsletter

dependencies
-[x] Mailgun

send all data to [email protected]

I decided to use Mailgun because it's in the Docs for Sending email for Phoenix. Might as well give it a try.

wip-form-submissions merged

People should have to confirm their account.
Use bamboo to preview and test your mailers.

• https://github.com/thoughtbot/bamboo
• test
• preview
• create template for confirming email
• create template for success of confirmation and a thank you.
  interactively rebased with merge-base to first commit

Email confirmation functionality

• create a table for confirmation codes using email as index and body to hold the generated key
• confirmation code should expire at 15 minutes
• add tests
• add attribute to person of confirmed for boolean

Controller

• create an action for confirming a submission. maybe use submission#update and stick to basic phoenix conventions.
• add tests

Mailer

• use the submission_update_path and confirmation_code body to add functionality to the link inside of the message body of a confirmation email. (make a separate branch for this)

wip-email-confirmation
add-confirmation-code-to-mailer

• Donation
• Swag
• Prizes

Branch In Progress

wip-add-sponsor-attributes-to-person merged

• fonts aren't being moved to priv on deployment
• Some areas on lower third of site are not mobile first
• • live-streaming mobile first
• • stay-up-to-date
• Subject line needed for submission confirmation emails.
• Compress photos to < 1mb
• move html blocks to partials
• Add photos of venue
• Add background image of west side highway at night to stay up to date block
• Add awesome linter elixir_linter (commented it out, works too well)

wip-refactor-then-ship merged

It's made from the best stuff on Earth. Go ahead and remove any default css and js that phoenix generates and use the good stuff.

WIP: add-bootstrap4-marketing-theme

Avoid the idea of Models like in Rails. All that a person.ex would be is a data structure that is a schema. It's just the structure for which you want data to adhere to not a namespace to store behavior.

DataManagers SubmissionManager are a great place to store changesets, behavior of all kind including behavior that performs CRUD operations. The debate should a single context of one type of manager be allowed to manage two data structures? Sort of like a universal remote control?

With these new entities refactor the controller.

Points to go over

• Modules don't maintain state.
• Possible function entanglement? (the compiler will probably warn us)