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

QR Code Component

P
Anjelica•160
@Anjie-MF
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'm most proud that this time around, I understood the code I wrote. A year ago, I completed this same challenge by copying parts of someone else’s solution, but I couldn’t tell you why it worked. This time, I rebuilt the solution using a Figma file and my own knowledge, and I can now confidently explain each part of the layout. That’s a huge win.

If I did this again, I’d probably simplify my structure earlier and rely more on fundamental layout principles instead of overcomplicating things. I also want to work on trusting my design instincts more — the Figma file gave me a taste of professional tools, and I’d like to get even more comfortable with that workflow.

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

Centering the card on the page gave me a surprising amount of trouble. It seems like such a basic layout goal, but I kept missing the key layout properties — like setting the body to min-height: 100vh and using flexbox to center everything. I revisited my old solution for clues, and while it helped, it also reminded me how much I’d relied on copying code without understanding it.

This time, I leaned into problem-solving: I used my notes, searched through MDN docs, and asked ChatGPT — but instead of copying the answers, I took the time to understand them. I even voice-recorded myself thinking out loud, which helped me clarify my thought process and track how long the project actually took.

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

Right now, I’m focusing on getting really solid with HTML and CSS fundamentals. I’ve started going through the full Frontend Mentor Learning Path again — this time with intention. I’d love feedback on how to keep improving my layout and semantic HTML choices, and how to transition more confidently into using tools like React when the time comes.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•8,750
    @MarziaJalili
    Posted 3 months ago

    Great work!

    Some sort of suggestion:

    ✅ The reason the elements are not centered on the page is because the body element should've had only one child element for the code you've set for centering to work.

    ✅ In order to fix this, you could either move the footer element to the main element or wrap everything inside a simple div element.

    😎😎😎

    Marked as helpful

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