Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

QR Code Component [Mobile First + Vanilla CSS + Responsive]

accessibility
Aakash Verma•9,540
@skyv26
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback welcome, Made it within 1 hour. I am great learner and I will be happy to hear anything regarding design and code in order to enhance my skills. Feel free to share your thoughts.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    David Turner•4,130
    @brodiewebdt
    Posted over 3 years ago

    That didn't take long.

    Marked as helpful
  • Danilo Blas•6,300
    @Sdann26
    Posted over 3 years ago

    Very fast! Good work Aakash :)!

    Marked as helpful
  • Anosha Ahmed•9,300
    @anoshaahmed
    Posted over 3 years ago

    pixel perfect

    Marked as helpful
  • Hania B.•1,280
    @techanthere
    Posted over 3 years ago

    @skyv26 that's awesome! And here I am still planning to complete this cute looking challenge :) And hey just a little suggestion, footer text is flowing over the card, when the height is decreased, I think you don't really need to use position property for this solution, instead just stick with some padding and for the footer some margin.

    Marked as helpful
  • Aniket Khot•50
    @aniket53
    Posted over 3 years ago

    brother can u help me to get the right course for the react js learning i also wanted to learn it

  • Kacper Kwinta•1,405
    @kacperkwinta
    Posted over 3 years ago

    My advice on the names of variables in css - use those that do not directly describe the color, but, for example, what elements they should belong to, because when you change the value of a variable, its name loses its sense

    Also you shouldn't use <main> tag for box with these elements, because this tag is for grouping elements, not for styling

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

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

Oops! 😬

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

Log in with GitHub