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

Qr code - HTML/CSS - Visual Code Studio

P-Mingi•170
@P-Mingi
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 think that i did a good job, i probably have a problem with the size of my main container, but the rest is fine i think. It shrink well to a smaller size page format.

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

I think the way to make it responsive, i don't know if i used the good method by using a media query, i wished i could do it without using any, but i don't think it was possible.

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

With my Responsive method, did i did well by using a media query, should i have use it at a higher width, or was there another way to do it ?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • William•40
    @Dartheryon
    Posted about 1 year ago

    I think it is a good work. It could be better if you take a look on the figma file and the meassures defined on it :) Taking a look into your repo, I can see you did not change the readme as the exercise suggest us to. It would be nices if you take the time to makeit, using the readme-template provided, as a guide.

    It seems there might be some accesibilites issues you can improve. I refer to landmarks, specially.

    You use a h2 tag without using previously a h1 tag. Remember that those tags are not a matter of size, but a semantic important part of the document. Please take a look on it :)

    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