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

Responsive Mortgage Calculator using TailwindCSS & Zod

react, tailwind-css, zod, next
Atatra•170
@Atatra
A solution to the Mortgage repayment calculator 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?
  • It was easier than I thought to format the amount's input without using a third-party library. But it led to accessibility issues mostly on mobile (the input is no longer of type number, but text). Next time I'll probably use a library like Cleave.js so I won't have to deal with all the side effects.
  • I'm happy I got the opportunity to experiment with Zod for client-side data validation (even if it was probably overkill here, but it made error handling way easier and much more flexible).
  • I tried experimenting with CSS grid for mobile responsiveness.
What challenges did you encounter, and how did you overcome them?
  • I struggled so much on changing the color of the radio buttons. It seems that I can't change it directly, since it is browser dependant (?). I had to make it invisible and replace it with 2 divs placed one inside another with absolute positioning, which resulted in slightly different layout with different browsers/screens. Next time I'll probably use an image instead. Any advice is much appreciated.
  • I'm still having trouble with the content of my page wrapping along the vertical axis on small width, and overflowing its container (I can't find a way to crop the content when I reduce the width).
  • I couldn't expand the background of the result's section to match full remaining height, so it poses an issue on large vertical screens.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

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.