Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 days ago

Password Generator App Using React.js and Tailwind CSS

react, tailwind-css
P
Petar Rakocevic•230
@PetarR21
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 learned a lot in this challange.

Frist and foremost, I learned how to create custom range input, and custom checkboxes. I struggled a lot with these, and it was in a way a humbling experience, beacuse I saw how much more I have to learn.

I also learned how to use these custom inputs to generate a password based on selected options.

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

Biggest challange for me was styling inputs and using svgs in button components.

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

I would like to continue improving. I also want to explore more advanced CSS techniques for styling and layout, and to find a way to make the code more modular and reusable.

Also, I would like to improve my code in the future so it is more clean and simple.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Ashmit-kansal•240
    @Ashmit-kansal
    Posted 9 days ago

    Amazing. One thing you can enhance in your project is that make sure password length is at least the number of checked checkboxes

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, SASS, 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