Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
12
Comments
13
P

emawid

@emawid190 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

  • Password generator app

    #vite

    P
    emawid•190
    Submitted about 1 month ago

    0 comments
  • Tip calculator

    #vite

    P
    emawid•190
    Submitted about 2 months ago

    0 comments
  • Time tracker dashboard

    #vite

    P
    emawid•190
    Submitted 2 months ago

    1 comment
  • Newsletter signup form with success message


    P
    emawid•190
    Submitted 3 months ago

    1 comment
  • Article preview component


    P
    emawid•190
    Submitted 3 months ago

    1 comment
  • Testimonials grid


    P
    emawid•190
    Submitted 4 months ago

    1 comment
View more solutions

Latest comments

  • Faraz mobin•160
    @Faraz-mobin17
    Submitted over 1 year ago

    Responsive Password Generator with React and Tailwind

    #animation#react#tailwind-css#vite
    1
    P
    emawid•190
    @emawid
    Posted about 1 month ago

    Hi Faraz,

    Great work with the password generator! You have solved the core functionality very well with a good UI. To improve further I suggest to focus on the design and layout. For example, typography and aligning the element for "Character Length" with the character length number output. You could also try and implement the strength bar features to get it more closely the the intended design.

  • P
    Thanasis Protopapas•440
    @thanasispro
    Submitted about 2 months ago

    Tip calculator

    #react#vite#tailwind-css
    2
    P
    emawid•190
    @emawid
    Posted about 2 months ago

    Hello Thanasis,

    Nice work with the tip calculator app! I think you have captured the look and feel very close to the design files. If you were to improve the app I would suggest adding an error message for the bill input field as well and maybe setting the defualt number of people to 1 since its optional.

  • S Mishra•230
    @sthitaprajna-mishra
    Submitted over 1 year ago

    Time Tracking Dashboard using React + TailwindCSS + Vite

    #react#tailwind-css#vite
    1
    P
    emawid•190
    @emawid
    Posted 2 months ago

    Congrats on completing the time tracker challenge. Great work! A couple of points to conisder for the next challenge:

    1. The responsiveness looks great on desktop and mobile but looks a bit sqished on tablet. My advice is to to either increase the size of each activity card or dynamically reduce the font size, whatever looks best for the user.
    2. The main content jumps when decreasing the screen size from desktop to tablet. I suggest you keep the same position for the main content for all acreen sizes. Either center or top-center. Good luck on your next challenge!
  • P
    Mirko Zlatunic•250
    @mirkozlatunic
    Submitted 3 months ago
    What are you most proud of, and what would you do differently next time?

    I applied the JavaScript fundamentals to React components and hover styles so that they are used when clicking the buttons. I would refactor the code even more into reusable components.

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

    I had challenges applying the proper function to the form. I needed to go back to the code multiple times to get the results that I have now.

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

    I'd like feedback on the refactoring part and how others would approach the React functionality with form validations.

    Newsletter sign-up component

    1
    P
    emawid•190
    @emawid
    Posted 3 months ago

    Great job with the newsletter sign-up challenge. What an accomplishment! I do not have any experience with React so I can only comment on the overall look and feel. The solution is close to pixel perfect compared to the design specification. It looks good on different screen sizes.

  • Konrad•200
    @ExtendoGH
    Submitted 3 months ago
    What are you most proud of, and what would you do differently next time?

    This is my first project using JavaScript, so I'm really proud that I was finally able to add interactivity to the website. Next time, I’ll definitely have a better understanding of how to manage CSS classes like .hidden to control the visibility of elements more effectively.

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

    The biggest challenge I faced was styling the popup that needed to overlay certain parts of the project. Fortunately, with the help of ChatGPT, I managed to get it working and added a smooth show/hide animation, which really improved the overall user experience.

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

    I’d really appreciate any feedback, especially regarding the JavaScript code, since this was my first time writing it.

    Article Preview

    1
    P
    emawid•190
    @emawid
    Posted 3 months ago

    Great job on the challenge. The solution is almost pixel perfect. I can only spot a minor deviation on the mobile toaster which does not seem to have rounded edges. Layout looks good on all screen sizes, even with the toaster. Solution include semantic HTML and is well structured. Nice implementation of the JavaScript and use of classList and toggle().

  • P
    Andrew A Lee•380
    @drewlee
    Submitted 3 months ago
    What are you most proud of, and what would you do differently next time?

    I'm pleased I was able to get this complex layout fully responsive and smoothly transitioning between the three major screen sizes. I was also able to leverage both Flexbox and Grid for laying out the various components on the page. Next time, I would probably come up with a full-page systematic grid system to handle element positioning.

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

    The visual design features numerous inconsistencies in spacing and text wrap handling, which is somewhat ignorant of how CSS styling actually works. We should try to avoid having to hardcode text block widths and let text flow naturally to fit the screen width. While I understand adding complexity to make the exercise challenging, the visual treatment is not very practical in a real-world scenario.

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

    Ensuring adherence to best practices and modern coding conventions.

    Meet Landing Page

    1
    P
    emawid•190
    @emawid
    Posted 3 months ago

    Hi Andrew, Nice work with the landing page! Solution is almost pixel perfect. Good use of semantic html elements. For image elements, always provide a default width and height attribute as the browser will reserve space for it. If not provided overall page layout can jump around after page load. Accessibility could be further improved with ARIA labels. Solution looks good on different screen sizes.

View more comments
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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Oops! 😬

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

Log in with GitHub