rubyforgood / voices-of-consent Goto Github PK

State machine and buttons for BoxRequest and Box Workflow:

Notify next step -or- Continue buttons (Individual BoxRequest Form, BoxRequest Review Form, Box Design Form, Box Assembly (checklist) Form) - linking together box steps

CoreBoxItems index.

Follow pattern from BoxDesign Form.

CoreBoxItem == many-to-many AbuseType/InventoryType

Use Jess's exported email HTML and hook it up with Action Mailer for the Box Design completed / Box assembly needed email which will be sent to a volunteer (Which will be a different Volunteer than the one who did the Box design).

We will use this for the BoxRequest model

(see more details below)

When a volunteer is logged in and tries to access a page that requires specific permissions and the volunteer does not have those permissions, we should display a friendly error message page.

We should probably start with a friendly, generic permission denied page for any logged-in volunteer with access denied. We can then tailor that page for specific categories of access and restriction if we want to do that later.

A friendly page should show up when volunteers tries to act in a role they don't have permissions for, and a friendly page should also show when volunteers tried to claim things that a different volunteer has already claimed.

After a Box Request is Reviewed, someone will "design" the box by deciding what does in it.
It's essentially building the checklist for the Asembler of items that go in the Box.
Later we'll layer in CoreBoxItems so there's an autopopulatedr list, but to start, iterate over a short array of included items (e.g. [toothbrush, toothpaste, socks]), and an array of items that can be added (e.g. [lotion, chapstick]).
Any included items should be removable.

@jessbeach is working on a design for this page, so please check in with her

Volunteers are who we will send solicit-help emails to, and assign Attendances to
Follow data model diagram for fields and relationships

Should be embeddable / iframe-able.
Research required: how does Squarespace do embeds?
Or, just check that you can embed it on an iframe on a page
@jgaskins is a great resource for this

This may be helpful! https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options

Assembler should see a list of BoxItems that they can mark of as included as they pack the Box.

This will be a React checklist form based on the Box Design stage populated by a simple rails controller.

Use the designer's exported email HTML and hook it up with Action Mailer for the Box Assembly completed / Box shipping needed email which will be sent to a volunteer (Which will be a different Volunteer than the one who did the Box Assembly).

Use Jess's exported email HTML and hook it up with Action Mailer for the Box Request received email which will be sent to a volunteer.

After Shipping a Box, the Shipper needs to log their Purchase and add shipping data to the Box
All of this should look like one form with relevant fields from Box and Purchase, and hidden field of purchase type

This may be useful! https://edgeguides.rubyonrails.org/active_storage_overview.html

Box Request and Requester data should display, along with the extra fields: tags, and summary

MeetingType CRUD

• Creates Requester (STI on Person)
• Creates BoxRequest
• Embeddable view

Use Jess's exported email HTML and hook it up with Action Mailer for the Box review completed / Box Design needed email which will be sent to a volunteer (Which will be a different Volunteer than the one who did the Box review).

(See details below)

this will allow us to send emails!

PermissionRecord (User has_one. And add delegate methods to User model?)

Add relations for these as well

Accept initial box request.

See https://www.voicesofconsent.org/survivor-box for current example and the page where it will be embedded.

This is a big high level ticket.

When a volunteer follows a link that requires login and they are not logged in, they should be redirected to the login page. After successfully logging in, they should be redirected back to their login page.

As an example, if a volunteer hasn't logged in and tries to use a link to claim a specific box request, they should get the prompt to log in and then get redirected back to the claim for that same box request.

boolean flags on a permissions record, user has_one.

(see description below)

Don't need sign up, but should have password reset and account self-management.