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

QR code. Basic version using CSS and HTML

P
Alex•60
@aseptimu
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Align center using flexbox and height styling of html and body tags.

What challenges did you encounter, and how did you overcome them?
What specific areas of your project would you like help with?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Øystein Håberg•13,260
    @Islandstone89
    Posted over 1 year ago

    HTML:

    • The text in the footer must be wrapped in a <p>.

    CSS:

    • It's good practice to include a CSS Reset at the top.

    • Remove the height on html.

    • Change height on body to min-height: 100vh.

    • box-sizing: border-box should be set on *.

    • body should not have a max-width.

    • Remove font-style: normal, as that is the default value.

    • The card must not have a fixed width. Instead, add a max-width of around 20rem - this prevents the card from getting too wide on larger screens.

    • As you have set box-sizing: border-box higher up in the DOM, it is already inherited by main - hence there is no need to declare box-sizing: inherit.

    • On the image, add display: block and replace width with max-width: 100% - the max-width prevents it from overflowing its container.

    • Since all text should be centered, you only need to set text-align: center on the body, and remove it elsewhere. The children will inherit the value.

    • font-size must never be in px. This is bad for accessibility, as it prevents the font size from scaling with the user's default setting in the browser. Use rem instead.

    • On the paragraph, remove font-family: 'Outfit', font-weight: 400 and font-style: normal. The font-family is inherited from the body, and the two other properties are default values of a paragraph. It should also not have a fixed width. To limit the length of the text, use padding-inline or a max-width of around 25ch.

    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
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