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

qr-code-component-responsive-transition-boxShadow

hamed samavati•90
@HamedSamavati
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?

it was easy- but being detail oriented would be my mindset for next proj.

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

remembering some properties

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    umwebdev•20
    @umwebdev
    Posted 7 months ago

    Hey Hamed, Good job on your first challenge, however there is a lot of room for improvement. I would break everything down into bullet points for you so its easier to implement these changes

    • Try giving meaningful classnames to the elements, it would save a lot of time when you are revisiting the code after a few days or weeks

    • don't add height to an element explicitly, this would introduce overflow issues when the content gets larger than the height you have mentioned

    • when you need spacing inside an element, try giving padding to the parent element instead of giving margins to the children elements

    • instead of giving margin-top to the second element, give margin bottom to the first element. This would keep the spacing even when you delete the second element.

    • learn and use css variables, or custom properties. that would save you ton of time, here's a video that'll help you quickly grasp the css variables https://www.youtube.com/watch?v=NtRmIp4eMjs

    • try using rem instead of pixels,, here's a great tutorial on learning the html css fundamentals by john smilga aka coding addict, it has time stamps for you to navigate easily https://www.youtube.com/watch?v=-8ORfgUa8ow

    I know that's a lot of suggestions, kindly don't get overwhelmed and take your time to implement those, it took me months to grasp all those concepts and the tutorial from john smilga is superb to learn the fundamentals.

  • Gildman Laécio•180
    @gillaercio
    Posted 7 months ago

    In my eyes it's practically the same. But as my colleague said, being detail-oriented is a crucial objective for our line of work.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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