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

QR Component Card - Second Solution

P
Jeff Guleserian•500
@jguleserian
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?

While this is an easy challenge, I wanted to take the opportunity to pass through each of the Frontend Mentor learning paths. This was the first project required, so I decided to challenge myself to see how quickly I could create the component. I was very happy with my time. Then, I decided to add a couple of extras: turn the QR code into a live link (for those who would view it on a computer screen, but didn't want to go to the site on their cell phone) and add a drop-shadow hover effect.

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

No challenges in this project since I have done it before.

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

What I would like help with is understanding GitHub more and becoming more proficient in utilizing what it has to offer. I find that I struggle with having a design work fine in my browser, but when it is published from GidHub Pages, the effects don't work or the image does not show up. I have reduced my frustration by avoiding the leading "/" in references to images or stylesheets but it still does not seem to work in every circumstance. If anyone has some better insight on this, I would really appreciate your help. In fact, if you have any suggestion at all, I would love to hear it.

Happy coding!

Jeff

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nandhakumar•50
    @nandha126
    Posted 12 months ago

    Your solution is a solid start with clear structure and styling.

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