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

QR code

Andrea-gli•10
@Andrea-gli
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

  • Brian Muniz Silveira•200
    @BrianMunizSilveira
    Posted 7 months ago

    Code Review and Suggestions

    Positive Highlights:

    1. Clean and Simple Design: The code effectively uses flexbox for layout and keeps the styles minimalistic yet functional.
    2. Font Import: Correct use of Google Fonts ensures a polished typography style.
    3. Responsive Approach: The centering of the main content ensures a good base for responsiveness.

    Suggested Improvements:

    1. HTML Structure

    • Heading Tag Mismatch: The <h3> tag should close with </h3>, not </h1>. This mismatch could cause rendering or SEO issues.
      <h3>Improve your front-end skills by building projects</h3>
    
    • Alt Text Description: Improve the alt text to be more descriptive for accessibility.
    <img src="./images/image-qr-code.png" alt="QR code linking to Frontend Mentor website">
    

    2. CSS Adjustments

    • Font Family Declaration: Update the font-family declaration to include fallbacks and match the imported font name.
    body {
        font-family: "Outfit", sans-serif;
    }
    
    • Use Variables for Colors: Define colors in CSS variables to ensure consistency and ease of updates.
    :root {
        --bg-color: hsl(212, 45%, 89%);
        --text-color: hsl(216, 15%, 48%);
        --heading-color: hsl(218, 44%, 22%);
        --container-bg: #fff;
    }
    body {
        background-color: var(--bg-color);
    }
    h3 {
        color: var(--heading-color);
    }
    p {
        color: var(--text-color);
    }
    

    3. Accessibility

    • Semantic Improvements: Wrap the <section> in an <article> tag for better semantics since it represents standalone content.
    <article>
        <section class="container">
            <img src="./images/image-qr-code.png" alt="QR code linking to Frontend Mentor website">
            <div class="text">
                <h3>Improve your front-end skills by building projects</h3>
                <p>Scan the QR code to visit Frontend Mentor and take your coding skills to the next level.</p>
            </div>
        </section>
    </article>
    

    4. Performance Enhancements

    • Preload Key Assets: Preload critical resources like fonts and images to improve loading speed.
    <link rel="preload" href="./images/image-qr-code.png" as="image">
    <link rel="preload" href="https://fonts.googleapis.com/css2?family=Outfit:wght@400;700&display=swap" as="style">
    
    • Optimize Image Size: Ensure the QR code image is optimized for its displayed dimensions (288px × 288px) to reduce loading time.

    5. Responsiveness

    • Add media queries for smaller screen sizes to ensure the container adjusts appropriately.
    @media screen and (max-width: 480px) {
        .container {
            width: 90%;
            padding: 20px;
        }
        img {
            width: 100%;
            height: auto;
        }
    }
    

    6. Consistency and Maintainability

    • Remove Unnecessary Properties: The margin-top: auto; and margin-left: auto; in the body styles are redundant since flexbox centering handles alignment.
    body {
        background-color: var(--bg-color);
        font-family: "Outfit", sans-serif;
        display: flex;
        justify-content: center;
        align-items: center;
        height: 100vh;
    }
    

    Summary

    This is a solid implementation with good design principles. The suggested changes will improve accessibility, maintainability, and responsiveness while optimizing performance. Keep up the great work!

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