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

Responsive QR Code Component

2trill2code•70
@2trill2code
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • Are there better ways to do a simple CSS reset?
  • Is there a better way to vertically and horizontally centre a div?
  • How was the HTML? Was it semantic enough? How about the class names were they also semantic?
  • Should all text type elements p, h1 etc. have class names?
  • Is it a good practice to specify something like h3 compared to .container h3 if you know that one h3 will be on the page?
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • YOPA SEREINA•100
    @BRENHINES
    Posted over 1 year ago

    Hello, your code is well written. As for how to do CSS resets more simply, I don't think there is a simpler way to do it. But if you fond another way to make it simply, please can you share it ? And flex is the simplest way to center a div.

    Your Html is quite semantic but the classes names, I find them a little disorganized and non-specific, have you ever tried to learn the formatting of class names?

    For SEO you should have an H1 for the title because it will be more referenced.

    Best wishes.

    Marked as helpful
  • myrh•100
    @myrhisyoinked
    Posted over 1 year ago

    I prefer to use this method to center container vertically & horizontally

    body {
      display: grid;
      place-content: center;
      margin: 0;
      min-height: 100vh;
    }
    

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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