Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

Responsive design using CSS with SCSS and flexbox

sass/scss
Shravan Kumar•50
@shravankumartalabhaktula
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there,

I'd like to have feedback from you.

  • My design is not mobile friendly for now, I tried my level best to implement the responsiveness for few screen sizes. I'd like to know what all generic screen sizes available and how to target them while developing the mobile first design strategy?
  • Am I following the best practices while writing the scss files?
  • Can you please suggest me where I need to improve and some tips and tricks on how to plan before starting to code.

Thank you so much for your time.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jillian Noreen•60
    @jilliannoreen
    Posted about 3 years ago

    Looks good! You've done great! You might want to consider adding a box-shadow to further match the design provided. I can’t give much help, especially with the responsiveness, since I'm a beginner myself. All the best for the future challenges, keep up the good work, let's keep learning!

  • Axurynn•200
    @Axurynn
    Posted about 3 years ago

    Good job @shravankumartalabhaktula!

    To fix accessibility issues, you could add a main tag to your HTML file as well as h1 title. About the responsiveness, you could add max-width properties or use @media queries. For example, the min-width you could use in your media queries are 480px for mobile, 767px for tablet and 1280px for desktop.

    Overall, you did well! Congratulations! 😊

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