Have base template, have sub_base templates for each section, for instance navbar could be different or not there at all on certain sections.

• Make Comment model with reference to a task, created_by, created/updated_at dates
• On Task Details display all comments in order below task
• At the bottom, include the comment creation form, which will link to the createComment view
• createComment view, on success, redirects back to task details

Clicking on a form submit button multiple times will call multiple form submits.

Already exists, just need to add edit functionality.

Account page with User details:

• Members -> link to specific member details page
• Link to list view of all tasks from all bands
• Username
• Email
• Reset password

• Instead of text, all image_url sections of forms should be dropdown of preset images
• Images are stored in S3 bucket, just plain colors or something
• Instead of url, image is displayed everywhere that image_url is used

• On User detail page (not member, members don't have emails) option to turn on notifications, which subscribes email to SNS topic

By default, SNS offers 10 million subscriptions per topic, and 100,000 topics per account.
https://aws.amazon.com/sns/faqs/

• Maybe topic created for user when notifications turned on
• If task of one of its members is made or commented on notify user
  • Assuming an endpoint used, it is ideally in user, but can be in member if user is too hard to change

This problem has already been solved, and others have done this before. See how they do it before continuing this one.