Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Responsive web page using viewport

John Michael Mapilisan•30
@mikowesome
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Need help in setting page width for desktop and mobile.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Chyunjet•620
    @Jetyun
    Posted almost 3 years ago
    1. For mobile, maybe you want to set the container width to be smaller than 350px, because in the design, it seems that there is still some space to see the light blue background color due to the design smaller width.

    2. For desktop, you can put @media screen and (min-width: 1440px){} and put the css setting in the curly bracket. When you use F12 and amend the screen width to 1440px, you will see the changes. This is called media query. maybe you want to watch youtube dave gray tutorial on media query to learn more.

    • in addition, I think you accidentally insert the paragraph into your footer.
    • If you want to you can delete the style tag in HTML and put the .attribution css styling into css file. This is not wrong, but I think it would be a hassle to look for the css styling in future if the styling is not all included in the CSS file (Other challenges may require you to wrote a longer CSS file)
    Marked as helpful
  • David•7,960
    @DavidMorgade
    Posted almost 3 years ago

    Hello John, congrats on your first Frontendmentor challenge!

    In this case seems that your component is already responsive, but for future and larger projects I would recommend you to use relative units such as rems / % instead of pixels, also try to use a reseter stylesheet such as normalize, that will help you reseting the default styles of the browser, like the body margin. You can get normalize here

    For next projects try using a bit more semantic tags, like main, section and footer, in this project since is a little component in not that important, but it can help you a lot for your future projects!

    Hope my feedback helped you!

    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

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