-
Notifications
You must be signed in to change notification settings - Fork 1
Donation after-actions makeover CSS #304
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: main
Are you sure you want to change the base?
Changes from all commits
946916c
4aacf47
cdec8e5
e5f9d05
5bdd10f
49dc29c
547c7f5
cadcf36
023b436
5e03e58
cb80831
df32a5c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,84 @@ | ||
| body.survey-page | ||
| { | ||
| .aa_makeover { | ||
| h1 { | ||
| font-size: 2.25rem; | ||
| text-transform: uppercase; | ||
| } | ||
| h2 { | ||
| font-size: 28px; | ||
| @include font(roboto); | ||
| font-weight:bold; | ||
| } | ||
| a { | ||
| color: $dark-blue; | ||
| display: inline; | ||
| } | ||
| label { | ||
| font-weight:normal; | ||
| } | ||
| #known_user { | ||
| text-align:center; | ||
| h3 { | ||
| @include font(roboto); | ||
| font-size: 16px; | ||
| } | ||
| } | ||
|
|
||
| #survey-questions { | ||
| // Placeholder | ||
| ::placeholder { | ||
| color: $placeholder-gray; | ||
| // Override Firefox's unusual default opacity; see https://github.com/twbs/bootstrap/pull/11526. | ||
| opacity: 1; | ||
| } | ||
| } | ||
|
|
||
| .known_user_firstname { | ||
| font-weight: 700; | ||
| } | ||
| .btn.cta { | ||
| display: inline-flex; | ||
| justify-content: center; | ||
| align-items: center; | ||
| @include btn--azure; | ||
| padding: 10px 20px; | ||
| color: $white; | ||
| padding: 13px 19px; | ||
| @include font(roboto-condensed); | ||
| font-size: 1.8rem; | ||
| font-weight: 700; | ||
| text-transform: uppercase; | ||
| width: 100%; | ||
| background-color:$azure; | ||
| } | ||
|
|
||
| // RADIO | ||
| .radio-input { | ||
| //font-size:20px; | ||
|
|
||
| input[type=radio] { | ||
| border: 1px solid #000000; | ||
| margin-right:0.25em; | ||
|
|
||
| &:checked { | ||
| border: 0px; | ||
| background-color: $azure; | ||
| opacity: 1; | ||
| box-shadow: none; | ||
| } | ||
| } | ||
| } | ||
|
|
||
| label { | ||
| color:inherit; | ||
| @include respond(( | ||
| line-height: 1, | ||
| )); | ||
| } | ||
|
|
||
| ul#ak-errors { | ||
| margin-left: 0px; | ||
| } | ||
| } | ||
| } |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,6 +3,7 @@ $thin-air: #caf4ff; | |
| $white: #ffffff; | ||
| $off-white: #f3f3f3; | ||
| $gray: #cacaca; | ||
| $placeholder-gray: #c2c2c2; | ||
technicalex marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| $light-gray: #a7a7a7; | ||
| $slate-gray: #696a6a; | ||
| $dark-gray: #222222; | ||
|
|
@@ -19,6 +20,7 @@ $azure: #00abff; | |
| $logo-blue: #1298FE; | ||
| $light-blue: #99ddff; | ||
| $ice-blue: #e5f5ff; | ||
| $dark-blue: #006394; | ||
| $red: #ea1c24; | ||
| $muted-red: #c3645c; | ||
| $orange: #dbad54; | ||
|
|
@@ -34,4 +36,4 @@ $moriginal-green-medium: #37b34a; | |
| $moriginal-blue-dark: #193f92; | ||
| $moriginal-blue-medium: #296ecb; | ||
| $c-facebook: #3B5998; | ||
| $c-twitter: #1DA8E2; | ||
| $c-twitter: #1DA8E2; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This color doesn't appear to be used. Furthermore, it looks like it's a different color from the color specified on Figma (#5AA5EB) and also (confusingly!) different from both the button and hover color I was asked to use for the Twitter button on my page (#1DA1F2 and #3FB6FF). If it's not being used, I would recommend removing it, unless we expect to use it in the future. But maybe more importantly, should we ask for clarification on the correct Twitter color?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I didn't actually add this, just a newline at the end of the file. But yes, that's very confusing and we should ask for clarification. (Maybe it's used on existing main-giraffe template 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.
I wasn't familiar with this style, so I looked it up. I think it only applies when we are using scroll snap, which I can't find either in existing styling or in these changes. Maybe I'm missing something; can you please explain? Thank you!
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.
On mobile, there's a button that lets you jump to the form, but because the header floats above everything else on the page, the form gets cut off. Adding the padding here makes the anchor tag jump to the right place to display the entire form.
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.
FYI @sjwmoveon, new scroll-padding-top values should be used for compatibility with the new header if this pull request is merged. I've copied the correct values below. (I suppose only the first one applies, if the button to jump will only ever appear on mobile.) Thank you!