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

Mortgage Calculator using React and TailwindCSS

react, tailwind-css
HrishiD89•50
@HrishiD89
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?

The thing i am most proud of is that i completed this project patiently, dividing part by part and not jumping and doing everything at a same time ,it took be around 2 days to complete the project which for me is the great deal because i don't have patience either i would jump to doing other things or drop the project.

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

I encountered many challenges, like

  • how to change the default radio button colour from blue to lime (which later found out have to hide its appearance and make custum style )
  • How to set the colour of the fields to focus -how to use useContext hook
  • and many more in tailwind CSS, as i only did one tailwind CSS crash course before it
What specific areas of your project would you like help with?

I would like help in the design part with tailwind CSS. i am still struggling with responsiveness width, and height

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex 🤸🏻‍♂️•1,710
    @sksksk2024
    Posted 10 months ago

    Firstly, I hope you are good and not giving up on your web development path, @HrishiD89(2 months of not publishing any site here)!! ⭐

    Secondly, I love how your structure is and the site looks solid! I see that you've encounter some difficulties with your tailwind CSS design, and based on my experience, I found that combining it with scss/sass or excluding the styles in a different file(importing it where you need) can be very helpful. I recommend the second aproach more. Ex: Let's say you have a cart.jsx file. You should put this import:

    //cart.jsx
    import styles from "./cart.module.css";
    

    In order to have access to the specified file(I recommend to put them together in a folder - Cart)

    //cart.module.css
    .cartContainer {
      @apply flex flex-column;
    }
    
    .heading {
      @apply red-500;
    }
    

    Hope it gives you a better perspective! Be patient and take care! 🔥🔥

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