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

Responsive QR Code Component using flexbox

P
Hosea Marcus Calalang•50
@Marcusgb21
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 to do project-based learning because it reinforces my knowledge as well as gives me confidence in my development skills.

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

The challenges that I encountered were styling the card and container divs. I overcame them by using Google to search for resources and utilizing AI by asking questions and challenging AI instead of copy-pasting the code.

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

In terms of styling, I get quite confused about how many divs I should create, as well as styling them.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dev Truce•230
    @DevTruce
    Posted 3 months ago

    Hey Hosea, great job on completing the QR code component challenge! You did great 🥳 Here are a few suggestions that might help you going forward:

    1. Use semantic HTML (section, main, article, etc) where it fits and fall back on div when nothing else makes sense.

    2. Each div should have a clear purpose, grouping content, applying layout or managing spacing.

    3. Don’t stress about the number of divs, focus on clarity and structure instead.

    4. Use layout tools like Flexbox or Grid to control spacing and alignment. Think of each section as a purposeful container.

    5. Check out the "text-align" CSS property, it will help you match the component descriptive text more closely to the design.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub