Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 21 days ago

HTML AND CSS

P
patrick•80
@Malachik
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?

am proud that i managed to complete the task without watching any tutorials.i felt nervous to as i have been watching lot of css courses, such as slay the dragon and on Udemy, and was afraid of not being able to complete the task. I was afraid to fail because i did want to feel like am just wasting my time. Doing this task made me realised that by doing is the best way to learn. I learn how to problem solve rather than just follow instructions coding along tutorials.

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

Under Figma as i have never used it before. I struggled with getting the qr-code image to fit in the container. I relaised that i needed to set height to auto after trying several different solutions.

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

I really want to focus on making my code clear and readable. I really want to focus on setting the stage, Making sense of what i am doing and how am i going to achieve it. I also need to learn when to use min-height, max-width and building responsive websites.I love the idea of CUBE-CSS i am trying to learn it moving forward, as i prefer to use it rather than BEM, however i still dont full understand some aspects of CUBE CSS

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    patrick•80
    @Malachik
    Posted 21 days ago

    I am still learning , just starting my jurney, any advice and fedback welcome. thanks

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