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

Password Generator app

ikethedev•280
@ikethedev
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'm proud to have successfully implemented JavaScript in my project. While I've focused heavily on DOM updates, I've realized the importance of visually appealing CSS. For my next project, I plan to prioritize both clean JavaScript and pixel-perfect CSS design.

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

My biggest challenge was styling the input range and I overcame that challenge with a lot of Googling and Youtube videos!

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

I would love to have help with using the Figma files. I do not understand how to use the information provided to get width and height from the files provided.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aslam Mohammad•220
    @AssSam7
    Posted 10 months ago

    Good work pal!

    A few things to improve upon,

    1. The checkbox looks distorted in the checked state. The tick gets translated to the bottom right and also is not visible. (Sorry unable to share the screenshot here)
    2. The responsiveness could be improved, as soon the breakpoint is hit for the tablet instead of the center the container moves to the top of the page where as per the design it should be at the center both vertically and horizontally). It might be because of the width of the container.
    Marked as helpful
  • P
    DJ Neill•130
    @djneill
    Posted 10 months ago

    If you double-click the element that you want to know the size of, for example, the input box that displays the password. On the right-hand side, it will have a 'w' for width and 'h' for height, the numbers displayed are the size in pixels. I can't share a screenshot here but if you look at the below link a similar question was asked in the Figma "ask the community" forum.

    Figma support forum, unit measurement

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub