Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

A responsive QR code component

Divya•50
@Divya4879
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 most proud of just simply starting this project, and most particularly this platform. Although I've known about it for a really long time, I'm just starting this now. As for this particular component, I'm proud of making it, within my estimated time range.

As for the next time onwards, I'll draw a rough wireframe of the component/site before its coding. Coz this time, I had a little rough start coz of not doing it.

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

As it was the 1st challenge, this one wasn't hard per say. But as I mentioned earlier, I had a little rough start coz of not making the rough wireframe before going on with the code part.

I overcame this challenge by screenshooting the desktop version design and then using it for reference, multiple times.

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

I would appreciate reviews and feedback on my code, like the better/shorter/more efficient method for the functionality, and regarding the responsive part of my design as well.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sonu Swapan Dutta•530
    @Sonu-Dutta
    Posted about 1 year ago

    Hey! Good solution, I would like to suggest you to use display: flex property. You can get more information on this from -> https://www.w3schools.com/css/css3_flexbox_container.asp

  • Vishal D.•810
    @Hummingcoder
    Posted about 1 year ago

    Give the card padding of 1rem(16px) or more, and give the card a width of 375px and 90% width for screens smaller than 375px.

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