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

QR Code displayer by CSS

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

Solution retrospective


How to accurately judge the measurements from a preview image only? I was confused that in the preview image box shadow is present or not. So how to judge more accurately the minor details of design which are not mentioned in the style sheet?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Juanca•220
    @juancaorg
    Posted almost 3 years ago

    Hi Akshat 👋,

    Answering your questions,

    Judging the measurements from a preview image only accurately is pretty hard.

    Ideally, you'll have the original design on Figma/Sketch/Adobe XD to work on, but if that isn't the case, you can leverage various tools for measuring.

    The one that I'm currently using and I would recommend (and found in the Frontendmentor Resources) is PixelSnap. It's pretty handy once you get used to it and has great tolerance config when the tool struggles to measure because of low contrast.

    Unfortunately, is a macOS exclusive and paid app. If you don't have the resources, the next best thing that I found is the web extension Dimensions. Available in Chrome and Firefox and is totally free. Of course, for this case, you would have to open the preview image in your browser to measure.

    Keep in mind the zoom level when measuring with these tools. These tools don't keep in mind the "real" dimension, they just measure whatever is on screen, so it can get tricky. Try to get the whole image on screen to get closer to the real dimensions when measuring.

    And again, this isn't a substitute for using the original design, but these are useful tools nonetheless.

    For minor details, like distinguishing if you should add a box-shadow or not, I use a color checker/picker to check for any contrast and to be sure if I should add one.

    The one that I'm currently using is Sip, again, macOS exclusive and paid app. But there's probably a web extension available in Chrome and Firefox, but I ignore which is the best, so I can't recommend any for now.

    And the last, for checking details in general, is just training your eye. The more you practice and the more more UIs you watch in general, the more details you'll spot.

    ~~Anyway, that's a lot of text. Sorry.~~ Hope this helps you out 🙌

    Marked as helpful
  • Adriano•42,890
    @AdrianoEscarabote
    Posted almost 3 years ago

    Hello Akshat Tiwari, how are you?

    welcome to the front-end mentor community.

    I really liked the result of your project, but I have some tips that I think you will like:

    1- All page content should be contained by landmarks click here

    2- Document should have one main landmark, you could have put all the content inside the main tag click here

    3- <html> element must have a lang attribute click here

    4- Page should contain a level-one heading, you could have replaced p.head with h1 click here

    I noticed that you tried to center the content using margin, always prefer to use flex-box or grid to center use margin only in the last case:

    withdrew:

    .main { /* margin: 150px auto 150px; */ }

    I added:

    body {
        display: flex;
        align-items: center;
        justify-content: center;
        min height: 100vh;
    }
    

    The rest is great!!

    Hope it helps...👍

    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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub