-
-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next round of Pray and Pay revisions #4845
Comments
Another thing, sorry, these are going to trickle in. This doesn't work if people don't have RECAP installed, so if people click the buttons to buy things, we should make sure they have RECAP installed before sending them to PACER. I think we have this functionality elsewhere, so we just need to bring it to these buttons too (if we haven't already). |
I'll take a bit to digest your comments, but regarding (2), aren't the buttons present on those pages? See this example in the bottom right. |
Yeah, ok, that's fine. Thank you! |
It's getting really close. Thanks everybody for the work getting it so far. It's cool already, but we need the UX to be good for it to work. I hope this doesn't feel like moving goalposts. We're close!
Here are my thoughts for the next round:
From the leader board, clicking on documents that aren't on page 1 of the docket doesn't work. For example, this link fails because the docket page only goes to entry 159 (and the link is for number 396):
https://www.courtlistener.com/docket/63290154/missouri-v-biden/#entry-396
A simple solution is to take the users to the document page instead:
https://www.courtlistener.com/docket/63290154/396/missouri-v-biden/
Speaking of those pages, I just noticed they don't have the icon. Darn.
We still need to teach people what the emojis mean and how to find the prayer leader board. One thought is that the first time somebody prays for something, we could pop up a modal congratulates them on their first prayer and then tells them about the leaderboard, how it all works, and points them to the help page.
We'd need a reliable way to know if the prayer was somebody's first. Maybe the API for creating a prayer could efficiently return if it's the first one the user has?
We're going to set up an email list that reminds people to buy things with their PACER accounts at the end of each quarter. We'll just need a button for it so people can go to the sign up page, and we'll want that button on our help page with an explanation there too.
The leader board page:
h1
heading on the leader board needs space below it. Maybe add.v-offset-below-3
to it?As for where the buttons should go, I think it should mimic our new opinion page. It's not yet released, but it looks like this across the top:
I think the Remind Me to Help button can go on the left, and the "Your Prayers" and "Learn More" can go on the right. All buttons can be white.
The HTML title for this page should say:
The og:description needs filling out too. It can explain a bit about what the project is.
The "Your Requests" page:
.v-offset-below-3
class.We need pagination on both of these pages. Maybe 25 items each?
In #4507 (comment), @v-anne suggested:
I'm actually sort of curious how useful this table will be to folks. I guess people might use it as a bookmark for stuff they're interested in, so this suggestion would be helpful. I think it's OK to punt on this for now though and keep the page simple.
Super interesting. We do that on the user tags page. I feel like for this to work, the page will need an RSS feed for people to follow or something. Just expecting people to reload it seems unlikely to do much. I suggest punting this for now too.
Some docket entries lack entry numbers. That'd be an easy thing to key off of. I'm not sure if we know how to detect minute entries though.
I think these are my
wishesprayers for the last iteration. I'm going to push a branch with help file tune up too in a few minutes.Thank you all for pushing and pushing this feature. It's one of the bigger ones that has been volunteer-contributed in a long time.
The text was updated successfully, but these errors were encountered: