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

QR Code Challenge

Bekezela•10
@bekezela
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?

Clean code and it's well identified.

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

When I styled the main background of the document, the text on the top container had the background highlighting of the same backgroundColor. So, I removed the highlight by styling the text back to white. Not sure if it's the right thing to do.

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

Deep understanding of Media Queries in CSS.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Eden Wong•110
    @EdenWong0
    Posted 3 months ago

    Can remove any unnecessary content such as the footer. Also, might need to add border-radius to the card as well as the size of image to match the design. The font size, font weight, and color for the heading and paragraph should also be changed to match the design.

  • Sonny Stark•30
    @sonnystark
    Posted 3 months ago

    I would look over the naming of elements and classes. Also, if you don't have a H1 or H2, don't start with an H3. It's the only heading there so make it a H1.

    The styling is interesting. Maybe you should go over it and really see what everything is doing. Just one very obvious thing is the <div class="attribution"> that is wrapping everything and styled with a pointer as a cursor. Why? :)

  • P
    Nick J•100
    @troy71
    Posted 3 months ago

    Fantastic effort, well done !

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.

e-dimensionz Inc

e-dimensionz Inc. is a Canadian web development company specializing in custom websites, applications, and eCommerce solutions. We work with businesses of all sizes to deliver high-quality, scalable, and maintainable digital projects, with a focus on clean code, strong user experience, and long-term client relationships.

Learn more

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub