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

Qr Code card with fixed values that is centered in desktop and mobile

kleschmabilla•20
@franzbackhaus3008
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 quite happy with the solution even though it is not quite perfect

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

I was first struggling with the html structure of the div elements, but after some consideration i think i got it down.

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

I dont know if my font implementation is correct, and if there are ways to improve my html structure

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • simgeduru•50
    @simgeduru
    Posted about 1 year ago

    I have heard that it is not correct to give a width height value in imgs, and doing so leads to distortions in responsive designs. that's my only advice

  • P
    Darkstar•1,440
    @DarkstarXDD
    Posted about 1 year ago
    • The "improve your..." text is a heading. You can use a <h1>. Always try to use the appropriate elements.
    • Don’t use fixed widths and heights on the container. They remove the containers ability to dynamically resize.
    • Instead let the content inside the container decide the size of the container.
    • But specify a max-width property so the container won’t get too large on really big screens or if you simply want to control the final size of the container.
    • So in this case you can remove the height on the .imagecard (the content will decide the final height of the card) and change the width to be max-width.
    • Set the image to be max-width:100%. No need to set a fixed width for the image. When max-width: 100% is set it will be limited to the maximum width allowed by the parent element.
    • You also need to have a <main> element in your webpage. It’s a landmark element.

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