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

📜Full Stack Recipes Web App | Prisma | Tailwind | NextJS | Vitest📜

next, prisma, tailwind-css, vitest, react
Sam•1,190
@JustANipple
A solution to the Recipe page 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?
  • Protein based macros adaption: In the details of a recipe, you can insert your personal macros and that recipe will be adapted to reach your protein level
What challenges did you encounter, and how did you overcome them?
  • Database: i made use of Supabase and Prisma to host and create a consistent relational database for my recipes. I also used Vitest to test my queries.
  • Backend: i had a decent grasp of React, so i wanted to give my project a structure with NextJS and Vercel to host it.
  • Frontend: i used Tailwind to style my project. Very easy to get into and with the help of a very good design from FrontendMentor i was able to get started.
What specific areas of your project would you like help with?
  • Authentication: this would let me choose which users can access the site. Also i could give different permissions to users to let them edit their own recipes, while others can only see them.
  • API: ingredients are a bit complex to create and not as user friendly as it should be. Making use of an API would help a lot creating recipes without caring much about macros
  • Error handling: i'm not sure how to handle errors in my app. It's not clear what part of the app is responsible for throwing errors.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Sam's solution.

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.