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

👻 Landing Page: Footer and header waves (HTML + Tailwind + JS)

tailwind-css, animation
Natali 👻 Grimm•1,190
@Grimm-N
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


What are you most proud of, and what would you do differently next time?

Well, I'm not sure if I can brag about this 😅, but I'm definitely trying to make my work interactive and dynamic! 😎 You tell me, did I nail it? Or should I try harder?

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

The biggest challenge was working with Tailwind for the first time. It felt like jumping from heaven to hell 😅. So unfamiliar, but in the end, I made something work. Guess what? It’s only going to get easier from here! 💪

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

Unfortunately, I only noticed the background under the sections with the curved edges at the very end 😅. Maybe someone can share a simple and elegant way to use the provided images for this?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Asilcan Toper•2,960
    @KapteynUniverse
    Posted 7 months ago

    Hey Natali, great job.

    There is a mix-blend-mode but i never used it. I don't know if it can be useable with another background animation but it is something like this.

    .test {
      position: relative;
    }
    
    .test:after {
    content: "";
    position: absolute;
    background: rgb(255,255,255);
    width: 100%;
    height: 100%;
    display: block;
    mix-blend-mode: difference;
    }
    

    It is normally for the dynamic background change on the element, like you give it a black background and text become white, then with animation or js you change background color and the text adapts to it.

    Here is an example

    Ignore if you saw my other reply. It was wrong :D

    Marked as helpful
  • Yacoub AlDweik•3,110
    @YacoubDweik
    Posted 7 months ago

    Yooo! Good job Ma'am!

    The website is a bit slow especially at the footer and this is not surprising bcuz of that animation ofc,

    Keep it up Ma'aaam and congrats for changing your nickname, as always ghosts and stuff hehe keep it up

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