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

CSS Flexbox for positioning and simple layout

react
Gnani•20
@Gnani31
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 happy as I made it almost same as the given one with suitable width and height and I would like to use key-frames next time for better responsiveness.

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

I struggled open it in localhost using parcel because the version is not compatible with regular image import method and so I used URL based import method with parcel and the regular method for vite.

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

I would like to get specific size of height and width of the image and padding in pixels.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Simone Paglino•115
    @simone-paglino
    Posted 2 months ago

    Hi Gnani 👋

    Good job overall. I'd like to leave just one note, regarding the font.

    Keep in mind that if you're using a font that is not already included in the default list of the supported fonts on devices (like Arial), your font-family will default to a basic version, using sans-serif.

    In this case you wanted to use Outfit, so since it's a google font, you have to included it in your html or css file. You can have a read at the following link on the google fonts website to see how to do that: https://fonts.google.com/selection/embed

    Marked as helpful
  • Leyanis Díaz•220
    @LeyaDiaz
    Posted 2 months ago

    Hello, I don’t know if this will be useful to you, but if you use VS Code, you can find out the default values of an image by pressing Ctrl and clicking on the image URL; it will show you the SVG data, including its height and width. I hope this helps you.

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