yurykorzun / notinphilly Goto Github PK

We need to implement a simple admin dashboard that will have a number of grids, such as user list, event list and so on. Only users in Admin role should be able to view and edit them. Currently a stub for the admin page is implemented but not finished.

We need to figure out a way to backup, make changes without loosing existing data and migrate database to a different server.

A fine suggestion from Ben Novack. From a UX perspective, there's an intuition to tap outside of the sidebar to close it, as would happen in a native app.

I think the best way to tackle this might be to use a touch event on the leaflet directive. Additionally, this library might help create a more native feel on mobile: https://github.com/ftlabs/fastclick

By making the intersection itself not part of the clickable area, it makes it more obvious that the streets are clickable. Also, it may be good to think about a slightly different color, like light blue or yellow, instead of gray.

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:

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 #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!

If a user zooms in with either the zoom tool or by scrolling, the map view should change from neighborhood to street after a certain zoom factor.

Pictured above: a logged-in user who has yet to select any Philly streets from the map feature to clean up.

Issue

The NotInPhilly.org membership database has a significant group of users who have yet to adopt a block and become active cleanup participants. A streamlined signup process from #62 is likely to generate more "inactive" participants.

Goal

Find ways of reaching out to registered users who have yet to adopt a block, and encourage them to become active participants.

Ideas

• Add a link to the maps feature to the welcome email
• Increase the prominence / frequency of on-screen CTAs for users who aren't currently participating in any streets
• Develop an automated email reminder system for registered users who have zero blocks to log in and make their selections in the map feature. Is a weekly reminder sufficient?
• Add ability for admins to manually select blocks for members
• Auto-suggest or auto-add blocks for new members - e.g. if the block where their home address is unclaimed during the signup process

Current Workflow

1. Users who complete registration receive a welcome email (see below) - but it doesn't include a link back to the site's map feature where they can adopt a block
2. Users who log in see a small prompt to find streets to adopt on their profile page.

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

The streets view has issues with Chrome and Safari in iOS and Chrome on Android.

• Difficulties scrolling around on iOS
• Selecting individual streets is broken; if the popup appears, it's offset from the clicked location
• bugs with tooltip hover not exiting

API: https://developers.google.com/maps/documentation/geocoding/intro

Use browser geolocation as well?
https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/Using_geolocation

Link with instagram

An "x" option in the upper right should be added when a block is selected if one wishes to close the window.

Pictured above: the Not In Philly signup screen for new users. Users can sign up with Facebook in order to auto-fill some of these fields.

Goal

Increase registration of new accounts by visitors to NotInPhilly.org.

Ideas

• Split up the signup form so that Step 1 only requires minimal information to create an account: email, password, and maybe first/last name. Users would then be encouraged to "complete their profile" by filling in the rest of the information that's required on the current registration form and adopting blocks.
• Make the prompt for new account registration more prominent in the menu / hero areas

Current Workflow

1. Navigate to http://notinphilly.org/
2. Select "Sign Up / Log In"
3. Select the "Sign Me Up" button
4. In the modal window that appears, fill in all required fields (including street address validation via Google API) and select "Register Now"
5. Receive a welcome message in your email inbox (see below)
6. Log in to your Profile page

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

Numbered streets, as well as any street that uses N/S/E/W is difficult or impossible to enter using the current format.

Include test launch info

STR:

1. Navigate to http://notinphilly.org/
2. Click "Sign Up / Log In" and then choose "Sign Me Up" button. The registration modal appears.
3. Fill out the information for a new user. Choose a home address from outside the City of Philadelphia (example: 6 Station Rd, Ardmore, PA 19003).
4. Click "Register Now"

Result: registration modal hangs. No error is displayed to the user. API call to /api/users/ endpoint hangs and then times out.

Locally, the node server console displays an error:

(node:99009) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: Cannot read property '_id' of null