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

Arash Asghari

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

  • Accessible Rating Component with Next.js

    #accessibility#framer-motion#next#tailwind-css

    Arash Asghari•220
    Submitted 3 days ago

    I'm always looking for suggestions on best practices, in this project especially for:

    • Next.js improvements, specifically better strategies for managing Server Component errors in a way that doesn’t disrupt user experience
    • Accessibility enhancements, making sure my implementation aligns with WCAG guidelines and utilizes ARIA attributes effectively

    Any insights or recommendations would be greatly appreciated!


    1 comment
  • Tip Calculator App Built with React, Zustand & Tailwind

    #jest#shadcn#zustand#react

    Arash Asghari•220
    Submitted 12 days ago

    I’m open to any suggestions regarding architecture, best practices, UI improvements, or optimization.


    1 comment
  • TTDashboard, Live Data with SWR and Styled with Tailwind

    #react#swr#tailwind-css#node

    Arash Asghari•220
    Submitted 20 days ago

    Any suggestion about any aspects of the project would be appreciated.


    1 comment
  • Newsletter Signup App using Redux and tailwindcss

    #react#redux#tailwind-css#react-hook-form

    Arash Asghari•220
    Submitted about 1 month ago

    I appreciate any suggestions for refining my approach.


    1 comment
  • Article Preview Page using MUI and Redux

    #material-ui#react#typescript#redux

    Arash Asghari•220
    Submitted about 1 month ago

    I would appreciate any suggestions, especially regarding best practices for using Redux.

    I’d love to hear your thoughts!


    1 comment
  • Responsive Testimonials Grid with Selectable Display Cards

    #framer-motion#react#tailwind-css#typescript

    Arash Asghari•220
    Submitted about 1 month ago

    I would appreciate any suggestions for improving performance, maintainability and structuring of the project.


    1 comment
View more solutions

Latest comments

  • Sanaz Bahmani•110
    @SanazBHMN
    Submitted 5 days ago

    Accessible, responsive components

    #accessibility#react#typescript#tailwind-css
    1
    Arash Asghari•220
    @AriArash44
    Posted 3 days ago

    Great job on the project! The UI is well-implemented and closely matches the design, and the code is clean and well-structured.

    One suggestion I have is to consider a more organized file structure within the src folder. For example, splitting page components and utility components into separate subfolders inside the components folder. This approach can significantly improve codebase maintainability, especially as the project scales.

    Overall, excellent work—keep it up!

  • P
    JeronimoCardu•490
    @JeronimoCardu
    Submitted 18 days ago

    Responsive tip-calculator

    #react#tailwind-css#vite#typescript
    1
    Arash Asghari•220
    @AriArash44
    Posted 12 days ago

    I checked out your project, and overall, it's really well-executed! The UI closely follows the original design, and the tip calculation works perfectly. Using Tailwind CSS, TypeScript, and React is a great choice for this kind of project—your tech stack is solid!

    A Few Suggestions for Improvement:

    • Restricting Alphabetical Input: To enhance usability, you might want to prevent users from entering non-numeric characters in the input fields. A simple regex like .replace(/[^0-9]/g, "") would help.
    • Custom Error Messages: If you don't like to restricting alphabetical inputs, Instead of the generic “Can't be zero” error message for all scenarios, consider providing more context-aware validation messages to improve the user experience.
    • Disabled Button Styling: You could use Tailwind’s disabled: modifier to change the reset button’s appearance when the user hasn’t filled the inputs yet. This would offer a clearer visual cue.
    • Tablet Screen Handling: I appreciate that you accounted for middle screen sizes, but the higher breakpoint seems a bit large for standard tablet dimensions. At those sizes, using the desktop UI might provide a better experience.

    Overall, great work! Keep it up.

    Cheers!

    Marked as helpful
  • P
    Shixu Luo•330
    @ShixuLuo
    Submitted about 1 month ago
    What specific areas of your project would you like help with?

    Any advice is welcome!

    Time tracking dashboard

    #tailwind-css
    1
    Arash Asghari•220
    @AriArash44
    Posted 20 days ago

    Your design is very similar to the original concept, and I love how you structured the UI—especially your handling of mid-range screen sizes. Overall, this is a fantastic implementation!

    For better project structure, I suggest using external scripts instead of writing JavaScript inside the HTML file. This follows the separation of concerns principle and improves maintainability.

    Additionally, applying cursor: pointer to hover states could enhance the website’s UX by making interactive elements more intuitive for users.

    Overally, Great work! 🚀

  • P
    Erik S. Carlsten•290
    @ecarlste
    Submitted about 1 month ago
    What are you most proud of, and what would you do differently next time?

    I liked how easy it was to produce a linear gradient background using tailwind. Since I was only using it in one place I simply used classes provided along with custom color classes I defined.

    If I had to use the same gradient in multiple components I would make a custom class for the gradient in the @theme section.

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

    For this particular challenge, I didn't run into anything I hadn't seen before and I didn't encounter any challenges while building the solution.

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

    I'd like feedback on my use of Semantic HTML more than anything.

    Responsive Newsletter Sign Up w/ NextJS/tailwind/zod/react-hook-form

    #next#react-hook-form#tailwind-css#typescript#zod
    1
    Arash Asghari•220
    @AriArash44
    Posted about 1 month ago

    Your project is really well done! I appreciate how you’ve incorporated metadata into the document, which enhances accessibility and SEO. The use of React Hook Form, Tailwind CSS, and other tools is a great choice—they contribute to a smooth development process and are promising for scalability.

    I also love how you've structured the project into different components, making it modular and easy to work with. Your approach to responsiveness, especially accommodating mid-range screen sizes, is impressive and ensures a seamless user experience across devices.

    One small suggestion for future improvements: structuring the project into directories like layouts or pages, and grouping the success page and signup page together, might make the structure more maintainable for larger-scale projects.

    Overall, fantastic job! 🚀 Keep up the great work.

    Marked as helpful
  • Gabriel Carreira•20
    @gabrielcarreira
    Submitted about 2 years ago

    Vite + React + Typescript + Material UI

    #react#typescript#vite#material-ui
    1
    Arash Asghari•220
    @AriArash44
    Posted about 1 month ago

    Overall, this is a solid implementation! One suggestion for improving the active state handling is to utilize the MUI Tooltip component.

    The Tooltip component allows you to wrap a child element that toggles between active and inactive states seamlessly. Additionally, it accepts a title attribute, which can receive JSX to dynamically render inside the tooltip.

    This approach could improve both usability and visual clarity like the design files, making the interactive elements more intuitive.

  • Alperen Aksoy•150
    @aksoyalpi
    Submitted about 1 month ago
    What are you most proud of, and what would you do differently next time?

    modular architecture thanks to react and scss

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

    publishing the react website with github pages, but now i got it => you have to create custom workflow with github actions.

    Responsive CSS Grid with react and Sass

    #react#sass/scss
    1
    Arash Asghari•220
    @AriArash44
    Posted about 1 month ago

    The grid works well and is nicely responsive! One small UI/UX suggestion: the card colors don’t match the design closely, and low contrast might make text harder to read—especially for those with vision difficulties. Adjusting the contrast could improve readability.

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