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

QR Code Card

fvdumah•100
@fvdumah
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 it looks pretty similar to design, so happy with that :)

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

I struggled with vertically centering the card with flex, however I was not defining the height, once I added a 100vh it became centered.

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

I'm not sure on when to apply margin to items versus using padding. I feel like I can get same result with using either, unsure if it would be better practise to use one over the other?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•3,130
    @Alex-Archer-I
    Posted about 1 year ago

    Hi! First of all - your solution is cool, and, yeah, quite similar to design =) Good that you are add * {margin: 0} - I always forget about it. Also you are using semantic tags which is great.

    As for margin vs paddings it is really not a big deal in this example (except one thing called "margin collapse" which can be useful when you are familiar with it, but annoying at first). But when you'll stylize elements with visible borders and backgrounds padding will be needed to expand the inner space of element not for creating gaps. I mean stuff like inputs and buttons where you don't want text to stick to borders. Sorry, if you are already know about all this - I don't know on which level you are now.

    As for me - I prefer flex and gap to create, well, gaps, but this is working only if you need equal gaps.

    And also I want to tell you about img - it doesn't maintain it's proportions on small screen. Try to not indicate height, but only weight - it'll hold square proportions.

    Well, I hope I told you something useful =) Keep doing great stuff and good luck!

    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