Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

CSS Grid, Flexbox, box shadow, box sizing

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

Solution retrospective


How exactly did you go about making sure the box shadow was as close as possible? How did you go about making sure your image was sized correctly? Did you put the image dimensions in the HTML img tag?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Exequiel Arco•390
    @quielScript
    Posted over 1 year ago

    Hi, Nicholas. Nice question! This was the first challenge that I took, to answer your questions:

    How exactly did you go about making sure the box shadow was as close as possible?

    • Using the box-shadow property, we can basically give it 5 values (x-offset, y-offset, blur, spread, and color). I checked your code and it seems you gave a value of -6px to your spread, in my case, this is unnecessary. What I did was:
    box-shadow: 1rem 0 4rem rgba(0, 0, 0, 0.2);
    

    I only gave it 4 values (x-offset, y-offset, blur, and color) which worked for me. You need to experiment with this to achieve your desired outcome.

    You can check this out to learn more.

    How did you go about making sure your image was sized correctly?

    • I did not define a fixed size for my image, what I did was I added the max-width property to my card container and made the image occupy 100% of the width:
    .container {
      max-width: 30.5rem;
    }
    
    .qr-img {
      max-width: 100%;
    }
    

    Did you put the image dimensions in the HTML img tag?

    • No, I prefer adding styles to my elements externally which is the proper way of adding styles.

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

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

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub