Soften black from #000 to #191919.
Change font size from 0.75rem to 0.9rem for readability.

Low priority, will just help abstraction.

Maybe a good task for @ryanfeatherman?

@gmittal don't gross us out

You said 2 seconds @gmittal.

Low-pri UI enhancement: it'd be nice to change the dropdown selection between Yes and No on the first question to be two buttons alongside each other, of which only one can be pressed. I'll draw this out to make it clearer soon.

The way the back button appears and leaves the form is very choppy and unpleasant to watch. Very minor UI fix.

Should run on top of a super simple Node webserver. Allows for better communication and setup across the various components of the entire system.

Really minor fix needed with the email validation regex.

The site works fairly well on most mobile phones. However, not all of the font/input sizes look good/are compatible on all mobile devices.

Kneel down before this webpage: https://varvy.com/pagespeed/wicked-fast.html

Drastically improves UX, also makes the site feel more robust.

Minor UI fix that tells the user when the input they've entered is invalid (e.g. the user says that their primary contact method is SMS, but they give an email address).

If I go back and then go forward, the form information I filled is now gone. If I don't change the previous field, there's no reason to reset any other fields either.

We need a script to set up the env, so we don't have to run commands like ./node_modules/eslint/bin/eslint.js. (copy of ProjectCopilot/mailroom#50)

Relevant.

BTW @gmittal feel free to assign any of these small tasks to @ryanfeatherman or @srustagi.

Our questions are currently very ambiguous and not very helpful in general. @ankitr, perhaps we can redesign our questions prior to MVP release? It should be very easy to fix through questions.json.

This way we can hide all of our precious server-side variables such as ports and the like.

My hacky intuition is to do some absolute positioning on the button so it doesn't move but there is probably a better way.

Write documentation in either the wiki or README specifying how to use the concierge. Explain how to set it up and how the questions.json works.

See ProjectCopilot/volunteer#2

Still need to clean data in the form (e.g. you can have you age be a string and not a number). There are also no checks to make sure the user actually submits all of the information (currently it submits empty strings for empty fields).

If a user submits a referral or request with the exact same contact information for the person who needs to be helped, throw an error stating that the user is already being helped by support staff.

Under the form, there should be a "Learn More" link which transitions the screen to an informational page for first time users.

It's time that our new logo was added to everything.

Doesn't look anywhere as nice or functional as it does on Chrome on browsers such as Firefox (currently testing on Quantum).