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

Tip Calculator - SCSS, Javascript, Vite, GH Pages, Lubuntu

sass/scss, vite
Juan A Lagunas Palomares•430
@dev-jLagunas
A solution to the Tip calculator app 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: I am most proud of the fact that I was able to get through 99% of this completely on my own without doing any google searches or asking copilot. This has been my main focus for the last few projects. I am now in the stage of my learning journey where I need to take off the training wheels and start doing, most, if not all on my own. It was so exciting because I am starting to learn to take risks and put less focus on the feeling that I need to be perfect.

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

Challenges: I was caught by surprise by how much of a challenge I faced when creating the layout. There were a lot of sections where the layout was trickier than it seemed. I managed to solve it with grid and some tinkering of padding and margins.

I also had a brain freeze when it came to the javascript because the project did not have a button that would "trigger" the logic. It seems easier when there is a single trigger button that can guide the logic so instead this project required me to work with various event listeners that would together trigger the calculation logic.

That was a great learning experience.

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

For Next Time: I want to improve two things.

  1. I want to write better commit messages. More granular, but simple and clear.
  2. I want to use other Git commands, even if they are just for practice so I can start getting the muscle memory of the process.

Thanks for reading! and thanks Frontend Mentor for giving us these challenges. They are extremely useful!

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 Juan A Lagunas Palomares'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 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.