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

ReactJS TailwindCSS Vite Interactive Pricing Tool

react, tailwind-css, vite
lavollmer•480
@lavollmer
A solution to the Interactive pricing component 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?

I am most proud of the interactive slider tool and toggle button functionality.

Next time, I would work more on the layout and mobile responsiveness early on.

What challenges did you encounter, and how did you overcome them?
  1. TailwindCSS Content Configuration: Initially, my tailwind.config.js file had an empty content array, which led to no styles being generated. Tailwind relies on this array to scan files for class names. By including paths to all relevant HTML, JavaScript, and JSX files, I ensured Tailwind could effectively generate the necessary styles.

  2. Custom Colors in Tailwind: The project required the use of specific custom colors. I learned to extend the Tailwind configuration under the theme section to include these colors. This allowed me to use the custom colors throughout the project by referencing their keys, seamlessly integrating the design's color scheme.

  3. Positioning Techniques: This project deepened my understanding of relative and absolute positioning, especially for layering images such as the background and pattern circles. Setting a container to relative positioning provides a reference point for absolutely positioned elements within it, facilitating layout control.

  4. Using Images as List Item Markers: TailwindCSS doesn't directly support dynamic values in class names, which posed a challenge when trying to use an image as a list item marker. I overcame this by defining a custom class in my global CSS file and applying it within my JSX, showcasing the flexibility of combining Tailwind with custom CSS for unique requirements.

  5. Building an Interactive Slider: Prior to this project, I had no experience with interactive sliders. I learned about managing the slider's state to reflect its current value and implemented an onChange event handler to update this state whenever the slider's value changed. Ensuring the input's type was set to range was crucial for the slider functionality.

  6. Extending Font Sizes in Tailwind: Tailwind's predefined font sizes didn't include one small enough for a specific design requirement. I extended the Tailwind configuration to include a custom xxs font size, demonstrating the ease of customizing Tailwind to fit project-specific needs.

  7. Enhancing Button Interactivity with Hover States: Adding a hover state to the "Start My Trial" button reinforced the importance of interactive elements in UI design. By utilizing Tailwind's hover: prefix, I was able to create a visually responsive button that enhances user experience.

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

I was unable to figure out how to change the range slider icon to the svg provided. I would love someone's guidance on how to do that.

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 lavollmer'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.