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

qr code

Ali-software-development•20
@Ali-software-development
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Im not sure if I did the sizing write?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aimal Khan•2,260
    @Aimal-125
    Posted about 2 years ago

    Bro in your CSS code, try padding: 1rem; to <body> tag. Because when i rotate my mobile in the landscape orientation your card is attached to the top and bottom of body. By giving padding to the body element it will push the card and will look good on small heighted screens.

  • P
    Prince Awuah Karikari•170
    @PRINCEKK122
    Posted about 2 years ago

    Congratulations on completing your first challenge.

    I saw a couple of things in your code that I would like to share with you.

    Firstly, although it accepted to mix HTML and CSS in your html file, it considered a bad practice as this violates the Separation of Concern in programming. To be specific, avoid at all cost styling in your HTML file and do this in your CSS file as you have done already in the stylesheet.css file. So cut the code in the body element's style attribute, and paste it in a ruleset in the CSS file.

    Also, I think your code is a little bit hard to read because it not formatted properly. A quick fix is by installing Prettier plug in, and turning on auto save feature if you are using VS code, to format your code properly.

    Also for the layouts, you can consider learning more about Flexbox and CSS Grid. You can learn about them on freecodecamp.org, as centering elements vertically with Display positioning and translate property is quite tricky.

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