Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

June 2017 Hackathon: Encourage Block Adopters to Log Cleanups #64

Open
tjnicolaides opened this issue Jun 13, 2017 · 0 comments
Open

June 2017 Hackathon: Encourage Block Adopters to Log Cleanups #64

tjnicolaides opened this issue Jun 13, 2017 · 0 comments

Comments

@tjnicolaides
Copy link
Contributor

screen shot 2017-06-13 at 10 33 25 am

Pictured above: a logged-in user who has adopted some blocks near 13th and Sansom.

Issue

For the users who have adopted blocks, the NotInPhilly admin team has only social media available to view evidence of litter pickup and to encourage active participation. See the "Social media" tab:

screen shot 2017-06-13 at 10 38 20 am

Goal

Add in-app features that allow admins to track participation and encourage consistent litter cleanup participation among block adopters.

Ideas

  • Add a feature where users can schedule and/or log cleanup events. Fields could include a datepicker, a dropdown where between 1 and all of the user's adopted blocks can be added to the cleanup event, and a checkbox to indicate complete status
  • Automatically email users to remind them of an upcoming cleanup event (similar to automated email reminder system from June 2017 Hackathon: Drive Block Adoption Among Registered Users #63)
  • Automatically email users to ask them if a recently passed cleanup event was completed
  • Automatically email users if they haven't scheduled or logged a cleanup event in X number of weeks

Current Workflow

N/A

Please use this issue thread to add ideas and develop solutions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant