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

Responsive QR Code Component | Using HTML and CSS

Zahra Ehsani•110
@ehsanidev
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 created and completed this project in an hour and a half, and that’s something I’m proud of.
This project was made responsive using Flexbox, and I’m considering using Grid for responsiveness next time.

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

The paragraph was not adhering to the layout as intended, and the size it was supposed to be was 15 pixels. The issue was not with the font size, but rather with not assigning a width to the container.

To make it responsive, the first unit that came to mind was percentage (%). However, on mobile sizes, the container looked like a thin bar. So, I decided to change the unit from percentage to rem, and fortunately, the appropriate width was achieved.

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

I would really love to get your feedback on how I’ve handled styling in the CSS file.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Amir_mohammad•100
    @Amir-mohammad-ahmady-1234
    Posted 4 months ago

    It was a really good job. But for me there is a problem with the display and responsive display. If you fix it, it will be even better!

    Marked as helpful
  • P
    laurice-dev•300
    @laurice-dev
    Posted 4 months ago

    You did a wonderful job with your project. I loved how you used variables for your CSS styling which makes things very easy to understand. One thing that we could update is to use less IDs because they have a high specificity and can only be used one time within a project. I would use classes instead of IDs for project scalability. You did great! Kudos!

    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
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