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

Responsive Component using flex box & media queries

sass/scss
P
Haley Underwood•190
@underhr
A solution to the Results summary 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'm most proud of using SCSS during this project, as this was my first time. I definitely got a bit carried away using the nesting feature, so I'm looking forward to learning how to use that efficiently without making my code confusing.

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

As usual, any input on how I can improve my code, make it cleaner, any ways I could have done anything more efficient!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•7,310
    @MarziaJalili
    Posted 5 months ago

    Great work!

    A cherry on the top?

    • For a smoother color change we usually use the transition property, but unfortunately it doesn't work with non-solid colors like linear-gradient.

    Therefore, we have to use the ::before or ::after pseudo elements.

    • Take the code below as an example for html:
    <button>
      <!-- to prevent the text of being hidden we have to wrapp it inside an element -->
      <div>Continue</div>
    </button>
    
    • Then, apply this in css:
    button {
      position: relative;
      background: black; /* or the code of that dark blue color */
      cursor: pointer;
       
      /* ensure that the text doesn't get hidden */
      & > * {
        position: relative;
      }
    }
    
    button::before {
      position: absolute;
      content: "";
      height: 100%;
      width: 100%;
      top: 0;
      right: 0;
      background: linear-gradient(codes of the two or more colores);
      /* we will only show it on hover so now it will be hidden... */
      opacity: 0;
      transition: opacity .4s;
    }
    
    button:hover::before {
      /* make the pesudo element appear */
      opacity: 1;
    }
    

    This definitely works!

    If you find any difficulties, let me know.

    😎😎😎

    Marked as helpful

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