Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 18 days ago

QR component using basic CSS

P
Bára Kalvodová•70
@BaraKalvo
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 think the result looks the same as the Figma design, including the spacing between elements, which is what I'm most proud of. For now, I'm happy with how it turned out.

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

To me, the largest challenge was the spacing between elements. All the time, I'm not sure if I should use margin or padding and which one would be better. I studied more about spacing and how to use both properties and I did my best to make my design match the one in Figma.

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

I'm not sure about using the margin and the padding correctly. My design matches the one in Figma, but as for those two properties, my CSS code looks a little bit chaotic to me. I feel like there are too many margins and paddings:

.container {
  margin: 60px auto;
  padding: 16px 16px 40px 16px;
...
}

.text-area {
  padding: 24px 16px 0 16px;
...
}

.text-area__title {
  margin-top: 0;
  margin-bottom: 16px;
...
}

.text-area__text {
  margin: 0;
...
}

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•7,050
    @MarziaJalili
    Posted 18 days ago

    Beautifully done! 👑

    Some tips?

    ✅ You could set some padding to the body element so it will look even better on mobile. Because now it’s stuck to the left of the page, man.

    ✅ There is a shorthand property for settling the top and bottom margins:

    /* Same values */
    margin-block: 10px;
    
    /* Different values */  
    margin-block: top bottom; 
    margin-block: 0 16px; 
    

    ✅ The same could be applied for padding:

    /* Same values */
    padding-block: 30px;
    
    /* Different values */  
    padding-block: top bottom; 
    

    ✅ Also, avoid using px for font-size, bro. It happens to cause some issues, and you can use rem units instead.

    Great work overall, keep it up!

    😎😎😎

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