Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

QR code component solution using CSS Flexbox

HussainAzimi•120
@HussainAzimi
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 that I can learn new things from completing this challenge and I would like to use them in future challenges

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

the div position was the challenge I encountered; fortunately, I could overcome it by searching and finding the solution.

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

I need more help in these areas of my code: 1- flexibility 2- clean and light

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • roopxx•120
    @roopxx
    Posted over 1 year ago

    @HussainAzimi, you did it really well, esp. the box-shadow around the main component ( I struggled for that and aligning the image ). However I would like to make note of the component not being centered vertically, maybe trying out column flexbox can come handy or perhaps auto margin along y axis ;-)

  • Sipan Ahmad•160
    @sipanahmad
    Posted over 1 year ago

    Good Job, keep going. You just need to change the description text color to : .description p{ color: var(--Grayish-blue); }

  • geektim•230
    @geektim
    Posted over 1 year ago

    Hi there, this is a beautiful job done. Well done! As regarding the centering of your card to the middle, you could consider the following: making your background display: flex; justify-content: center; align-items: center;. Or you could make your background position to be relative, then the card's position to be absolute, then you set top: 50%; left: 50%; transform: translate(-50%, -50%); on your card. I hope you find this helpful.

  • Akhil•40
    @code-sura
    Posted over 1 year ago

    Excellent work!

    A suggestion:

    Try to have good contrast ratio for the text. Especially the paragraph text. Readability is more important and is the most important criteria for a good 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

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

Oops! 😬

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

Log in with GitHub