Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 7 months ago

QR Code Component

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

Solution retrospective


What specific areas of your project would you like help with?

All feedback is appreciated

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aakash Verma•9,500
    @skyv26
    Posted 7 months ago

    Hi @progfish,

    Great effort on your project! 🎉 I have a small suggestion to enhance the semantic structure and simplicity of your code:

    • Simplify the Section Usage: The <section> tag is generally used for grouping related content that's meaningful on its own, often accompanied by a heading. In your case, the content can be wrapped in a simple <div> without losing meaning or structure. Here's an updated example:
    <body>
      <main>
        <img src="./images/image-qr-code.png" alt="QR Code">
        <div>
          <h1>Improve your front-end skills by building projects</h1>
          <p>Scan the QR code to visit Frontend Mentor and take your coding skills to the next level</p>
        </div>
      </main>
    </body>
    

    Why this works better?

    • Reduces unnecessary use of semantic tags where they're not required.
    • Keeps your code concise and easier to read.

    You're on the right track, and I love how clean your HTML structure already is! Keep up the great work! 🚀

    Marked as helpful
  • Alaa Mekibes•2,090
    @alaa-mekibes
    Posted 7 months ago

    Hi @progfish, you did it good job 🎉 just a few points to fix:

    • Update Your README File

    Start by using the provided README template included in the starter file. Customize it to enhance clarity and professionalism.

    • Use css variables to improved maintainability like this:
    :root {
        --bg-color: hsl(210, 46%, 95%);
        /* Add your other colors here */
    }
    
    body {
        background-color: var(--bg-color);
        /* Other properties */
    }
    
    • Separate your CSS code: Move your CSS code into a separate file (e.g., style.css) and link it to your HTML file using:
    <link rel="stylesheet" href="YOUR PATH HERE">
    

    Keep up the incredible work, @progfish, your dedication is inspiring!

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