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

QR CODE

Ayomidesholanke•20
@Ayomidesholanke
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 of how I was able to recreate the QR Code Component to closely match the given design. I ensured the layout was perfect. Additionally, I maintained clean, semantic HTML and CSS, which made the codebase organized and easy to understand. It was also satisfying to see the component fully functional and visually appealing.

Next time, I’d aim to plan the structure more thoroughly before jumping into coding, which would help optimize development time.

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

Some of the challenges encountered was aligning the component properly on the page. Initially, I struggled with centering the QR Code Component both vertically and horizontally on the screen.

And I overcame them By utilizing CSS Flexbox and set the container to justify-content: center; align-items: center; to ensure the component stayed centered. For design precision, inspected the design closely and used the style guide to get the colors and font sizes accurately.

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

The main area I’d like help with is ensuring responsiveness across all screen sizes, I want to improve my approach to make the design more fluid and adaptable to edge cases. Any tips or best practices for achieving this would be greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Stephengrammy•60
    @Stephengrammy
    Posted 7 months ago

    This is nice keep up the good work dev🙌🙌🙌 but you should learn to add fonts I use google fonts and it is very easy to use just search for the fonts you want and they will provide you with an embedded link to copy into your html head. If you hit a blockage when coding as a beginner it's nice to try everything possible you can think of but if it doesn't work remember you don't have to know everything off the start the internet is there to help so utilize your search engine it would help a lot I'm not saying you should use Ai to write codes no just check online for the right semantic of the code you already have in mind but don't know to write it or the right selector/element to use Congratulations on your project 🥰👌

    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

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