The ultimate academic resource platform for BTECH students - where finding study materials stops being a struggle!
Explore the Project Internals »
Welcome! This is the central hub for Prepnerdz. For a deep dive into the project's architecture, setup, and contribution guidelines, please see our dedicated documentation:
- 📖 LEARN.md: Understand the project structure, database schema, and API.
- 🤝 CONTRIBUTING.md: Our main guide for contributors, with detailed setup and development instructions.
- 📜 CODE_OF_CONDUCT.md: Our community standards.
- Centralized Resources: Previous year papers (RGPV), Best notes, lab manuals etc.., all in one place
- Verified Content: Faculty and topper-approved materials
- Bookmarking: Save important resources for quick access
- Contribution System: Earn recognition for contributing useful content
| Frontend | Backend | Database |
|---|---|---|
| Next.js (TS) | Node.js | PostgreSQL |
| Tailwind CSS | Express.js | Prisma ORM |
- Node.js (v18+)
- PostgreSQL (v15+)
- Google Cloud account (for Drive API)
- Cloudinary APIs (for avatar/image uploads)
-
Clone the repository
git clone https://github.com/Shubhashish-Chakraborty/prepnerdz.git cd prepnerdz -
Install dependencies
npm install
PrepNerdz Frontend:
/apps/web
Backend :/apps/backend
Admin Panel:/apps/admin -
Set up environment variables
Create a
.envfile in the respective directories:- For frontend :
ENV SAMPLE - For Backend :
ENV SAMPLE - For Admin :
ENV SAMPLE
- For frontend :
-
Run the application
- In the Root directory, run the following command:
npm run dev
- If you want to run Individual apps:
- In the Frontend directory, run:
npm run dev - In the Backend directory, run:
npm run dev - In the Admin directory, run:
npm run dev
- In the Frontend directory, run:
- In the Root directory, run the following command:
We welcome contributions from the community! Please see our comprehensive Contributing Guide for detailed instructions.
Quick Summary:
- Fork the repository & clone your forked repository.
- Submit an issue or feature request.
- Create a new & separate branch for your feature or bug fix.
- Make your changes.
- Commit your changes with a clear and descriptive commit message.
- Push your changes to your forked repository.
- Create a pull request to the main repository.
- Wait for your pull request to be reviewed and merged.
- Your contribution is now part of PrepNerdz!
Finally you'll get a shoutout on LinkedIn and X (Twitter)!
MIT License - See LICENSE for details.
Inspired by the struggles of college students everywhere
Built with ❤️ for the academic community
