Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

fullstack comment section

framer-motion, next, react, node
Marvellous Obatale•520
@MARVELGARR
A solution to the Interactive comments section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Exciting Journey: Building a Full-Stack CRUD App with Next.js, Tailwind CSS, MongoDB, Prisma, and AutoAnimate! 🌐✨

🌟 What began as a frontend project turned into an incredible exploration of Next.js' full-stack capabilities. Today, I'm thrilled to share the journey behind creating a powerful full-stack application that seamlessly combines frontend magic, data management, stunning designs, and captivating animations. Let's dive in!

🔨 Tech Stack Highlights 🔨

Next.js: For the frontend, I chose Next.js, and it proved to be a game-changer. Its speed and versatility in handling dynamic pages through server-side rendering and static site generation set the foundation for a smooth user experience.

Tailwind CSS: To make the application visually stunning, I leveraged Tailwind CSS. Its utility-first approach allowed for rapid UI development and a polished look that users love.

MongoDB: For data storage, MongoDB came into play. Its flexibility and scalability made it the ideal choice for managing the application's data.

Prisma ORM: To handle database queries, Prisma ORM was my go-to tool. With Prisma, complex database operations became incredibly straightforward, saving me time and effort.

AutoAnimate: To add the 'wow' factor, AutoAnimate was introduced for captivating animations. These animations brought the app to life and enhanced user interactions.

👉 Frontend Magic 👈

The frontend journey with Next.js was a breeze. Server-side rendering and static site generation made building dynamic pages a joy. The application's frontend became responsive, efficient, and user-friendly.

🧙‍♂️ State Management Sorcery 🧙‍♂️

Managing application state was made simple with Redux. It handled complex data flows seamlessly, ensuring a predictable and smooth user experience.

🔐 User Authentication Fortified 🔐

User authentication was a vital component, and Next-Auth came to the rescue. Securing routes, managing sessions, and handling user data became a walk in the park, enhancing the application's security.

🏢 Database Powerhouse 🏢

MongoDB and Prisma ORM proved to be a dynamic duo. MongoDB efficiently managed data storage, while Prisma ORM simplified complex database operations, ensuring optimal performance.

🌀 Animation Enchantment 🌀

AutoAnimate added the 'wow' factor to the app. Engaging animations brought the application to life, making user interactions fun and captivating.

In the end, what began as a frontend project evolved into a full-stack masterpiece. The powerful combination of Next.js and this impressive tech stack allowed me to create an application that's both functional and visually appealing.

🚀✨ Check out the app here: [Link to your app]

Thank you to everyone who contributed to this journey and made it possible. 🙌 Let's continue pushing the boundaries of technology and innovation! 🌟

#FullStackDevelopment #NextJS #TailwindCSS #MongoDB #Prisma #AutoAnimate #WebDevelopment #Innovation #CodingJourney 🚀✨

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Marvellous Obatale'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.