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

Responsive QR Code Component

Dizzy_Sloth•50
@TotallySly
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I would like advice regarding Units of Measurement. I am not entirely sure which unit is the best and when. I have read a lot and it does appear to be a personal preference. I base this upon the many differing opinions.

I am yet to learn Bootstrap. And I only use 'vanilla' CSS (unless Flexbox is not considered 'vanilla'?!). I have read that, for the time it takes to learn Bootstrap, I should just consider continuing with more vanilla CSS and learn CSS Grid instead?

Thank you for taking the time to have a look at my work!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • kxnzx•870
    @kxnzx
    Posted over 3 years ago

    Hi @TotallySly,

    I would like to share what I have learned about Units of Measurements and how I use them + why:

    • REM Units for defining width’s of elements, margins, padding, and font-sizes (using this relative unit is important for accessibility settings, they adapt to the user's browser > people with visual impairment can zoom in to make the font-size/components on the screen bigger/smaller)
    • Pixels for shadows & borders (pixels are static > borders/shadows need to stay the same size always)
    • EM Units for media queries & padding in buttons (this is also a relative unit > the padding will auto adjusts to the font-size of the button)
    • % use this in combination with a max-width ( I personally mostly use this to define the width and min-height of the html element, you can also use vh or vw for this. However I have read somewhere that this is not the best practice to do yet)
    • CH Unit for defining the of width paragraphs

    There is a lot of info about this available, but this out of my head what I have learned for now. I hope you can get something out of this.

    Greetings, Kxnzx

    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