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

Centered QR code component

bem, sass/scss, gulp
Mr Rabbit•1,020
@rabbitmaid
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I updated my challenge and added a gulp workflow

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    👾Hello , congratulations for your new solution!

    To create box-shadows its kinda tricky if you create it using only the coding line, my advice for your is create the shadows using Figma where you create the shadow design and just drop the code, the devtools in Google Chrome where you can manage the shadow values.

    Anyway the value for the shadow is: box-shadow: 5px 5px 15px 5px rgb(0 0 0 / 3%);

    If you're not familiar to Figma you can use this online tool to create your shadows: https://www.cssmatic.com/box-shadow

    👋 I hope this helps you and happy coding!

    Marked as helpful
  • Pulkit saxena•870
    @Pulkit-s21
    Posted almost 3 years ago

    @Agbortoko imo the best way to do this challenge is by using display:grid

    1. Place the qr code and text in seprate divs and both the divs in one container and apply grid to it with grid-template-columns: repeat(1,1fr).
    2. For the box shadow apply it to the container and the challenge will be done.
    3. At last just set max-width on the container to around 35 rem or so Ig but that can be done with trial and error method
    4. To center the container use display:flex min-height:100vh justify-content:center align-items:center to the body
    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