We need to migrate the blog section from the master branch to the new code base in the next branch using the generator-react-firebase file structure and conventions.

I am suggesting a restructuring of our project. This is only related to the src folder

Current:

• Src
  • components
    Holds the screens/pages
  • modules
    Holds the reducers & auth

Proposed:

• Src
  • components
    Holds reusable UI components
  • views
    Holds the screens/pages
  • store
    holds the redux store
  • modules
    holds other modules

I can do it and submit a pr by 10PM IST March 18.

Describe the bug

1. Create a new request without logging in.
2. The console sometimes logs an error about this line.

Please see details in the design document that I shared. I will update this issue with the details in a bit.

As we get ready for production release, we need a way to differentiate between production and dev configs. Maybe use NODE_ENV node var.

Using getterms.io for now.

Maaz is working on this.

We need to add cypress tests for the following:

1. Request acceptance
2. Request release
3. Request completion
4. Add admin comment on a request
5. Add private comment on a request

One of the immediate needs is to send out notification emails to volunteers for open requests. We are still analyzing the initial approach as part of #49, but our initial vision is to check every 5 hours and send a notification email to volunteers for open requests. The notification email will include the following sections.

1. Open requests near you: this section will include up to 15 open needs within a 60 mile radius, ordered by the distance from the individual volunteer.

2. Open requests farther away: this section will include up to 5 open needs that are farther away, ordered by the distance from the volunteer. The intention here is to request help with either finding more volunteers or organizations who might be able to assist.

3. Simple informational text about the upcoming feature to snooze or turn off these notification emails.

I have started the Firebase auth skeleton integration, and need someone to continue.

We need to convert the contact page to an actual React form. It should have the following fields and add to the contacts collections in Firebase.

1. Name
2. Email
3. Phone - optional
4. Organization - optional
5. Message

Furthermore, it should also email the administrators on submission. The project uses the Trigger Email extension so emailing requires adding a new document to the mail collection.

@prescottprue, can you please update this with the collection where you were suggesting saving the admin emails?

Please note that all new development is now being done on the next branch which will be going live in the coming days. Please branch off of it if working on this task.

See figma for the section. This will be a new section on the homepage.

The current login page is used as both a sign up and a login page. This can be confusing for new users. We need to break this up into two sections (or steps/pages), one for login and one for sign up. Ideally, the sign up page would account for the volunteer information as well.

We need to add the following additional menu entries to the main App Bar (see App.js). Please add the buttons and ensure responsiveness.

We need to allow the user to enter an address and then use Google Maps API to lookup the geolocation. Note that the ClickableMap component is used on request help and the sign up screens. On the sign up screen, we also need to fill in the discrete address fields, if possible.

The request page needs to require at least one need and immediacy value. We are using Formik and Yup for validation, and using FieldArray.

GET /needs?location=x,y&distance=number&units=mi|km

units can be "mi" (miles) or "km" (kilometers), default to "mi".

Returns an array of needs/requests.

Quick stats
Attach Flyer and request handing it out - Steve Knurr might be working on this already
Mention improvements
Explain the upcoming notification improvements

Now that we pushed out the next branch live, we need to make the firestore rules more secure.

API implementation https://github.com/CV19Assist/app/blob/master/functions/handlers/needs.js#L25

On successful posts, please redirect the user to "/need/posted". Please create this new component (NeedPosted.js) as a copy of Volunteer.js component.

After the basic hookup, if you have time, please see #34

We need to incorporate Redux and follow the ducks/modules pattern.

Thanks for working on the notification, @prescottprue. I noticed that the browser prompts even when the user is not logged in, e.g. when a new anonymous person visits the website. Can we request the notification permission only for logged in users?

Need to design the Firestore collection and attribute design. Please document in this wiki entry https://github.com/CV19Assist/app/wiki/Datastore-Design

See "Post a help task" in https://docs.google.com/presentation/d/10-7U6jxHvQ_3AEq4Pg8U_hbdkpAA787PSP9INo-gnE4/edit#slide=id.g81892fd633_1_25

The source files is hosted in a github repo/github page and have the following format.

The index file will be index.json and have the following format. It will return the blog entries in the needed order. Let's not worry about pagination in the first iteration.

[{
	id: “random-id-here”,
	createdAt: “ISO-8601 timestamp”,
	title: “First Entry”,
	author: “Farhan Ahmad”,
	slug: “first-entry”,
	summary: “A quick description for the listing page.”
}, ...]

The individual entry files will are named entry-{slug}.json and will have the following format.

{
	id: “random-id-here”,
	createdAt: “ISO-8601 timestamp”,
	title: “First Entry”,
	author: “Farhan Ahmad”,
	slug: “first-entry”,
	summary: “A quick description for the listing page.”,
	html: “JSON-escaped HTML”
}

Examples:
https://cv19assist.github.io/blog/index.json
https://cv19assist.github.io/blog/entry-first-entry.json

Site Functionality

The above should result in the following routes on the front end.

/blog — Listing page
/blog/<slug> — Specific blog entry

Feel free to see the source blog repo if you are curious about the generation process.

We need the following changes to get the notifications ready for general rollout.

1. Do not send out emails when there are no requests.
2. Simplify email templates (remove all the Mailchimp tags), confirm that the template is functioning properly (null values, etc.) and update copy.
3. Enhance the FCM notification to display the requester firstName and generic location. Confirm that clicking on the notification takes to the request page.
4. Remove the user filter so all users start getting the notifications.