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

responsive design of a qr code card

Ashley waudby•310
@ashleywaudbydev
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


would really like some feedback on this one thankyou.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ashley waudby•310
    @ashleywaudbydev
    Posted over 3 years ago

    thankyou for the feed back i saw my mistakes , i have adjusted it now cheers .

  • Aditya Singh•460
    @adityas24
    Posted over 3 years ago

    Hey Ashley you did a great job!🙂

    I studied your code well and found some points you need to improve on: 🙂

    1. You are using div element where it is not necessary. Using div there will not create any problem, but you are unnecessarily increasing the length of the code. That will reduce the maintainablity and readability of the code.

    For example: <div class="header"> <h1>Improve your front-end skills by building projects</h1> </div>.

    Here you do not need to wrap h1 in a div. If still you want to write h1 inside of a header, then use <header> tag instead. As we have to take care of semantics also 🙂

    1. Similary you don't need to wrap paragraph inside of a div. You can straight away use <p> tag without wrapping it. Afterall everything inside a flexbox will become flex item. You don't need to wrap everything inside a div 🙂

    I will recommend you to go through markup written by Daniel. He has written it perfectly i think

    https://www.frontendmentor.io/solutions/qr-code-component-using-html-and-css-38XEjHXG2

    All the best 🙂👍

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