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

Tip Calculator app using HTML, Tailwind CSS, JavaScript

tailwind-css
Vinit Yadav•180
@vinits-repo
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey Everyone,

I just wrapped up my latest challenge, building a tip calculator app using HTML, Tailwind CSS, and JavaScript. I'm eager to receive feedback. Any suggestions for enhancing the solution would be greatly appreciated.

Thank you!

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

    First and foremost, congratulations on completing your Frontend Mentor project! It's an impressive feat to take a concept and turn it into a functioning web application. Your efforts have certainly paid off. Here are some best practices and recommendations to further refine your project:

    HTML & CSS Best Practices:

    • Semantic HTML: Great job using semantic elements. Consider using more specific tags like <section> or <article> for better structure and accessibility.
    • CSS Organization: Your CSS is well-structured. Keep using comments and consistent formatting for better readability.
    • Responsive Design: Ensure your design is responsive and looks good on all devices. Using relative units like em or rem instead of pixels can further enhance responsiveness.
    • CSS Variables: Good use of CSS variables for managing colors and fonts. This makes your code more maintainable.

    JavaScript Best Practices:

    • Use of const and let: Prefer const and let over var for variable declarations. They provide block-level scoping, which is more predictable.
    • Event Delegation: Implement event delegation for handling events on dynamically added elements or for reducing the number of event handlers.
    • DRY Principle: Follow the DRY (Don't Repeat Yourself) principle. If you find yourself writing similar code multiple times, consider creating a function for that purpose.

    Accessibility:

    • Keyboard Navigation: Make sure all interactive elements are accessible via keyboard.
    • Form Accessibility: Ensure form inputs have associated labels for better screen reader support.

    Performance:

    • Optimize Images: Check if your images can be optimized further to reduce the load time, especially for users on slower internet connections.

    Learning Resources:

    • For more in-depth knowledge of HTML and CSS, MDN Web Docs is an excellent resource.
    • To strengthen your JavaScript skills, JavaScript.info is highly recommended.
    • For best practices in web accessibility, refer to WebAIM.

    Keep up the amazing work! Remember, each project you build enhances your skills and brings new learning opportunities. Your progress is admirable, and as you continue to apply best practices in your work, your development skills will grow even stronger. Happy coding!

    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

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