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

Responsive Landing Page using media queries

Chisom Ohanu•20
@Chiblessed
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


During this, I found making the QR component responsive as every screen has a different width and targeting this width can be difficult. Personally, I am not sure of the responsiveness of this project on mobile.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Olaniyi Ezekiel•7,580
    @Ezekiel225
    Posted over 1 year ago

    Hello there 👋 @Chiblessed.

    Good job on completing the challenge !

    Your project looks really good!

    I have suggestions about your code that might interest you.

    Consider changing the background-color of the body element to hsl(212, 45%, 89%).

    body {
      background-color: hsl(212, 45%, 89%);
    }
    

    I hope it helps!

    Other than that, great job!

    Happy coding.

  • Dêvid Teófilo•240
    @devid8642
    Posted over 1 year ago

    Firstly, congratulations on the solution.

    I have some suggestions for your project:

    Consider structuring all the content on your HTML page using semantic tags, in this case <main> and <article> for the card. See more about semantic tags here.

    It's not interesting to use tags like <br> to position like you did, consider doing this in CSS because it breaks your layout. As you centered the card using position, depending on the display, the texts may end up leaving the card.

    I recommend that you remove the <br> and to center the card use the following, considering the card inside <main>:

    main { /* or .container */
       display: flex;
       align-items: center;
       justify-content: center;
       min-height: 100vh;
    }
    

    Centering the card without using position and removing <br> will certainly ensure that the layout is more uniform across existing display varieties and facilitate responsive design.

    Even though you applied the sources to the project, you did not upload the assets directory to GitHub and therefore they do not load on the page.

    As this is a simple project, the responsive design probably became a problem due to the layout techniques you chose to use, I recommend using flexbox to center the card and without using <br> to position the texts (research the property text-wrap) you probably won't even need to apply any additional CSS rules in the mobile media query, just change the width of the card.

    I hope you found my comment useful, again congratulations on the solution.

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

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