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

Frontend Mentor | QR code component

codewithedeepak238•150
@codewithedeepak238
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 thinking to start the frontend mentor challenge since a long time, now I started my first challenge. I didn't find any difficulty in doing this one. Hope I will stay attach to these challenges, and will learn something new daily.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Oscar Bocanegra•235
    @obocanegra-dev
    Posted about 2 years ago

    Congratulations on taking the plunge and tackling your first Frontend Mentor challenge! It looks great, and you've done a fantastic job.

    I have a few suggestions to enhance your work:

    Instead of writing CSS directly in your HTML, I recommend creating a separate stylesheet file and linking it to your HTML. This will help keep your code organized and make it easier to manage and update your styles.

    Consider using semantic elements rather than generic <div>s. Semantic elements like <header>, <nav>, <main>, and <footer> add meaning and structure to your HTML, improving accessibility and search engine optimization.

    For the QR code image, it would be helpful to use a more descriptive alt attribute, such as "QR code to Frontend Mentor website." This provides better context for screen readers and improves the accessibility of your site.

    Remember that font sizes should never be specified in pixels. It's better to use relative units like rem or em. This ensures that your font sizes are responsive and adapt well to different devices and user preferences.

    Keep up the excellent work, and don't hesitate to explore more challenges on Frontend Mentor to further enhance your skills! 🎉💪

    If you have any questions or need further assistance, feel free to ask. Good luck with your future projects! 🚀✨

    Warm regards, Oscar

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