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

QR code solution

Kevin Rasata•70
@kevinrasata
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?

The use of semantic HTML elements like and , makes the structure of the document clearer. Standardized naming conventions for CSS variables, makes the code more readable and maintainable. Next time I would consider starting the CSS with styles for mobile devices first and then using media queries to add styles for larger screens.

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

When working on this front-end project, I encountered significant challenges with the layout. Despite my efforts, I found it difficult to achieve the desired structure and responsiveness. The main issues were ensuring the elements aligned properly and adapting the design to different screen sizes. After multiple attempts and adjustments, I decided to seek help from an experienced front-end engineer. This consultation provided valuable insights into refining my HTML and CSS for better structure, accessibility, and responsiveness, ultimately allowing me to overcome the layout issues and complete the project successfully.

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

Again, I would say the layout. If anyone has any other suggestions to write better code for the layout. It would be much appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • abdelrhman-mahmoud-awad•30
    @abdelrhman-mahmoud-awad
    Posted about 1 year ago

    it was so simple so i don't have much to say

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