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

easybank-landing-page

Saima Ahmed Sial•1,220
@saimasial-bit
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?

I'm proud of the design accuracy and how I was able to replicate the reference design exactly. The responsiveness of the page is another achievement, as it works well across different screen sizes. The smooth animations and interactions also turned out well. Next time, I would focus on optimizing the code for better performance and faster load times. I’d also test the website more thoroughly across different browsers to ensure consistent behavior. Additionally, organizing the code into more modular components would make it more maintainable.

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

During the project, one challenge was ensuring the responsiveness across different devices. To overcome this, I used CSS media queries to adjust the layout and design based on screen sizes. Another challenge was achieving smooth animations, which I addressed by experimenting with CSS transitions and JavaScript to make the interactions seamless. I also had to ensure that the JavaScript functions were working perfectly, especially for interactive elements. I overcame this by debugging and testing the code thoroughly in different environments. Finally, maintaining exact design alignment with the reference was tricky, but I carefully followed the design specifications and adjusted the layout using flexbox and grid systems.

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

"I’d like help with optimizing the JavaScript for smoother interactions and ensuring that all dynamic elements work flawlessly across different browsers. Additionally, I'm looking for guidance on improving my CSS layout, especially making sure that all sections are perfectly aligned and responsive across various screen sizes. Any tips for enhancing code performance would also be appreciated."

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Saima Ahmed Sial'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.