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

QR Code Component

Dezza Anne•250
@DezzaAnnePeregrina
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi! this is my first challenge in frontend mentor. I am willing to take advices and comments to learn more. Thanks :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bryan King Pecho•230
    @bkpecho
    Posted over 2 years ago

    Hey Dezza! I wanted to take a moment to congratulate you on completing your first frontend mentor challenge. It's clear that you put a lot of effort into your work and you should be proud of your achievement. You have shown great potential in your frontend development skills and I encourage you to continue pushing yourself to reach new heights.

    I reviewed your project and I have to say that everything looks great! Your attention to detail is impressive, and the overall design is very clean and polished. However, I noticed that there is one thing missing: alt text for your qr code image. Adding alt text will not only make your site more accessible to users with visual impairments, but it will also improve your site's search engine optimization (SEO).

    Don't worry, it's a quick fix and I'm sure you'll have it done in no time. Keep up the great work and I look forward to seeing what you create next. Happy coding!

    Marked as helpful
  • Josh•1,120
    @josh76543210
    Posted over 2 years ago

    Hey there! Great job on your solution!

    Here is one more recommendation for your code:

    Add an alternate text for your image. For example: <img src="images/image-qr-code.png" alt="QR code to frontendmentor.io"/>

    Happy coding!

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted over 2 years ago

    Hi, Dezza Anne! 👋

    Congratulations on completing your first Frontend Mentor challenge! 🎉

    I recommend removing <div class="heading">. You don't need to make the text content a flex layout. Use margin to add spacing between the heading and the paragraph. Then, use the padding of the <main> element to control the text wrapping.

    After that, for the attribution, I recommend having the class attribution on the <footer> element instead. This way, you can remove the <div> element.

    For the styling, I recommend increasing the line-height of the <body> element. line-height: 1 is making the spacing between lines of text of the paragraph too small. You should increase it to something like 1.5.

    I hope this helps. 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

Oops! 😬

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

Log in with GitHub