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

Responsive QR Code Component

MiguelDeLaMora•10
@MiguelDeLaMora
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What did you find difficult while building the project?

  • The thing that i spent more time was on making responsive the page. First I made it with the principles of "Mobile first".

Which areas of your code are you unsure of?

  • On how I arrange the date and items (flex or grid)

Do you have any questions about best practices?

  • Yes, on my css
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bailey Frye•90
    @baileyfrye1
    Posted over 1 year ago

    Hey Miguel! Your CSS overall looks pretty good. Couple pieces of advice I have, I would set your font family on either your body element or on your card, that way you don't have to declare the font-family for each text element. I would also utilize the "margin" shorthand so you don't have to individually set every side. (i.e "margin-bottom: 3em; margin-left: 2.5em; margin-right: 2.5em;" could be set to "margin: 0 2.5em 3em" and "margin-left: 2em; margin-right: 2em;" could be set to "margin-inline: 2em")

    It does look like your image isn't loading, in your HTML you have your image source set to "/images/image-qr-code.png" but in your file structure you do not have an images folder so it is not able to find your image. If you just remove the "/images" from the front of your source everything should work fine. Without seeing the image it's impossible to tell how the CSS looks for the image.

    Great job overall though and great use of responsive CSS units!

    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