Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 9 months ago

Fundamentals of HTML and CSS - QR reader

Jun41dU•10
@Jun41dU
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 of how I was able to make this project with no help, as well as my attempt at making it responsive using @media. During this first project, I used git for the first time, so I am glad I can now integrate future projects with GitHub and work with other programmers easier.

Next time I could probably make a better plan out how I would approach the project especially as when it becomes more complex, I could be unsure what to do.

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

The challenges I faced was actually deploying the website, as I did not know I had to put the /main.html at the end of the URL for it to display the site, which on reflection was a silly oversight.

I also had some problems with finding the exact font size I needed as I had to learn how to use googles apis to access the fonts. I feel like the font I have is fairly similar to the design, but it probably could be more accurate. I overcame this mostly through trial and error.

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

When looking at my code, I feel my approach to 'responsiveness' meant that the design isn't perfect, such as the word 'skills' in the main body text not being on the second line like with the example picture. Some pointers also on how to fix this would be great.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • David Sibrian•350
    @armson45
    Posted 9 months ago

    Hey there! David here...It looks great but here are some points to dive in.

    -Try to use semantic html5 tags like section, article, headings(h1, h2, h3, etc). -I like the way you name the classes. -I think the problem of the title is because the width of the 'qr_container'. -If you use correctly min-width and max-width you can save some media queries.

    That's all I can say, If you need more help you may want to join to the discord community

    Have a nice day! :D

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