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

QR Code Card ( HTML / SASS)

Hamza Masmoudi•180
@HamzaMasmoudi
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


𝗛𝗲𝗹𝗹𝗼 𝘁𝗵𝗲𝗿𝗲 👋, 𝗜'𝗺 𝗛𝗮𝗺𝘇𝗮 𝗮𝗻𝗱 𝘁𝗵𝗶𝘀 𝗶𝘀 𝗺𝘆 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻 𝗳𝗼𝗿 𝘁𝗵𝗲 :

𝗤𝗥 𝗰𝗼𝗱𝗲 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁. 🤖

This is my first challenge on frontendmentor.io after learning the basics of HTML and CSS and I will be doing all the challenges before I start learning Javascript.

I guess it will be a long journey but I m sure i will have fun.

✨ Follow me on my journey on completing all the free HTML/CSS challenges ( 1/26 )

Any suggestions or feedbacks on how I can improve and reduce unnecessary code are welcome! Thanks you 😊🫶

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aman Singh Bhogal•1,010
    @asbhogal
    Posted about 2 years ago

    Hi Hamza,

    Good job! Just something I noticed, your explicit width is causing the container to scale down and shift to the left when you reduce the viewport. Ideally, you should just set a max-width for parent containers, and a width of 100% to ensure the width of the container only takes up a fixed width, and anything below, it will only take up 100% of it, and avoid setting width values for children containers, instead let them take up the space they need. This will help avoid any overflow problems.

    What you can do is the following:

    • Remove the width: 64rem on the .container and instead apply, for e.g. a max-width: 300px and width: 100%
    • Remove the width: 50% on the .image-text

    Hope this helps!

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