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

QR Code Component

adityaac7•30
@adityaac7
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 starting and finishing my very first solo project without any given solution. It was a significant milestone in my learning journey, and it demonstrated my ability to apply what I have learned to create a functional web component from scratch.

Next time, I would focus on enhancing the project by making it more dynamic. For example, I would explore adding functionality that allows the QR code to be generated based on user input, making it more interactive. Also, I would invest more time in refining the design and user experience, ensuring that the component is not only functional but also visually appealing and intuitive to use.

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

Centering the component in the middle of the page was a significant challenge. While centering it horizontally was straightforward, I struggled with vertical centering. I tried several techniques I knew but couldn't achieve the desired result (For e.g, flexbox align-items. I'm not sure why it didn't work but it just didn't). Eventually, I sought help from a senior developer who shared an article about CSS centering, which helped me overcome this issue.

Another challenge was making the entire page a single color. I discovered that the element only extends as far as the content within it, which meant it didn't encompass the whole page.

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

I would like help mainly on improving my CSS syntax. Much of my CSS is written through trial and error, and I'm aware that there are likely better and cleaner ways to achieve the same results. Specific feedback on best practices, more efficient ways to write my styles, and advice on organizing my CSS would be incredibly valuable. Additionally, I'd appreciate any suggestions for optimizing the performance of my CSS.

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 adityaac7'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.