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

Mobile and desktop design done

Alexsander Batista Dos Santos•360
@alexsanderBDS
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I need some tips for how hover a background linear-gradient element 😃

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Emmanuel-Xs•100
    @Emmanuel-Xs
    Posted about 2 years ago

    Try This

    .button {
        background-color: var(--clr-neutral-270);
    }
    
    .button:hover,
    .button:focus-visible {
        background: var(--gradient-primary);
    }
    

    Replace my custom properties with yours

    NOTE It is not possible to do transitions on linear-gradient.

    Marked as helpful
  • Account deletedPosted about 2 years ago

    Hello there,

    Readable and maintainable code is important for any developer. Here are some recommendations to help improve the readability and maintainability of your code:

    1. Use descriptive class names: Use clear and descriptive names for your classes. This helps other developers understand the purpose of the class without having to read the code.

    2. Use consistent naming conventions: Use consistent naming conventions for your classes and functions. This helps maintain consistency throughout your codebase and makes it easier to understand.

    3. Keep your code organized: Use indentation and spacing to keep your code organized and easy to read. This also helps to differentiate between different sections of your code.

    4. Use comments to explain complex code: Use comments to explain any complex or difficult-to-understand code. This helps other developers understand the purpose of the code and its intended behavior.

    5. Avoid code duplication: Avoid duplicating code as much as possible. This reduces the amount of code that needs to be maintained and makes it easier to understand and debug.

    6. Write modular and reusable code: Write modular and reusable code wherever possible. This makes it easier to add new features or make changes to existing code without having to rewrite large sections of your codebase.

    By following these recommendations, you can improve the readability and maintainability of your code, making it easier for other developers to work with your code and reducing the chances of introducing bugs or errors.

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub