Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

QR Code

Tobiloba•70
@Tobiloba1234
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


While trying to recreate the design, it was fun and I found it hard to make my profile picture come together and arranging my html element accurately. I have a long way to go but would really like feedback and review of my code. View my Profile paragraph could not change the background color, would love to know why.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mikhail•440
    @MikeBeloborodov
    Posted almost 2 years ago

    Hello! I like how it looks, very good for a beginner! Try to change your header background color like this:

    header {
    background-color: blue;
    }
    

    It should work. Or change it to any other color that you like. Hope it helps! Good luck!

    Marked as helpful
  • P
    Justin Green•2,940
    @jgreen721
    Posted almost 2 years ago

    Yea it looks like you have the span background set to blue and so that is whats rendering. Since a tags(links) naturally default to blue text, that makes things a little hard to see but that can overwritten in css as well. a{color: foo} -- although this approach will apply the color to all a tags which may not be what you want, in which case just give the a tag a class and target it that way.

    Nice work though, I like the personalized/contact header idea and you nailed it on the card design! 🙂

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub