-
Notifications
You must be signed in to change notification settings - Fork 100
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
Make image on Backup & Recovery
page less imposing
#746
Comments
This issue could be part of our bigger milestone focusing on revising the newly formed Daily spending wallet reference design we now have in the guide. |
Backup & Recovery
page less imposing
I'd like to solve this. How do I go about it? I have check the issue, and if I get it correctly the image size and colour doesn't blend well with the content. I could recreate the illustration in figma and make appropriate changes |
Here is the Figma file for that image: https://www.figma.com/file/q9EgLqOKcIVc0Cq7khtpNm/Onboarding-%3E-Backups?node-id=0%3A1 by @sbddesign This can be found in the markdown file which if you go to Code at the top, go the guide -> Daily spending wallet -> Backup & recovery -> landing-page.md file you can see there is a illustration sources section at the top of the page. Details on how to size the images can be found here: https://bitcoin.design/guide/contribute/illustration-guidelines/ If you need help opening the PR for this, happy to help! |
The simplest option is to just remove the line A second simple option could be to tone down the colors a bit (mostly the purple background). But up to you what you'd like to do. |
Thank you @GBKS and @Bosch-0 for your help. The repo has been cloned on my computer to make the appropriate change. The option of removing the Here are the two images for comparison. I also need help with PR |
@enyipreshious Here is a good place to learn about making a PR. There is a video tutorial you can watch and instructions underneath the video. Let us know if you have any questions, we can help. |
This is complete with the merge of #775. |
Via this comment.
Live page.
The text was updated successfully, but these errors were encountered: