Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Responsivre QR code card using flexbox

Rehan•10
@rehanmm
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What did you find difficult while building the project?

Text was not adapting according to screen size

Which areas of your code are you unsure of?

It seems that i am applying padding and margin randomly completely based on hit and trial

I am unsure about when it preferred to use margin and padding what convention should be used

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • shalash23•280
    @shalash23
    Posted over 2 years ago

    Congratulations on your first project.

    • Regarding the responsive typography, I found a little trick really eliminates all the headache regarding responsive typography, it is called "clamp". There is a website that I use that actually calculates the values and gives me the final clamp values to apply to font-size. Here is a link: https://royalfig.github.io/fluid-typography-calculator/

    I am quite sure this will make your life a lot easier. After finding this trick, I never write media queries for fonts.

    • I will explain this as easily as I can. I have a box, how much of the inside of the box should the content take? that's padding. How far is the box from other boxes? that's margin. When to use when? It all depends on the design, I think. But for arguments sake, let's say you have a header section that contains a logo and a hamburger icon. The header element is taking all the space. With padding, you can specify an "inner margin" you can say to those child elements. Margin comes in when you want to separate the header section from another section. There are situations where you actually have to use both, but I'd say don't complicate things at the beginnings.

    My two cents here, is that CSS requires some hit and miss until you get a grasp on how it behaves. I am sure it drove everyone who is learning it crazy at one point.

    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