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

responsive tailwind css calculator

tailwind-css, accessibility
Gift Richard•520
@fibonacci001
A solution to the Calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey there! I'm pumped to share more about my approach to the calculator app challenge. 😄 It was such a fun project to flex my HTML, CSS, and JavaScript skills!

For starters, I focused on setting up the markup to match the designs. Getting the structure down with semantic HTML5 elements really helped streamline the styling process later. I made sure to use header, main, footer tags, and ARIA roles for improved accessibility too.

On the CSS side, I relied heavily on Flexbox and Grid for layout from tailwindcss. This made it smooth sailing to get the numpad and display area aligned nicely across device sizes. I definitely learned some new tricks for responsively styling the range slider and toggle switch that I'll be sure to apply in future projects!

JavaScript was the real brain bender! 🧠 I used event listeners on the number buttons to build the display value string, and wrote logic for the math operators, delete button etc. The theme toggling gave me a chance to sharpen my DOM manipulation skills as well.

In terms of optimization, I tried to keep the JavaScript focused and modular. I probably could have split it out even further into logical files. And there's certainly room to improve performance by only updating specific DOM elements rather than full page re-renders. More to learn!

Let me know if you have any other feedback! thanks! 💪

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 Gift Richard'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.