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

QR Code Component

Ayoola Emmanuel•10
@Ayoola-Emmanuel
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please, I can't seem to get the media query right. Can anyone help?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Carlos Henrique•200
    @devriquesant
    Posted over 2 years ago

    Hello Ayoola-Emmanuel

    Congratulations for completing this challenge!!

    ✏️ Here is a possible answser to your question, but before, here are some tips and suggestions for this and your future projects ;) ✏️

    1. 🚀 Contain your "main" content in a "main" tag:

    • <main> is a semantic element from HTML which provides accessibility and organization for your web page;

    • semantic elements provides detailed info about the contents in your page.

    • Others semantic elements includes: <header>, <footer>, <figure>, <figcaption> ...

    • To implement this, you should exchange the <div class="book"> for <main> and wrap all the necessary and main content of your page

    • Start practising it and you will be more familiarized to do it in future projects.

    2. 📱 Build a responsive web page:

    • The use of px unit to dimension your components in the page gives it a appearance of static.

    • To build a more responsive one, you should start to use relative length units to adequate the page components to a device screen.

    • That's why your media query is not working!!!

    • You made it work in the screen dimension in a certain range, but there is a lack of use of these relative units, as vw or vh, that makes the web page more responsive, try it with few components like a div and then expore to more components! :)

    • To deeper details, take a look at it

    Overall you did a good job!! Keep coding!! I'm sure you will discover new things and become even better

    Here, take a star for achieving it: 🌟 <- it's a glowing star if you're seeing a rectangle :)

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