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

Responsive landing page with vite, react and tailwind css

react, tailwind-css, vite
Raza Abbas•770
@RazaAbbas62
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback is welcome :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Great job on completing your Easybank landing page project! It's a significant step in your journey as a developer. Here are a few suggestions to enhance your code:

    1. Refactoring for Reusability and Efficiency:

      • Consider creating a reusable component for buttons. You have Button imported in several files. Make sure it's a generic component that can handle different texts, styles, and actions. This approach reduces code repetition and increases maintainability. Explore more about React component design patterns here.
    2. Accessibility Considerations:

      • Ensure all interactive elements, like buttons and links, have appropriate ARIA attributes for better accessibility. For example, adding role="button" to elements styled as buttons but not using the <button> tag. Learn more about accessibility in React here.
    3. Optimize Image Loading:

      • Use modern image formats like WebP for better performance. Also, consider implementing lazy loading for images. This can significantly improve your site's loading time, especially if there are many large images. You can learn more about image optimization here.

    Keep up the hard work! Remember, each project is a learning opportunity. Continue experimenting and exploring new ideas. Your progress is commendable, and I look forward to seeing more of your projects in the future! 🚀💻

    Marked as helpful
  • Theunis•210
    @theYuun
    Posted over 1 year ago

    Very cool! I wanted to point out the missing image behind the top image you have there, but you mentioned that to Vishal. Loading images from outside sources can be a prickly subject, no doubt.

    Marked as helpful
  • Vishal Maurya•500
    @VishalMauryastp
    Posted over 1 year ago

    you tried well .

    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.

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