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

responsive password generator app using tailwindcss

tailwind-css
Edidiong•580
@ScarAgathor
A solution to the Password generator 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?

I used this project to practice tailwind because I'm trying to compare it to sass. So far I do prefer scss just because Its easier for me to write but I can see how tailwind can still be useful especially because I don't have to come up with class names. Although there were definitely some things I didn't like. I couldn't make the custom slider using tailwind alone and he re was also the issue of tailwind removing classes that aren't being used at the moment the page loads. I understand that is one of its uses but it did get annoying and I had to define the classes in the input CSS file. Any advice on how to make this process easier will be appreciated.

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

Advice on how to dynamically add classes using js and tailwind and also how to design the custom slider in tailwind. I also couldn't figure out how to make the custom slider accessible. I.e, I couldn't complete it using my keyboard alone dso I would appreciate advice on this

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    DJ Neill•130
    @djneill
    Posted 11 months ago

    I couldn't find much info on range sliders either. It was noted that they're not used much in the real world due to inaccuracies. Since you're using HTML this article was shared in the group that may be able to help you.

    https://www.smashingmagazine.com/2021/12/create-custom-range-input-consistent-browsers/

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