Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 19 days ago

QR Code Component using basic HTML5, CSS3 and Flexbox

Raizo-03•50
@Raizo-03
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 proud with the solution I formulated base on my own basic knowledge of HTML, CSS, and CSS Flexbox. I also used the fundamentals such as box models, semantics, proper structures etc. I treated this challenge as an opportunity to actively recall and apply what I’ve learned from past lectures. What I will do next is, I will try to read documentations so that I will take up too much time figuring out things.

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

Since I didn't use any documentations or tools aside from using fonts, I've had hard time formulation a solution in my head such as applying flexbox, using var for the hsl colors etc. I also had hard time figuring out the fonts, content sizes but I've overcome it by figuring out what's the closest possible replica of those said properties.

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

I'm open to all feedback, but I'd especially appreciate help with the following areas:

Responsiveness: Are there better ways to handle mobile responsiveness, especially for centering the component vertically?

Styling Practices: Is my use of CSS custom properties and font import clean and maintainable?

Layout Structure: I used Flexbox for centering — is this the most efficient approach for this type of layout?

Code Optimization: Are there any unnecessary CSS declarations or better practices I could follow?

General Code Readability: Is the HTML and CSS structure readable and scalable for future projects?

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 Raizo-03'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.