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

Basic HTML - QR Code

Michael•240
@mksoofian
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I was overthinking about the layering of objects in this project.

I was trying initially to break the image, header and paragraph into three boxes and set them to fill the card in a ratio proportion but wasnt having luck with that. Especially because I thought this would be responsive design and I would be able to just include a max-width on the card to keep it from getting too large. However, I wasn't having any luck with that.

Would someone be willing to share how I could have accomplished that?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tamana•210
    @Tamana123-2
    Posted over 2 years ago

    Hi mksoofian! Great job for completing the project. Although I wanted to check you code, but I could not find the CSS file. For the whole design you can get a container, so that you can set the padding, background-color margin ..., then one div for the image, one div for the first text and finally one div for the second context. As your first project, it is a great attempt. Keep moving forward. Nice time!

    Marked as helpful
  • Mr Rabbit•1,020
    @rabbitmaid
    Posted over 2 years ago
    • HTML5 elements such as <main>, <nav>, <header>, <footer>, <section>, <aside> act as landmarks, or special regions on the page to which screen readers and other assistive technologies can jump. By using landmark elements, you can dramatically improve the navigation experience on your site for users of assistive technology (Users with disabilities) .

    You can use the <div> for sub items within landmarks like <section>. In other words for containers or sections in your html you can use the <section> tag. In most cases as well you may have to put all your main site content in a landmark element <main>

    I hope you find the above solution useful! 😄 Nevertheless, the solution you submitted is great! Happy coding!

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

Oops! 😬

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

Log in with GitHub