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

QR Code Component Challenge

Katarina Naskovikj•30
@KatarinaN98
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 of creating a clean and simple design for the QR code component, focusing on minimalism while ensuring the layout was responsive across different screen sizes. I also enjoyed using Flexbox for layout, which made centering and positioning elements much easier.

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

For this QR Code Component project, the main challenges I encountered were ensuring the layout was responsive across different devices and making the design simple yet effective. To overcome the responsive issue, I focused on using Flexbox for better alignment and positioning of elements. I also spent extra time testing the component on different screen sizes to ensure a smooth user experience. The challenge of simplicity in design was tackled by sticking to a minimalist approach and avoiding unnecessary elements, focusing solely on the QR code and its surrounding layout.

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

CSS Structure and Efficiency: I’d like suggestions on how to organize my CSS more efficiently, especially for responsiveness. Are there any best practices for keeping stylesheets clean and minimizing redundancy?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dangelo•440
    @Dangelobast
    Posted 5 months ago

    Keep it up !

    1. Once you get comfortable start using responsive units, avoid using px since it can complicate your life when doing responsive.
    2. Do a global reset, something most people do automatically when starting CSS rules. *{ margin:0 padding:0 box-sizing:border-box;} That way you ensure there is no extra padding or margins applied to elements as well as changing how width and height are calculated, if you don't use border-box you if you set a box to 20px and padding to 2px, in reality, your box is not exactly 20px, and you will have to add that padding too, with border box it's already included and it's "forced" to be 20px, search some info about it. and * selector is just to select every single element
  • P
    SKszymek•180
    @SKszymek
    Posted 5 months ago

    When you gives some element fixed width you should always use the max-width property, not width. Go check how the element behaves after changing width with max-width on the different screen sizes.

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