-
Notifications
You must be signed in to change notification settings - Fork 5
Feature/donor wall style tweaks 1 #1256
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
base: feature/donor-wall
Are you sure you want to change the base?
Feature/donor wall style tweaks 1 #1256
Conversation
…days worth of data. Currently have debug data output for created day for each donation record
matthewdylan
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Don't have the time to go through and vet all of the css but I'm sure it's good. Left a general question above.
|
|
||
| // Set base typography proportions for headers, paragraphs, etc. | ||
| // sizing variables in settings/_breakpoints.scss | ||
| h1 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pretty sure these rules are being covered elsewhere but wanted to make sure you checked to see if these updates effected any of the other donor app pages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some mild regressions on the /donate page, specifically around the h1 size. I'll address shortly.
What's this PR do?
/membersWhy are we doing this? How does it help us?
Continuing to work towards a port of the donor wall to this repository.
How should this be manually tested?
After running locally, go to localhost/members, compare to https://www.texastribune.org/support-us/donors-and-members/
How should this change be communicated to end users?
Are there any smells or added technical debt to note?
What are the relevant tickets?
Have you done the following, if applicable:
(optional: add explanation between parentheses)
TODOs / next steps: