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

Qr code - html, css

andevlima•20
@andevlima
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 of succeeded finish my first practice project with html and css. How it was done and the result itself, I'm proud of it. But next time, I'll definitelly have to translate better the guide file, because I was trying to do the figma design, not the image on the design folder, lol. After done, I think it is really close to the original image.

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

The box model was the hardest part, I thought i did understood how it works in my beginner course on CodeCademy, but it was just the tip of the iceberg. I read tones of articles to understand just what I had to finish the challenge. I had to do the Qr code page responsive, and position a , in another propertly, to make it happen. So I found a way to do it reading articles about. But checking other persons sollutions I realize that my knowlege of box model is doesn't exist at all. The way I did the boxes in my sollution is all improvised. So I'll study more now, untill I take another challenge.

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

I want to know how you guys make a responsive page and how you deal with box model issues, because that was hard for me, and I think it can be many ways to solve the problem.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • David de Alencar•120
    @dealencardavid
    Posted 10 months ago

    Hello, qrcodezip!

    Great job on your project! I have a few suggestions, if I may:

    • Try updating the README.md file with a more personal touch. It’s a good opportunity to get comfortable with markdown.
    • In your solution, there's an issue with the padding. If you look closely, the main component (which includes the image and text) has more padding at the bottom than at the top and sides.
    • Additionally, your heading (H1) appears significantly darker than the one in the proposed solution. This might be due to an incorrect color or font weight. I suggest checking both to ensure consistency.

    That's all! Good luck on your journey.

    Cheers, David

    Marked as helpful

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
Frontend Mentor logo

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, SASS, 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