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

Divyamsharma-18 / QR-code-component-Responsive-challenge-

Divyam Sharma•160
@Divyamsharma-18
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 just proud of doing it so effortlessly, next time I'll do it with time boundation.

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

None

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

None tbh.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Carlos Al•200
    @crsaele
    Posted about 1 year ago

    I congratulate you for your efforts 😊

    If anything i would say try to write more semantic html.

    It is highly recommended to utilize semantic HTML elements, such as <main></main>, instead of generic <div></div> tags, to provide a clear structure and meaning to your content. This approach not only enhances code readability but also improves accessibility and search engine optimization (SEO).

    Writing semantic HTML is important for accessibility, SEO, code readability and maintainability, cross-browser compatibility, and future-proofing.

    By using appropriate HTML elements, you can create a clear and consistent structure for your content, making it easier for users, search engines, and other developers to understand and interact with your website.

    Marked as helpful
  • Miriam Sarpong•30
    @Mimi3678
    Posted about 1 year ago

    Great work! Looking at your code was easy to read, navigate and straight on point! Your solution also align with the style-guide that was given, but noticed that you also made small changes too

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