Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Responsive QR code site using CSS Flexbox

Hanna•10
@HannaNashita
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'm quite proud of how the finished project looks similar to the design challenge.

Next time, I'll try to make it look exactly as it should.

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

I'm a bit confused when choosing display value for wrapping/layouting the contents. Block, flex, or grid, not sure which one to use.

So I did some research about those values, and finally I decided to use flex. Because it seems easier for layouting columns or rows.

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

So I actually set the paragraph size to 13px and not 15px like how the style guide told me to do.

Because when I try to use 15px, it makes the paragraph look bigger than the heading and I have no idea why.

Here is my HTML code:

<section>
        <div class="qr-code">
            <img src="./qr-code-component-main/images/image-qr-code.png" alt="QR Code" width="100" height="100">
        </div>
        <div class="text">
            <h3>Improve your front-end skills by building projects</h3>
            <p>Scan the QR code to visit Frontend Mentor and take your coding skills to the next level</p>
        </div>
</section>

And here is my CSS code:

.text {
    text-align: center;
    margin-inline: 1.2rem;
    margin-block: 1.3rem;
}

h3 {
    color: var(--slate-900);
    margin-bottom: 1rem;
}

p {
    font-size: 13px;
    color: var(--slate-500);
}
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•9,390
    @MarziaJalili
    Posted about 1 month ago

    Welcome! Algorithms reign supreme here! 🎉🥳🎉

    🤔 The reason you're encountering the font size issue is because the designer wanted you to use the <h1> element, which by default has a larger font size than the <h3> element, and therefore, you don't get the intended match! 😳

    🌟 But a quick win for responsiveness?

    ✅ Using pixels for font size is not a good idea because it doesn’t adjust well on different screen sizes or when users zoom in.

    ✅ It's better to use units like em or rem so the text can resize more easily and stay readable.

    ✅ Here you go with an example:

    p {
      /* Instead of this...*/
      font-size: 16px;
    
      /* Try this...*/
      font-size: 1rem;
    }
    

    So you could take that num in pixels and divide it by 16 to get the rem value, using calculator of course. 😅

    Well-played overall — keep being awesome! 😎🔥🥇

    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

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