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

SCSS and vw unit for responsive

sass/scss
ScrimaliAnthony•20
@ScrimaliAnthony
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everybody.

How do you decide the size of your components by having an image as a model? do you use an extension on your browser? Or is Figma essential?

Thanks in advance

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Brian Michael Poblete•490
    @Brian-Pob
    Posted over 2 years ago

    Hello there ScrimaliAnthony 🙋‍♂️! Great job on this challenge 🎉!

    That's a good question! When determining sizes for components based on a given design, mockups presented through something like Figma are definitely useful as we have exact fonts, colors, pixel sizes, etc. In my web development work, however, sometimes all I receive are PDFs or images.

    With this challenge, you may need to just give your best estimation to get sizes right. I learned that 99% of the time the apps you make won't match the mocks exactly. This might be due to a lack of time, budget, or knowledge. But that's ok!

    If the clients/ stakeholders are satisfied then you have accomplished your job.

    Of course, there are some best practices you can follow like making sure text is spaced enough according to accessibility standards. Accessibility (also referred to as a11y), is actually a great place to start off when you're not sure about things like sizing.

    Resources you might find useful 🔗:

    • Accessible line-height

    • Contrast Checker

    I hope this helps! ✌️

    I look forward to seeing more of your work in the future! 😄

    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