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

QR code component solution.

David Miguel Andrés•330
@damigand
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am proud of how I managed to get the dimensions down because I don't have a sharp eye just yet.

What challenges did you encounter, and how did you overcome them?

I didn't encounter any particular challenge.

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

I'd like to know if there's any better way I could have written my HTML document, but help with anything overall is greatly, greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roberts P•120
    @indaqoo
    Posted 12 months ago

    Hey,

    First of all, I wanted to welcome you to Frontend Mentor and congratulate you on successfully completing your first challenge.

    Let's start by reviewing your HTML. The general structure looks good.

    Maybe I'm nitpicking here, but I think it would be great if you used the <div> element for the card itself and wrapped both text elements in their own <div> element, like in the example below:

    <main>
       <div class="card">
          <img src="./assets/images/image-qr-code.png" alt="qr code" loading="lazy" />
          <div class="card-content">
            <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>
       </div>
    </main>
    

    Here is a good resource of example card - w3school example card

    Looking at the css..

    I see that you missed the left and right padding in the text section, which is included in the Figma design file's "Text" component - view screenshot

    The border-radius on the card should be 20px instead of 16px - view screenshot

    The padding on the card should be 16px instead of 15px.

    The card's image is currently 240px by 240px but in the design it is 288px by 288px

    There are a lot of incorrect/missing values that are specific to this task and provided to us.

    I think you need to pay more attention to the design system provided in the Figma files and maybe watch a Figma tutorial to see where to get all the values. This will ensure that all the challenges look as good as possible.

    Overall, it is a good project, but I would recommend following the provided design system more closely to improve accuracy and consistency.

    Marked as helpful
  • Shinzenko•60
    @shinzenko
    Posted 12 months ago

    Hey great work buddy looks precisely like it the only small issue. i think is that the container for qr code and image itself was a little smaller than the figma dimentions but apart from that well done.

    Also if u observer the heading under image and the text under heading align together at the ends but your text seems to take more width than heading. I dont think there are any major flaws just small ones keep it rolling.

    Marked as helpful

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