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

Easybank Landing Page | React JS āš›ļø & Tailwind CSS šŸŽØ & GSAP šŸš€

Marzia Jalili•7,270
@MarziaJalili
A solution to the Digital bank landing page 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?

This is my very first time I got my hands dirty working with GSAP. I kinda got the main idea of the framework (or libraray šŸ˜…, by the way let me know how we can differentiate these two).

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

The main challange was setting up the background image for the intro section, got on my nerves. But your buddy knows her work!

šŸ˜ŽšŸ˜ŽšŸ˜Ž

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

There is always room for improvement, and I kinda love criticism as well šŸ˜…, so don't hesitate to share your thoughts.

🫔🫔🫔

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Natnael•160
    @natnaelmemory7
    Posted about 2 months ago

    When the menu button is opened on the mobile version, an overlay background appears along with the menu. However, the overlay does not disappear when switching back to the desktop version of the site

    Marked as helpful
  • Hossein Heydari•540
    @Hossein-H-I
    Posted 3 months ago

    Hi Marzia.

    Well done as always specially the dark mode.

    For extra you can add a back to top button.

    Marked as helpful
  • Victor Eleanya•780
    @mrvicthor
    Posted 17 days ago

    Fantastic work here. It is responsive and looks great across devices. I love the animation, and kudos to you for adding light and dark theme. I guess this is my cue to start looking at GSAP

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

Oops! 😬

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

Log in with GitHub