mchristie / covid-collective Goto Github PK

Currently a resource can be added and it will be live immediately with no approval process.
There should be a step where an authorised person can approve resources before they are available live.

Currently the CloudFront cache is never cleared (or it has a default TTL?) it should be cleared once the deploy pipeline has run.

Using the "I'm a human checkbox"

There are a few tickets which require an admin to be authenticated but there is no way for anyone to authenticate currently.
It would be acceptable to use the Laravel build in auth services, however the "user" model should be event sources as the Resources model is.

As we're storing PII (email addresses and possibly more) we require a privacy policy.

The website should have OpenGraph tags to improve the shareability of the website.

A rough outline of my aspirations for this:

Types of offers/requests:

• Assistance with essential shopping/collection of prescriptions
• Help with education, primarily kids (e.g. help with maths homework from out of work teachers)
• Essential household tasks (e.g. elderly person changing a lightbulb?)
• Other relevant tasks?

An approximation of the flow:

• Users need to be able to authenticate ( #10 )
• Users should be able submit requests and/or offers of support
• Other users should be able to publicly reply to requests/offers of support
• Original user should be able to accept one offer or multiple requests for support
• A location (or "online") may be relevant, if appropriate approximate location should be visible publicly but the detailed location will only become available once an offer/request is accepted

When HTML page are returned to CloudFront they are not cached. A short cache time could vastly improve scalability should a spike in traffic occur.

We need a T&Cs page?

The categories don't really filt the resources we have, there could be changed to better fit the content.

Complications:

• The list of categories is repeated in: resources.blade.php, addResource.blade.php, Covid/Resources/Domain/[Audience/Category].php
• Can we reduce this repitition?
• Existing resources in changed audiences/categories will need updated to the new categories

Relevant to offering support such as through groups or the upcoming 'volunteer' section.
This page should outline appropriate steps to take to ensure assistance can be rendered without the risk of spreading coronavirus.

The copy on the homepage was a two mind vomit to get something in place, this could be greatly improved.

Currently it is not possible to edit a resource.
It should be possible for an authorised person to edit a resource and correct any typos or incorrect/outdated information.

Rather than reloading the entire page each time as it does now

Deliverables:
Split the pipeline into a test phase to run on a PR being opened and another for it to test & deploy once merged to master

As the volume of content grows the page will become excessively long and will need to support pagination.

The content on the 'Ways to Help' page is pretty anemic and could be improved.
Each description could be around a sentence longer, and more steps could be added. Plus maybe a better design?
Potential additional steps:

• Donate blood
• Share our website
• Submit additional resources
• Links to a filter for the volunteer category

To enhance SEO there should be a sitemap and robots.txt to help search engines crawl the website.

Bonus: I've not looked at SEO for any website for about 5 years, if you can suggest additional task for SEO please do.

There should be useful content in the readme page.