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

QR Code Component with Pure CSS

MasonCleverBJ828Coder•20
@MasonCleverBJ828Coder
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 am most proud of how I was able to structure the HTML semantically, ensuring the content is well-organized. I also successfully implemented Flexbox for centering the content and making the design responsive, which I hadn't worked with much before. Additionally, I maintained clean and simple code, which improved the maintainability of the project.

For future projects, I would experiment with more advanced CSS techniques like Grid Layout, which I think could be helpful for larger layouts. I would also focus more on optimizing the project for mobile-first design by starting with mobile styling before moving on to desktop adjustments, rather than making all of the adjustments together. Additionally, I would try to make the design even more interactive by adding hover effects or animations for a more engaging user experience.

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

Ensuring the component was responsive was also a challenge. This was managed by avoiding hard-coded pixel values and instead using relative units for better scalability across different screen sizes.

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

I would appreciate help with the following areas of my QR code component project:

I would like feedback on how to make my HTML and CSS cleaner, more efficient, and better structured. Since I am getting back into frontend development after a break, I am not always sure if I have written things correctly or if I have added unnecessary code.

I would like to explore adding more interactive features to the QR code component, such as hover effects or animations, to make the user experience more engaging.

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

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.