Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 18 days ago

QR code component using Flexbox and custom box-shadow

Takshil-P•10
@Takshil-P
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm proud that I finally overcame the fear of starting and completing a project. This was my first Frontend Mentor submission, and I learned how to center elements using Flexbox and style components using shadows and custom fonts.

Next time, I would try not to rely on external help too early. I want to build more confidence by solving layout issues on my own first.

What challenges did you encounter, and how did you overcome them?

One of the main challenges was understanding how to inspect design dimensions from just an image. I used Figma to estimate the size of the card and padding. Another issue was unwanted space below the image, which I fixed by using display: block on the image tag.

Also, I was initially nervous to even start the project, but breaking it down step-by-step helped reduce the fear.

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

I'd like feedback on my use of pseudo-selectors like :first-child and :last-child for styling elements. Is that a reliable method in professional projects, or should I use class-based selectors?

Also, any tips to make my layout more responsive without using media queries would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mustafa Sen•2,690
    @mustafasen97
    Posted 18 days ago

    Your design is great. Feel free to use media queries. This is often necessary for responsive design.

    Is Using :first-child, :last-child Professional?

    • Yes, it can be used in professional projects.

    However, you should pay attention to the following conditions:

    When is it safe:

    • If the structure is static and will not change (for example, if there are 3 fixed blocks).

    • In semantically meaningful places like ul > li:first-child.

    When is it dangerous:

    • When the element order in the DOM can change (for example, if the list is sorted with JS).

    • When other developers will add to it later and rely on the order

    Suggestion:

    Selectors like :first-child, :last-child:

    • Should be used with utility or special class names,

    • Or in critical cases, should be overridden with the class.

    I hope this helps you. Good luck with your future designs.

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