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

QR code component

Poncho Ramos•290
@alfonso-ramos
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I'm glad to receive feedback 😀

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    👾Hola Poncho!

    Acabo de ver tu solución, amigo, y tengo algunos consejos para ti con respecto a la capacidad de respuesta de la imagen y el contenedor.

    Para corregir la capacidad de respuesta del contenedor, debe reemplazar width con max-width para que el contenedor sea flexible, tenga en cuenta que width es una medida fija y no permite que el contenedor crezca.

    Para hacer que la imagen coincida con el tamaño del contenedor, agregue max-width: 100% y display: block

    Aquí hay algunos cambios que hice para ti:

    .component_container {
        MAX-WIDTH: 32rem;
    }
    
    img {
        display: block;
        max-width: 100%;
    }
    
    

    Saludos desde Brasil!

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hi, Poncho Ramos! 👋

    Nice work on this challenge! 🙌 Your solution is responsive and looks great! 👍

    I agree with what @saifion33 has suggested. Every page should have one h1 to allow the users to identify each page. But, since it is just a component, you can use h2 if you want. You can assume that it is a chunk or a part of a full website so the h1 might exist somewhere else.

    One suggestion I have is to improve the alternative text of the QR code. You can improve it by telling the users what the QR code is about. In this case, it is going to navigate the users to https://www.frontendmentor.io/. So, alternative text like "QR code to frontendmentor.io" is good enough.

    That's it! I hope this helps! Keep up the good work! 👍

    Marked as helpful
  • Azeem Saifi•370
    @saifion33
    Posted almost 3 years ago

    Hi poncho your solution in perfect .

    If you want to improve here is some tips

    Replace <p class="bold">Improve your front-end skills by building projects</p> with h1 tag

    <h1 class="bold">Improve your front-end skills by building projects</h1>

    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