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

qr-challenge-html-css

Lê Đức Long•10
@lelongrvp7
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My first try on this challenge. Happy to get some feedbacks. Thanks!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Hassia Issah•50,390
    @Hassiai
    Posted over 2 years ago

    replace <div id="container"> with the main tag to fix the accessibility issues. click here for more on web-accessibility and semantic html

    To center %container on the page, add min-height:100vh; display: flex; align-items: center: justify-content: center; or min-height:100vh; display: grid place-items: center to the body.

    To center #container on the page using flexbox:
    body{
    min-height: 100vh;
    display: flex;
    align-items: center;
    justify-content: center;
    }
    
    To center #container on the page using grid:
    body{
    min-height: 100vh;
    display: grid;
    place-items: center;
    }
    

    Increase the padding value for #card . padding: 15px

    Give h1 and p the same font-size of 15px and the same margin-left, margin-right and margin-top values. Give p a margin bottom value.

    Use relative units like rem or em as unit for the padding, margin, width values and preferably rem for the font-size values, instead of using px which is an absolute unit. For more on CSS units Click here

    Hope am helpful.

    Well done for completing this challenge. HAPPY CODING

    Marked as helpful
  • Sandro•1,150
    @sandro21-glitch
    Posted over 2 years ago

    Hi Lê Đức Long

    Here are a few suggestions for improvement your code

    HTML

    Use semantic HTML elements:

    Instead of using a div for everything, use semantic HTML elements such as header, nav, main, section, etc., to better describe the structure and purpose of your content.

    CSS Consistent naming convention:

    Consider using a consistent naming convention, such as BEM (Block, Element, Modifier), to keep your CSS organized and avoid naming conflicts.

    Reusable classes:

    Create reusable classes for styles that are used multiple times in your code. This will make it easier to maintain and update your styles.

    Use CSS variables:

    Consider using CSS variables to store values that are used multiple times in your code, as this makes it easier to maintain and update your styles.

    Minimize the use of hard-coded values:

    Instead of hard-coding values, consider using relative units such as em, rem, vw, vh, etc., to make your styles more flexible and adaptable to different devices and screen sizes.

    Happy Coding

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub