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

Responsive Landing Page using Astro and TailwindCSS

astro, tailwind-css
Mehar Giri•30
@mehargiri
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?

Most proud of the fact that I could create the landing page using Tailwind CSS with relative ease. I also got a chance to use both flex box and CSS Grid for the design.

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

The main challenge was the hero background images of the mockup mobile photo and the desktop/mobile intro photo. I tried my best to match the hero content with the design file. However, the hero content does not match, with the design files, as well compared to other sections of the landing page.

I used multiple media queries to allows the two background images of the hero content to gradually increase with higher screen width. However, the CSS I wrote is very messy.

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

I would greatly appreciate it if someone could heavily critique my design and suggest improvements regarding accessibility or the general readability of the code.

In particular, I would be very grateful if someone could help me fix my hero section to match the design file as much as possible. The current method of using multiple wrapper elements and media queries seems very cluttered.

Thanks a lot to the Frontend Mentor team for providing this challenge. It was really fun to do this challenge!

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 Mehar Giri'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.