-
Notifications
You must be signed in to change notification settings - Fork 5
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
Respsonsive Redesign // UI fix - Need more help component #179
Comments
@jonichan Please post your copy recommendations here, thank you! |
Option A Option B I'd like more feedback on what wasn't working with the old copy, then I can tweak these suggestions accordingly. |
@jonichan thank you these are great! As far as the button CTA - I apologize because I am reverting back after reminding myself why we chose that language in the first place -- I actually believe keeping 'Ask the Community' drives more continuity across the site and the support vision -- I went back to the research we did a couple months ago on why we picked that language (same language used in the nav) -- check it out here . This all being said :
|
@kkellydesign moving to triage for you |
@jess-cook03 sure, but please provide URLs for where each example should go. |
http://localhost:3000/en-US/get-involved pages get the grey box |
These changes will all be in here: mozilla/kitsune#4193 @jess-cook03 as far as the icon goes, can you send me the SVG file that you have? The one I used is straight from Protocol, and it looks like the right proportion to me. I did shrink it down from 36px to 32 though. Here's the raw file from protocol: |
Confirming this ticket is completed |
@kkellydesign
Can this component have two skins? One Mozilla brand and the one Firefox?
Specs for both:
@kkellydesign global rule here:
For mozilla brand the typography Zilla and body should always be black -- not Ink or grey.
(refer to image above and styling for #183 )
Current screenshot:
The text was updated successfully, but these errors were encountered: