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

hover effects fot the buttons, flexbox for responsive land page...

Ruan Gomes•100
@rug19
A solution to the Huddle landing page with curved sections challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi guys!

I'd like some help with the wave backgrounds because both backgrounds from the tag main and footer got distorted, I got to adapt for a mobile screen but when comes to the tablet screen the background gets a little distorted, so I hope someone checks my code and give me a feedback.

Thank you guys for all the supporting

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Boots 😺•1,610
    @adityaphasu
    Posted almost 2 years ago

    Hi!

    Good job on the challenge!

    • The problem of distortion of waves is coming due to insufficient heights of the waves when the media query is applied due to those heights the waves just cuts off.
    • I think only the footer and section-3 waves have this so one way you can do to fix this just increase the height of the waves in the max-width:768px a little bit and add another media query say max-width:400px to keep the wave heights for the mobile.(The ones you wrote for in the 768px media query)
    • Do it like this:
    @media (max-width:768px) {
     
    .bg-wave-section3-top {
    background: url(../images/bg-section-top-mobile-2.svg) no-repeat;
    height: 13rem;
    }
    
    .bg-wave-section3-bottom {
    background: url(../images/bg-section-bottom-mobile-2.svg) no-repeat;
    height: 13rem;
    }
     
    .bg-wave-footer {
    background: url(../images/bg-footer-top-mobile.svg)no-repeat;
    height: 5.6rem
    }
    }
    
    @media (max-width:400px) {
    .bg-wave-section3-top, .bg-wave-section3-bottom {
    height: 10rem;
    }
    
    .bg-wave-footer {
    height: 2.6rem
    }
    
    • I've increased the heights according to what I found to be good at those screen sizes but you can try playing around a little bit to see what feels more okay.

    • You might've noticed that I've removed background-size: cover; from all these, it's because you are already applying this property originally (for the desktop) this still gets applied when you write the media query, and in this case it remains the same so writing them again just repeats the code.

    This should be enough to fix the problem you are having 🙂

    Keep coding and good luck!🙌🏻

    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 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