Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Responsive QR component using Flex and Media Queries (HTML & CSS)

Justina-R•20
@Justina-R
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm most proud of how quickly I completed the exercise using my basic knowledge of HTML and CSS. Next time, I would focus more on refining the design and experimenting with new techniques to enhance the overall quality.

What challenges did you encounter, and how did you overcome them?

The exercise was quite straightforward, but my biggest challenge was working with media queries. I overcame it by reviewing documentation and experimenting with different breakpoints to ensure the layout was responsive across devices.

What specific areas of your project would you like help with?

My main concern is whether I'm following best practices, even though the exercise was quite simple. I want to avoid replicating any mistakes when I work on larger projects, so any feedback on code structure or optimization would be really appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • juan-mentor•330
    @juan-mentor
    Posted 9 months ago

    Hola ,que tal Justina.

    • Tu solución de código QR es muy buena, pero si me lo aceptas, tengo alguna sugerencia para que sea superlativo.
      • Cuando delimites el ancho de una imagen en un contenedor, es mejor utilizar max-width.
          .image img {
                max-width: 100%;
                /* Con width la imagen se escala infinitamente aunque pierda calidad,
                     pero con max-width la imagen no se escala más allá del ancho máximo 
                     intrínseco de la imagen */
                     
           }
    
        - Cuando yo empecé, también trabajaba con px (unidad absoluta). Pero luego me di cuenta que utilizando rem, em, % (unidades relativas), la escalabilidad y el diseño responsivo era más flexible.
    
        - Lo dicho  **trabajo fenomenal** y sigue así que vas muy bien.
    
    • Un saludo.
    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