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

This is a QR code component that uses HTML and CSS

airtable
Grace M codes•20
@GraceMCodes
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • beowulf1958•1,930
    @beowulf1958
    Posted about 1 year ago

    Hello, Grace ! I really like the box-shadow; I will use it in my own design! This project is well on its way; a few more lines of code will make it look like the design.

    First, your h3 should be <b></b> (bold) not <em></em> (slanted, italic).

    Second, your font-size is too big; the guidelines call for font-size: 15px.

    Next, fix the centering: remove position: relative and add flex-direction: column; min-height: 100vh. [This allows your flex container--the body element--to use the entire vertical viewing space to aid in the centering]

    To get the box in shape, remove top: 0; bottom: 0; left: 0; right: 0; margin: auto; Add width: 320px; padding 20px; Your stylesheet now looks like:

    body{
      background-color: rgba(49, 103, 184, 0.469);
      font-size: 15px;
      font-weight: 400;
      text-align: center;
      display: flex;
      align-items: center;
      justify-content: center;
    
      flex-direction: column;
      min-height: 100vh;
      
    }
    .box-shadow{
        box-shadow: 10px 10px 10px rgba(0, 0, 0, 0.2);
        border-radius: 20px;
        background-color: rgba(240, 248, 255, 0.949);
        width: 320px;
        padding: 20px;
    }
    

    That should get you pretty close. For extra points you could add:

    h3 {
          color: hsl(218, 44%, 22%);
          font-size: 25px;
          font-weight: 700; 
        }
        p {
            color: hsl(220, 15%, 55%);
        }
    

    Hope this helps. Keep on coding!

  • Uche Ofatu•350
    @Macnelson9
    Posted about 1 year ago

    Hi there Grace! I see you've attempted the first challenge on frontend mentor and I'm super proud of you for attempting this challenge. I'm trying to look up your codes but It's returning a Page not found error, so I suggest you check on the repository. And finally, you should have attempted this challenge using the starter files provided which includes the QR code image and the color codes used in the project. You can always reach out for help, I'll be here. Thank you and Happy Coding!

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

Oops! 😬

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

Log in with GitHub