Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

EasyBank Landing Page

react, bootstrap
King David•50
@01kingdahvid
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Good Morning/Afternoon/Evening!. I just want to share a quick note about my journey building the Easy Bank Landing Page project with React.js.

I actually used just HTML and CSS initially but after learning React.js (thanks to my tutor), I decided to transfer my work from HTML to React.js. I used React.js for this project because it’s a powerful JavaScript library that allows building interactive and dynamic user interfaces.

Throughout the process, I focused on creating reusable and modular components, such as the navigation menu, Intro Section, Hero section, Blog section, and the Footer section. This helped me keep my code organized and maintainable. 💻

I also used React Bootstrap and React Router Dom, and it was a game-changer! It provided a wide range of pre-built components that made the development process/route navigation faster, easy and more efficient. Finally, I also debugged while building and seamlessly integrate with React Components, React bootstrap & React-router-dom, which allowed easy customization, responsiveness and swift/easy navigation. I highly recommend giving it a try for your project! 😊

Overall, building the Easy Bank project with React.js was an exciting and rewarding experience. It allowed me to showcase my skills in debugging and also my skill in front-end development and creating a modern, responsive, mobile first applications to suit a wide range of mobile and desktop screens and user-friendly website.

Pls kindly like, comment and feel free to check out the project and let me know what you think!. If you have any questions or need further details, just give me a shout - My DM is always open

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on King David's solution.

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.