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

Made using plain HTML and CSS

Ismail Jabiullah•10
@IJabiullah
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 proud that I was able to make it in very short time. But i Don't know if the approach is correct or not. It felt like bruteforcing it to look like the design.

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

It was challenging to deal with the image at first. Then I google my problem and it helped. But the very first problem was setting up git with global username and email.

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

I would like to know if it was a good way to make this or was it "Bruteforcing"

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Muhammad Saif•350
    @saif010101
    Posted about 1 month ago

    Hello, i am new to this website and relatively new to front-end development as well. I am also here to learn and improve.

    Just two things i want to mention regarding your CSS file.

    • Use CSS variables to improve readability and make code easier to maintain.

    • According to the solution i think it is perfectly centered, so just add justify-content : center or remove flex-direction : column (body tag), since in this case it is just a single card.

    Good job!

    Marked as helpful
  • haquanq•2,015
    @haquanq
    Posted about 1 month ago

    There is no brute-forcing here, no need to overthink.

    • There is however different ways to simplify HTML structure, example would be remove .textDiv wrapper and your structure stay the same (div does not have semantic meaning, avoid using it, similar to span).
    • Your page should contain one main landmark and h1 to describe page content.
    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

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