Project for updating nonprofit website
1) The nonprofit website needs to operate more like the https://nextdoor.com website. You need to research and find out what the website nextdoor.com does to be sure you understand everything the nextdoor.com website does and include that functionality in this project. I have attempted to list everything the nextdoor.com website does in this project description, but I may have over looked some features and functions which still need to be included in this project for it to be completed. It is up to you to make sure all of the nextdoor.com functionality is completely done and provided in the deliverables for this project. 2) Change material design color scheme of the website to look something like the color scheme of https://nextdoor.com. Simply brighten up the current color scheme using material design rules. 3) Add our policies, procedure and user agreement to the registration process so the user has to agree to abide by our policies, procedures and usage agreement to use our website before they can be registered with us. I will provide the policies, procedures and usage agreement later. 4) Build a administration email list into the website so every registered user will be put into our mailing list to get updates on what is going on in their zip code. Only the admin can access the email list and the email list is automated to send out emails when users want to let their zip code know what is going on in their zip code area. 5) Build a referral capability into the website so existing users can submit new users email address, first name and last name to become a member of our website by asking them to register with us. This is what nextdoor.com does. 6) Build the ability for existing users of our platform to send messages to other users in their zip code area. This is what nextdoor.com does. 7) Build a administration mass mailing email management tool to send emails to groups of users based on zip code and groups of zip codes and all users and individual users. 8) Build a set of administration reports in the website which only the admin can get to. a. A report for all of the tutoring and community reports in a zip code area. List detail for both the tutoring and community reports (separate reports). b. A report detail on on city, state, zip for both the tutoring and community reports. c. A report for listing a detail list of all parents and children registered for CodeForward Academy Tutoring Requests. d. All of the reports must be able to be printed in a clear format and saved as a text, cvs and pdf file. 9) Build a feature to allow users to reset their own password by themselves via email. 10) Build a feature to allow users to upload pictures and movies to the complaint table as large as possible. 11) Build a feature to allow the Admin user to modify user passwords, put user accounts on restriction status, update user information. 12) Build an automated response to users who register for the website so that they get a email sent to them to verify they have registered for the website. And then once they verify they are sent a Welcome email message. See the attached example of Email Verification and Welcome Email images. Use the CodeForward logo image to substitute the logo image in the example emails. 13) Build an automated response to have an email sent to the user when they submit a request for “Tutoring” and a different email response for when a “Community Reporting” is submitted so they get a notification email message sent to their email address with a file attachment of our how to overview pdf file, which I will provide later. 14) Add the ability for Admin user to update user registration, tutoring requests and community reports in the database. 15) Build an Administration tool that only the Administrator can get in and it must be password protected and allow the Administrator to change the Administrator name and password at will. The Administrator should be able to add other Administrators and change all of the Administrator names and passwords at anytime. 16) The administration tools and reports should be password protected in the Administration tool, separated from the regular user website access. 17) All design and functionality work must be approved by me, prior to any work being done and the deliverable agreed on. 18) Interested freelancers need to submit a project plan and deliverables schedule along with costs so we can discuss it and come to an agreement we can put in writing and each entity agrees to it. This way we are clear on what is expected on both sides of the project. 19) Code must work without failure of the design and functionality on the nonprofit website before payment is given.
The website is: www.ethanberry.org/ebics/
All assets and deliverables for this project shall be turned over and released as the property of Ethan Berry and the software tested to be fully functional for each delivery phase before payment is made.