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

Leeh27

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

  • meu portfólio de dev


    Leeh27•80
    Submitted 10 months ago

    1 comment
  • News-homepage


    Leeh27•80
    Submitted 10 months ago

    Ainda tenho dificuldades com responsividade.


    1 comment
  • Perfil de links sociais


    Leeh27•80
    Submitted 10 months ago

    2 comments
  • html e css


    Leeh27•80
    Submitted about 1 year ago

    0 comments
  • HTML & CSS


    Leeh27•80
    Submitted about 1 year ago

    CSS e JavaScript


    1 comment

Latest comments

  • Ruslan B•60
    @rusbers
    Submitted 10 months ago
    What are you most proud of, and what would you do differently next time?
    • The extension of the original challenge by adding additional features like the Admin Dashboard and User Account management.
    • Successfully implementing a full-stack application using Next.js, especially as it was my first time working with this framework.
    • The integration of Cloudinary for secure storage of user avatars and show thumbnails.
    • The implementation of role-based access control (user and admin roles).

    To test the app, you can use the following credentials:

    User Role: Login: user1@example.com Password: 12345678

    Admin Role: Login: admin@example.com Password: 12345678

    What challenges did you encounter, and how did you overcome them?
    • Learning Next.js and its App Router as a first-time user.
    • Integrating full-stack components with Prisma and PostgreSQL.
    • Implementing secure authentication with NextAuth.js.
    • Incorporating Cloudinary for image management.
    • Efficient error handeling.
    What specific areas of your project would you like help with?

    To be honest, error handling across the app has been my biggest headache. I know I didn't do it properly, and I'm really looking for guidance here. I'm struggling with how to handle errors consistently, especially since we're dealing with both client-side and server-side stuff in Next.js. I'm not sure if I should be approaching server actions and database errors differently from other types of errors.

    I've tried some basic error handling, but it feels patchy at best. If anyone has experience with error handling in a Next.js, Prisma, and PostgreSQL stack, I'd really appreciate any tips, code examples, or resources you could share. I'm eager to learn and improve this aspect of my app.

    Entertainment Web App

    #next#prisma#tailwind-css#typescript#react
    1
    Leeh27•80
    @Leeh27
    Posted 10 months ago

    Ficou muito bom! Parabéns!!

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