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

Responsive landing page (Mobile-First approach). Using ReactJS, SCSS.

react, sass/scss, bem
Simon Hernandez•615
@simonhernandez
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi Guys!

It's been a while since I last submitted a solution. I am very happy to be back!

This time around I decided to put into practice my React skills to bring to life this simple and beautiful design. Used Semantic HTML tags, SCSS for styling, and AOS library for animations.

Hope you guys like it! I also would really appreciate any feedback on my code or on the overall project.

Wish you guys an awesome week and fun coding!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted almost 3 years ago

    Greetings, Simon Hernandez! 👋

    Incredible work on this challenge! 🙌 It's great to see you back with another solution! 👏 I really like the animations you added to your solution! 😀

    A small suggestion I have is to perhaps set the alt text for the icons in the "Why choose Easybank?" section to be an empty string so that they will be ignored by screen readers. That’s because those elements aren't really necessary or important to the content of the page and as a result probably don't need to be read by screen readers. 😉

    It would also be good to add some focus styles to some of the interactive elements on the page that do not currently have them (such as the "Request invite" buttons).

    And it would be worth taking a look at the responsive issue that @veljkoilic mentioned in the hero section of the site! 🙂

    Hope you find this helpful. 😊

    Keep coding (and happy coding, too)! 😁

    Marked as helpful
  • Veljko Ilic•190
    @veljkoilic
    Posted almost 3 years ago

    Awesome work dude!

    Everything looks super slick and responsive! I suggest you make your animations go only one way. If you scroll up and down again they replay, but this is just a personal taste.

    However, there is a bit of a weird 1000px - 1140px area. The Intro section heading overlaps with the background making it unreadable and the articles at the bottom are really squished. This is all minor but I thought you'd appreciate the nitpicking feedback!

    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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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