Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 6 months ago

QR code component

RoxanaAnamariaTurc•40
@RoxanaAnamariaTurc
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?

I am refreshing my skills after holidays and I am happy to see that they are not so rusty. Even if this is just html and css it felt good to complete it and feel the reward of a task done.

What challenges did you encounter, and how did you overcome them?

This challenge was quiet easy, what I research about a bit was the media queries , but then I realise I dont need it with the flexbox as when I tested the component on a smaller screen was looking as expected.

What specific areas of your project would you like help with?

Feedback is always appreciated. If I can write the styles in a more elegant way or the html itself, I would like to hear opinions.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Keith•190
    @KeithEsc
    Posted 6 months ago

    Nice work. I messed with your CSS a bit to center the positioning of the component:

      html, body {
      background-color: #d5e1ef;
      height: 100%;
      margin: 0;
      padding: 0;
    }
    
    main {
      display: flex;
      flex-direction: column;
      align-items: center;
      height: 100%;
      justify-content: center;
      margin: 0;
      padding: 0;
    }
    
    img {
      width: 288px;
      height: 288px;
      margin-bottom: 24px;
      border-radius: 10px;
    }
    
    section {
      display: flex;
      align-items: center;
      flex-direction: column;
      background-color: hsl(0, 0%, 100%);
      padding: 16px 0 16px 0;
      width: 320px;
      border-radius: 10px;
    }
    
    h3,
    p {
      text-align: center;
      font-family: "Outfit", serif;
    }
    
    p {
      size: 15px;
      color: hsl(216, 15%, 48%);
    }
    
    .attribution {
      text-align: center;
      size: 10px;
      color: hsl(216, 15%, 48%);
    }
    
    • Main changes are assigning html and body a height. Which then lets your <main> take up the entire height of the screen. This allows justify-content: center; on <main> to center your <section> vertically.

    • flex; 1; changes the behavior of justify-content so I went ahead and removed it. It also didn't impact the design as far as I could tell.

    You could opt to use a <div> with the class of "container" instead of styling a <section> tag (then move your CSS to .container). This is what people would normally suggest.

    Marked as helpful
  • Saeed Abedini•80
    @Saeed-Abedini
    Posted 6 months ago

    Everything is great, but compared to the design pattern, it is not vertically in the middle of the page and the footer should also be at the bottom of the page.

    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