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

QR Code Component using CSS custom properties

Dineo Mashaba•40
@dineo-matla
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?

Coding my first project without tutorials has given me a tremendous sense of accomplishment and confidence. I've realized that I'm capable of learning and adapting quickly, even when faced with unfamiliar concepts or technologies. This experience has shown me that I can trust myself to figure things out and create something meaningful.

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

One of the biggest hurdles I faced while working on this project was mastering version control using the terminal. As someone who was new to this method, I found it daunting to navigate the command line interface and make commits. However, I was determined to push through the learning curve. I turned to external resources like YouTube tutorials and online forums such as StackOverflow to help me better understand the concepts and troubleshoot issues. I spent quite some time watching videos and seeking guidance from experienced developers.

Through persistence and practice, I slowly began to feel more comfortable using the terminal for version control. I learned to appreciate the power and flexibility of Git and how it could help me manage my codebase more efficiently. The breakthrough moment came when I finally understood the concept of staging, committing, and pushing changes. It was a eureka moment that made all the struggles worth it. I felt a sense of accomplishment and confidence that I could tackle even more complex challenges.

I also struggled with file paths as my image was breaking. When I finally figured out how to fix the file paths and get my image to view on the local file, that boosted my confidence even further. However, once, I deployed the solution, the image was still breaking, I have yet to figure out how to solve that one :(

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

I struggled with file paths as my image was breaking. When I finally figured out how to fix the file paths and get my image to view on the local file, that boosted my confidence even further. However, once, I deployed the solution, the image was still breaking, I'm yet to figure out how to solve that one.

What can I do to stop my image from breaking once it's been deployed? The file path issue was fixed for the image to be visible on the local file, but how can I fix it so the image is visible on the live site?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Dineo Mashaba's solution.

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 1st-party linked stylesheets, and styles within <style> tags.

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.