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

qr_code

Ted•80
@TedL402
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • JunoField•310
    @JunoField
    Posted over 2 years ago

    Hi,

    This was a great attempt, just a few suggestions:

    Some of the CSS "tweaks" you've added aren't necessary for this project - sections 7 and 8 for example. There's no real need to remove these - just thought I'd make you aware.

    Ideally the main element should be centered - another commented mentioned a grid solution, but personally I'd just use absolute positioning. This can be done by adding this to the centre card's CSS:

    position: absolute;
    left: 50%;
    top: 50%;
    transform: translateXY(-50%, -50%);
    

    Also, take note of the issues raised in the FM report:

    • Alt text: Personally I'd either make it empty or add a link, but neither are ideal solutions in production so it's really up to you.
    • Main tag required: This one's simple: just change your section tag to main and update the CSS to suit.
    • Attribution section: Personally I'd replace div with footer for the attribution to fit this requirement.

    Speaking of the attribution section, don't forget to fill it out with your name and profile. I also like to move its styling from the HTML file to the CSS file but that's down to preference.

    Good luck!

  • Account deletedPosted over 2 years ago

    Hey there! 👋 Here are some suggestions to help improve your code:

    • Do not forget ⚠️ to check your FEM report, to see what is incorrect and update your code with it right after you submit your challenge.
    • To properly center ✅ your content to your page, you will want to add the following to your body (this method uses CSS Grid):
    body {
        min-height: 100vh;
        display: grid;
        place-content: center;
    }
    

    More Info: 📚

    Centering in CSS

    If you have any questions or need further clarification, feel free to reach out to me.

    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

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