Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
21
Comments
31
Mudasir Nadeem
@mudasirNadeem

All comments

  • Raozhaizhu•580
    @raozhaizhu
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    I got too caught up in my responsive design experiment and forgot to implement a grid system for mobile compatibility. I'll redo it next time. I'm already tired.

    bookmark-landingmaste

    1
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 5 months ago

    updete your page '

  • P
    sophia-see•590
    @sophia-see
    Submitted 5 months ago

    Room Landing Page using HTML and CSS

    1
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 5 months ago

    greate

  • P
    sophia-see•590
    @sophia-see
    Submitted 5 months ago

    Loopstudios landing page using HTML and CSS

    1
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 5 months ago

    greate

  • Stefan Bojkovski•720
    @xStephx
    Submitted 5 months ago

    Solution Time tracking dashboard

    #tailwind-css
    14
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 5 months ago

    very greate you are outside from Frontend mentor why?

  • denise•510
    @moncadad
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    Proud of using React components, props and icons. Hopefully I get the hand of things sooner than later. Also yay me for completeing a lengthy project.

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

    Note to self with bolded/uppercase letters. "DON'T FORGET TO INCLUDE ALL YOUR NECESSARY DEPENDENCIES!!!" Basically, on this lovely project I decided to use React and Scss. Let's just say it took me the whole day to realize the live site wasn't configuring properly on Netlify due to I had completely forgot to install sass dependecies.

    Huddle landing page with alternating feature blocks

    1
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 5 months ago

    so greate

  • Sara-Mousa•120
    @Sarah-Mousa
    Submitted 6 months ago
    What are you most proud of, and what would you do differently next time?

    I am so happy cause I started to organize my code.

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

    ..

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

    I think the card is not in the middle despite putting display grid, place content center to the body element.

    nft-card

    #accessibility
    1
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 6 months ago

    greate

  • Stefan Bojkovski•720
    @xStephx
    Submitted 6 months ago

    Solution Social media dashboard with theme switcher

    #tailwind-css
    11
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 6 months ago

    greate

  • Willian Ernesto Arevalo Rodriguez•170
    @WillianArevalo
    Submitted about 1 year ago

    Ecommerce product page responsive

    1
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 7 months ago

    good

  • Stefan Bojkovski•720
    @xStephx
    Submitted 7 months ago

    Solution Newsletter sign-up form with success message

    #tailwind-css
    9
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 7 months ago

    good very good

  • Skyler Ang•330
    @skyleranglh
    Submitted 8 months ago

    News Homepage

    1
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 7 months ago

    Great job, Steven-Ang! Your use of semantic HTML and overall responsiveness is impressive. To improve, consider adding visible focus states for better keyboard navigation and ensure all form inputs have proper labels for accessibility. Keep up the great work!

  • P
    zhansayatazhibayeva•640
    @zhansayatazhibayeva
    Submitted 7 months ago

    Responsive time tracking dashboard

    1
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 7 months ago

    i think you did not understand his requerment please check my page https://mudasirnadeem.github.io/time-tracking-dashboard-main/ load data from json file click the weekly Daily and Monthly text I appropriate you bacause you ui is very best

  • P
    Austin•430
    @astnio
    Submitted 8 months ago
    What are you most proud of, and what would you do differently next time?

    I mostly learned how to style forms further, along with validation via JavaScript. I had done a smaller version of this before, but this was a bit more complicated as this had several elements to manage.

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

    I find that I struggle to remember how to style form elements often. With how common this seems to be I feel as though I should take some notes to refer to, as I find myself going back and having to research how to style certain elements repeatedly.

    Responsive Form with Validation and Animation

    1
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 7 months ago

    Your use of semantic HTML is strong, and adding aria-live to form validation would enhance accessibility. The layout works well on small screens, but more spacing could improve larger screen designs. Refactoring repetitive styles into reusable classes would help maintainability.

  • BaiacuPlays•70
    @BaiacuPlays
    Submitted 9 months ago

    accordionfaq

    1
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 8 months ago

    very good

  • Stefan Bojkovski•720
    @xStephx
    Submitted 8 months ago

    Solution Project tracking intro component

    #tailwind-css
    10
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 8 months ago

    greate

  • Eduardo•40
    @MrRedu
    Submitted 8 months ago

    Social links profile [Vanilla]

    2
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 8 months ago

    greate

  • Stefan Bojkovski•720
    @xStephx
    Submitted 8 months ago

    Solution Coding bootcamp testimonials slider

    #tailwind-css
    4
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 8 months ago

    very greate

  • Mudasir Nadeem•430
    @mudasirNadeem
    Submitted 8 months ago
    What are you most proud of, and what would you do differently next time?

    I’m proud of completing the project successfully and implementing a responsive design that works well across devices. Additionally, I improved accessibility by adding clear navigation and text contrasts.

    What would you do differently next time? Next time, I would focus more on optimizing my code for performance and ensuring better cross-browser compatibility. I’d also spend more time testing for edge cases and user feedback before launch.

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

    One challenge I faced was ensuring the layout was responsive on all devices. To overcome this, I researched media queries and used a mobile-first approach, which made the design adaptable to different screen sizes. I also encountered issues with some JavaScript functionality, which I solved by debugging the code step by step and seeking help from online communities.

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

    I would appreciate feedback on the following areas:

    Code Optimization: Are there parts of my code that could be more efficient or simplified? Accessibility: Does the project meet accessibility standards, especially for users with disabilities? Cross-Browser Compatibility: Are there any issues with how my project works across different browsers or devices? Being specific in these areas will help me improve and refine my project further.

    interactive-rating-component-main

    2
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 8 months ago

    Semantic HTML: Great job using semantic HTML elements! This enhances accessibility and SEO. Ensure all sections use appropriate tags to convey meaning effectively.

    Accessibility: The solution is generally accessible, but consider these improvements:

    Add alt attributes to images for better screen reader support. Ensure all interactive elements, like buttons and links, have visible focus states to improve navigation for keyboard users. Responsive Layout: The layout looks good on various screen sizes. It’s essential to test on smaller devices to ensure there are no issues with overflow or alignment.

    Code Structure: The code is well-organized and easy to read. Consider breaking larger functions into smaller, reusable components for better maintainability.

    Design Consistency: The solution closely follows the original design, with only minor deviations that don’t impact usability.

    Overall, this is a solid solution with just a few areas for improvement. Keep up the great work!

  • Mudasir Nadeem•430
    @mudasirNadeem
    Submitted 8 months ago
    What are you most proud of, and what would you do differently next time?

    I’m proud of completing the project successfully and implementing a responsive design that works well across devices. Additionally, I improved accessibility by adding clear navigation and text contrasts.

    What would you do differently next time? Next time, I would focus more on optimizing my code for performance and ensuring better cross-browser compatibility. I’d also spend more time testing for edge cases and user feedback before launch.

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

    One challenge I faced was ensuring the layout was responsive on all devices. To overcome this, I researched media queries and used a mobile-first approach, which made the design adaptable to different screen sizes. I also encountered issues with some JavaScript functionality, which I solved by debugging the code step by step and seeking help from online communities.

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

    I would appreciate feedback on the following areas:

    Code Optimization: Are there parts of my code that could be more efficient or simplified? Accessibility: Does the project meet accessibility standards, especially for users with disabilities? Cross-Browser Compatibility: Are there any issues with how my project works across different browsers or devices? Being specific in these areas will help me improve and refine my project further.

    interactive-rating-component-main

    2
    Mudasir Nadeem•430
    @mudasirNadeem
    Posted 8 months ago

    Semantic HTML: The solution effectively uses semantic HTML elements, which helps with accessibility and SEO. Consider using more specific tags (like <article>, <aside>, or <nav>) where appropriate to enhance clarity.

    Accessibility: Overall, the solution is accessible, but here are some improvements:

    Ensure all images have alt attributes for screen readers. Check that interactive elements (like buttons and links) have clear focus states. Responsive Layout: The layout adapts well across different screen sizes. It would be helpful to test on various devices, especially mobile, to ensure there are no overflow issues or misalignments.

    Code Structure: The code is well-structured and readable, making it easy to follow. Consider breaking larger functions into smaller, reusable components to improve maintainability.

    Design Consistency: The solution closely aligns with the original design. If there are any differences, they are minor and do not detract from the overall user experience.

    Overall, this is a strong solution with minor areas for improvement. Great job, and keep up the excellent work!

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

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