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

Responsive Card-QR-View

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

Solution retrospective


¿Qué encontraste difícil mientras construías el proyecto? No me pareció difícil este reto, estuvo bastante fácil

¿Tiene alguna pregunta sobre las mejores prácticas?

Me gustaría obtener sugerencias, consejos o criticas constructivas de como podría mejorar mi CSS o mi HTML

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Melvin Aguilar 🧑🏻‍💻•61,020
    @MelvinAguilar
    Posted over 2 years ago

    ¡Hola! 👋. ¡Buen trabajo al completar el desafío! Tengo algunas sugerencias sobre su código que podrían interesarle.

    • El atributo alt debería explicar el propósito de la imagen. Al escanear el código QR, el usuario será redirigido al sitio web frontendmentor.io, por lo que un mejor atributo alt sería qr code to frontendmentor.io.

    Si desea obtener más información sobre el atributo alt, puede leer este artículo. 📘.

    • Establecer el ancho del componente con un porcentaje o una unidad de vw se comportará de manera extraña en dispositivos móviles o pantallas grandes. Debe usar un max-width de 320px o 20rem para asegurarse de que el componente tendrá un ancho máximo de 320px en cualquier dispositivo, también elimine la propiedad width con un valor porcentual.
    • ¿Por qué has utilizado etiquetas en español? <enlace rel="preconectar" href="https://fonts.googleapis.com">.

    Espero que te sea útil! 😄 Por encima de todo, ¡la solución que has presentado es genial!

    Saludos

    Marked as helpful
  • Sandro•1,150
    @sandro21-glitch
    Posted over 2 years ago

    Hi Ower

    Here are some suggestions for your code

    Use semantic HTML tags: Instead of using div tags, you can use appropriate semantic HTML tags like header, section, and footer for the different sections of your code.

    Consider using a CSS reset to ensure that all browsers display the elements in a consistent way.

    Use rem units for font-sizes instead of px, so that your text resizes proportionally with the user's browser font-size setting.

    Use class names that are more descriptive, for example, instead of "general", you can name it "card-container".

    Use CSS shorthands for multiple properties with the same value, for example, instead of "margin-top: 5%; margin-bottom: 15%", you can use "margin: 5% 0 15%".

    Happy Coding

    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

Oops! 😬

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

Log in with GitHub