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

Responsive QR code using HTML and CSS

123dakalo•50
@123dakalo
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?

Well I didn't learn much

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

center div... i left out position absolute

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

none

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Cillian Bracken-Conway•50
    @cillianbc
    Posted over 1 year ago

    Have a look at using semantic HTML like <section>

    Marked as helpful
  • Grace•32,130
    @grace-snow
    Posted over 1 year ago

    There are some important foundational learnings from this challenge:

    1. All content should be contained within landmarks. This needs a main wrapping the container. You could make container into a section too but there is really no benefit at all to doing that.
    2. The image is extremely important content. It must have a proper alt description saying what it is ("QR code") and where it goes ("to FrontendMentor.io")
    3. Remove all of those brs. That is not how you create line breaks. They need to happen naturally.
    4. The html file should always be called index.html
    5. It's better for performance to link fonts in the html head instead of css imports.
    6. Never limit the height of elements that contain text. It's fine to use min-height on the body but not set a height.
    7. Do not use position absolute to center a component in the viewport. Use flexbox or css grid. Position absolute removes the elements from the document flow and could lead to really awful bugs.
    8. Always use a modern css reset at the start of the styles in every project. Get into the habit now. Andy Bell or Josh Comeau both have good ones you can look up and use.
    9. The image must not have an explicit width. All it needs is display block and max-width 100% (which would already be included in the css reset)
    10. Font size must never be in px
    11. You seem to be confusing padding and margin in this. I've written a post about padding and margin which you may find 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, 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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub