Skip to content
  • Learning paths
  • Challenges
  • Solutions
  • Articles
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

QR Code Page Using Flexbox

sass/scss
Nguyen Nguyen•340
@jesuisbienbien
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello, I've tried my best to recreate this webpage. This is my very first project and I have a few things I'm not satisfied with and would love to receive feedbacks on

  1. My container's still bigger than I wanted it to be, what's the best solution to make it smaller?
  2. The blue background of the qr code has 2 shadows which I have no idea what it's called and how to do it. I'm happy to receive feedbacks on any other things too. Thank you!
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yahya•80
    @yhas14
    Posted over 3 years ago

    regarding the shadow, you can you CSS box-shadow property.

    syntax box-shadow: horizontal-value vertical-value blur and color. example box-shadow: 10px 5px 5px red;

    You can also add another shadow on the same selector ( separate second shadow by a comma) example box-shadow: 3px 3px red, -1em 0 .4em olive;

    You can check the MDN site for further resources. https://developer.mozilla.org/en-US/docs/Web/CSS/box-shadow

    I would say don't be too concerned with exact proportions if you don't have a premium. I think you did a great job on your first challenge.

    Marked as helpful
  • Hexer•3,620
    @EmmanuelHexer
    Posted over 3 years ago

    Great job overall man. You can also check out mine to see how i did it.

  • Nguyen Nguyen•340
    @jesuisbienbien
    Posted over 3 years ago

    Nevermind on the second question 😅 . I just noticed the background comes with the image. Sorry, it's my first coding challenge so I'm kinda lost.

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

Oops! 😬

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

Log in with GitHub