You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the user clicks "donate now" they're redirected to the website in a new tab; when they come back they get a message asking whether they've donated (y/n); if yes, then "how much?"& "any message of support" what it does: (1) creates a social signals that communicates how trustworthy you find the fundraiser - makes it easier for other donors to vet; (2) allows you to virtue signal (think comments & Constitution DAO); (3) creates a proxy for how much money someone got (could help cap the donations if the fundraiser has smaller goals)
Acceptance Criteria:
Add an identifier in localstorage that keeps track of user having clicked donate now
Store user input in a database (google sheets)?
When loading the homepage, show a modal that asks for user input
Legacy comments:
Birdman [Mar 7 at 9:44 AM]
Re: Reporting Donations amount feature --- I have expressed concerns previously on this proposed feature.
This is technically complicated than it might appear and could easily lead to a buggy website. We launched the website without any major bugs. We need to maintain that.
Web apps cannot display one modal over another. Currently not sure we can support this feature given that the OrgPage is a Modal already. We would have to close any open modals before opening a new modal. Tracking modal state is not something we currently support.
Users navigate around and click on multiple things quickly. What would be displayed to a user that has clicked on more than one Donate Now button?
Where would this payment information be stored? Who would manage this information? That means we would need some sort of Donations Dashboard where non-technical people could check these amounts. We can't have Devs doing database queries and manually filling out excel spreadsheets. That means we either need to plug into some sort of existing Donations Dashboard through an API, or we need to build an API ourselves.
"omen" also had this to say about storing payment info: "yeah, payment information storage gets sticky legally"
[Reply]
Javier Gonzalez added Acceptance Criteria to this card
[Mar 2 at 7:49 AM]
Javier Gonzalez added this card to Backlog
[Mar 2 at 7:48 AM]
The text was updated successfully, but these errors were encountered:
After the user clicks "donate now" they're redirected to the website in a new tab; when they come back they get a message asking whether they've donated (y/n); if yes, then "how much?"& "any message of support" what it does: (1) creates a social signals that communicates how trustworthy you find the fundraiser - makes it easier for other donors to vet; (2) allows you to virtue signal (think comments & Constitution DAO); (3) creates a proxy for how much money someone got (could help cap the donations if the fundraiser has smaller goals)
Acceptance Criteria:
Legacy comments:
Birdman [Mar 7 at 9:44 AM]
Re: Reporting Donations amount feature --- I have expressed concerns previously on this proposed feature.
This is technically complicated than it might appear and could easily lead to a buggy website. We launched the website without any major bugs. We need to maintain that.
Web apps cannot display one modal over another. Currently not sure we can support this feature given that the OrgPage is a Modal already. We would have to close any open modals before opening a new modal. Tracking modal state is not something we currently support.
Users navigate around and click on multiple things quickly. What would be displayed to a user that has clicked on more than one Donate Now button?
Where would this payment information be stored? Who would manage this information? That means we would need some sort of Donations Dashboard where non-technical people could check these amounts. We can't have Devs doing database queries and manually filling out excel spreadsheets. That means we either need to plug into some sort of existing Donations Dashboard through an API, or we need to build an API ourselves.
"omen" also had this to say about storing payment info: "yeah, payment information storage gets sticky legally"
[Reply]
Javier Gonzalez added Acceptance Criteria to this card
[Mar 2 at 7:49 AM]
Javier Gonzalez added this card to Backlog
[Mar 2 at 7:48 AM]
The text was updated successfully, but these errors were encountered: