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

Responsive QRCode component design with html & css.

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

Solution retrospective


  1. I was unable to align the QR code component to vertically align center. Could some body give suggestions to achieve that.
  2. How to align the component header text and body text align center? (
<h3>Improve your front-end skills by building projects</h3> <p> Scan the QR code to visit Frontend Mentor and take your coding skills to the next level </p> ) 3) How to add multiple media queries to deal with various mobile screens? or can handle all mobile screens with single media query?
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

    Hello there 👋. Good job on completing the challenge !

    I have some suggestions about your code that might interest you.

    • You can use the text-align property in CSS to align the text:

      .QRBody p {
          text-align: center;
      }
      
    • To add multiple media queries to deal with various mobile screens, you can use the @media rule. This rule allows you to specify different styles for different media types/devices. e.g:

      Note: This challenge does not need to use media queries.

      @media only screen and (max-width: 30em) { 
          /* Styles for devices with a maximum width of 30em =  480px */ 
      } 
      @media only screen and (max-width: 48em) { 
          /* Styles for devices with a maximum width of 48em = 768px */ 
      } 
      @media only screen and (max-width: 64em) { 
          /* Styles for devices with a maximum width of 64em = 1024px */ 
      }
      
    • To center the component in the page, you should use Flexbox or Grid layout. You can read more about centering in CSS here 📘.

      Using flex:

      body {
          background-color: #d5e1ef;
          min-height: 100vh;
          display: flex;
          align-items: center;
          justify-content: center;
      }
      

      Using grid:

      body {
          background-color: #d5e1ef;
          min-height: 100vh;
          display: grid;
          place-content: center;
      }
      

      Using flexbox and margin:

      body {
          background-color: #d5e1ef;
          min-height: 100vh;
          display: flex;
      }
      .QRCodeContainer {
          margin: auto;
      }
      

    HTML 📄:

    • Always avoid skipping heading levels; Always start from <h1>, followed by <h2>, and so on up to <h6> (<h1>,<h2>,...,<h6>).
    • Since this component involves scanning the QR code, the image is not a decoration, so it must have an alt attribute. The alt attribute should explain its purpose. e.g. QR code to frontendmentor.io

    CSS 🎨:

    • You should use a CSS reset to remove the default browser styles and make your page look the same in all browsers.

      Popular CSS resets:

      • Reset CSS
      • "My Custom CSS Reset" by JoshWComeau

    I hope you find it useful! 😄 Above all, the solution you submitted is great!

    Happy coding!

    Marked as helpful
  • ricar1990•20
    @ricar1990
    Posted over 2 years ago

    hola, Un saludo desde Republica Dominicana.

    Yo lo haría de la siguiente forma.

    1- Según la solución el contenedor principal no esta centrado en la pantalla completa. puedes darle al body un display: flex; , align-items:Center; , justify-content: Center; , si no se alinea le daría un flex-direction: column; ,

    2- Tienes que darle un tamaño al contenedor con clase .QRBody pues si no le das un tamaño el contenedor crecerá de acuerdo al contenido, ve dándole un tamaño hasta que veas que el contenido quede igual a la imagen de ejemplo. También debes darle tamaño al h1 y los demás elementos. Tienes que utilizar el inspector para que puedas observar el tamaño de cada elemento porque mucha veces queremos centrar algún elemento dentro de un contenedor sin espacio interno disponible para poder centrar y ese espacio lo conseguimos asignando tamaño al contenedor.

  • Mohmed elshaarawy•830
    @MohmedElshaarawy
    Posted over 2 years ago

    Hi, dandamudi2 Good job on completing the challenge!

    I have some suggestions about your code that might interest you.

    HTML

    Use the <main> tag to wrap up all the main content of the page instead of the <div> tag. With this semantic element, you can improve the accessibility of your page. Use the <footer> tag to wrap the footer of the page instead of the <div class="attribution">. The <footer> element contains information about the author of the page, the copyright, and other legal information. Since this component involves scanning the QR code, the image is not a decoration, so it must have an alt attribute. The alt attribute should explain its purpose. e.g. QR code to frontendmentor.io CSS

    Instead of using pixels in font size, use relative units like em or rem. The font size in absolute units like pixels does not scale with the user's browser settings. This can cause accessibility issues for users who have set their browser to use a larger font size. You can read more about this here. Use min-height: 100vh instead of height: 100vh. The height property will not work if the content of the page grows beyond the height of the viewport. I hope you find it useful!

    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