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

Responsive QR Code Component using HTML5 and CSS Flexbox

Mohamed ashrf•340
@x-mohamed25
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 proud that I completed the layout using only HTML and CSS, and that I was able to make the component look clean and centered using Flexbox. I also managed to deploy the project successfully on Vercel. Next time, I would add more responsiveness to make the component adapt better on mobile screens, and focus on using semantic tags more consistently.

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

The biggest challenge was aligning the component in the center of the screen and setting the proper margins and padding for the card layout. I solved it by practicing more with Flexbox properties and inspecting the layout using browser dev tools. Another challenge was deploying with GitHub and Vercel for the first time, but after understanding the correct steps and fixing file paths, it worked.

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

I would appreciate feedback on:

Whether my HTML structure is semantic and accessible

Best practices for writing clean and scalable CSS

How to make the design more responsive on small screens

Any improvements I can make to the visual design or spacing

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Prateek•130
    @Prateek1789
    Posted about 1 month ago

    Your HTML structure is semantic but you should not use a section tag for creating a card component since it is generaly used to define different sections on the page. You should instead stick to using a div and you can add an aria-label on it if you want to. In order to write clean and scalable CSS you should use root variables and define colours and font sizes in that. To make design more responsive on smaller or any screen sizes you should use relative units such as em, rem, vh, vw, additionally you can use minmax() and clamp() function to define a range for anything basically.

  • Igor Barreto•10
    @Igorbarr3to
    Posted about 1 month ago

    Very well, Mohammed.

    Some points that i could observe is:

    • The css was not reseted, so the <main> container is getting a padding of body container;
    • You did not use the font specified in the design guide;
    • <h2> tag is not centered;

    Furthermore, the rest of the design was quite similar to what was proposed, congratulations!

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

Oops! 😬

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

Log in with GitHub