Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 7 months ago

Responsive QR code

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

Solution retrospective


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

I have tried fixing semantics,, Please let me know if anything can be done to improve the solution.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Trần Thành Danh•1,500
    @TranDanh1122
    Posted 7 months ago
    1. you review code must be your repo url, not profile
    2. let use fontface to load font, not import
    3. image need object fit, and if can, add aspect ratio
    4. let reset css first (*{margin 0 pading 0 boxsizing border-box}), that will help you control spacing.
    5. remember, display flex on your body maybe cause missing content on mobile device if your card higher than 100vh

    hope that help!!!

  • Ardian Wicaksono•70
    @Ardianwi
    Posted 7 months ago

    your size is'nt same with design..you can download the design in file design figma..

  • Jordan Bugglin•410
    @Jbugglin
    Posted 7 months ago

    The border-radius on the main card looks to be a bit too sharp, might need to increase that value to get a more rounded corner. I like to take the value for the outer radius on the main card and halve it to get the inner radius for the image. That way the corner looks to be a more consistent thickness throughout.

    Source: https://www.uidesign.tips/ui-tips/border-radius-consistency

    Your box-shadow is a bit too dark, not blended as much as the design calls for, nor drops as far down. The values you have is 0px 0px 7px 1px $paraColor. If you want to apply a simple box-shadow, remember that the first value is the offset-x, second is offset-y then blur-radius value and color, no need to overcomplicate it.

    Source: https://developer.mozilla.org/en-US/docs/Web/CSS/box-shadow

    As for the h1 and paragraph elements, just adjust the width of the elements to match that of the design.

    You did a great job and keep it up!

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

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