• 🚀 Project Overview
• 🌐 Live Demo
• ✨ Features
• 🏗 Tech Stack
• 📂 Project Structure
• ⚡ Quick Start
• 🔐 Environment Variables
• 🌐 Google Authentication Setup
• ❓ FAQ
• 🛠 Troubleshooting
• 🤝 Contribution Guidelines
• 🏷 Issue Guidelines
• 📸 Screenshots
• 📬 Getting Help
• 📬 Contact & Community

Most productivity tools are either too bloated or too simple. DailyForge is a no-nonsense weekly planner that gives you total control over your schedule — built by students, for students and professionals alike.

What it does:

• Build a reusable task library with custom durations, colors, and categories
• Design weekly routines by dragging tasks into a visual time grid
• Save, update, and delete routines with one click
• Automatically detects and prevents scheduling conflicts for the same day

Why it matters:
Most people don't fail to plan — they fail to stick to a plan. DailyForge makes routines feel visual and deliberate, making habits easier to build and track.

Key highlights:

• ⚡ Drag-and-drop weekly planner powered by @dnd-kit
• 🔒 Secure JWT authentication with bcrypt password hashing
• 🗂️ Reusable routine templates to clone and reuse schedules
• 🚫 Conflict detection — no overlapping tasks on the same day
• 📱 Clean, responsive UI built with React 19 + Tailwind CSS v4

⚠️ Deployed on Render's free tier — first load may take 30–60 seconds to spin up.

• Signup / Login with JWT-based session management
• Protected routes — unauthenticated users are redirected to login
• Passwords hashed with bcrypt

• Create tasks with: title, duration, color, and category
• Edit and delete tasks from your personal task library
• Tasks persist across sessions

• Drag tasks from your library onto a 7-day weekly grid
• Time-slot-based placement with visual feedback
• Overlap detection prevents conflicting task placement on the same day

• View all saved routines at a glance
• Quick access to edit or delete any routine
• Summary stats for your weekly schedule

• Save any routine as a reusable template
• Re-apply templates to any week in seconds

DailyForge/
│
├── backend/
│   ├── config/                 # DB connection config
│   ├── controllers/
│   │   ├── authController.js   # Signup, login logic
│   │   ├── routineController.js
│   │   └── taskController.js
│   ├── middlewares/
│   │   └── authMiddleware.js   # JWT verification
│   ├── routes/
│   │   ├── authRoutes.js
│   │   ├── routineRoutes.js
│   │   └── taskRoutes.js
│   ├── src/
│   │   ├── models/             # Mongoose schemas
│   │   │   ├── User.model.js
│   │   │   ├── Task.model.js
│   │   │   └── Routine.model.js
│   │   └── server.js           # Express app entry point
│   ├── .env                    # ← You create this (see below)
│   └── package.json
│
└── frontend/
    ├── public/
    ├── src/
    │   ├── api/
    │   │   └── axiosConfig.js  # Axios base URL config
    │   ├── components/
    │   │   ├── Dashboard/
    │   │   ├── Routine/
    │   │   ├── Task/
    │   │   ├── Navbar.jsx
    │   │   └── ProtectedRoutes.jsx
    │   ├── context/
    │   │   └── AuthContext.jsx
    │   ├── hooks/
    │   │   └── useTasks.js
    │   ├── pages/
    │   │   ├── Dashboard.jsx
    │   │   ├── RoutineBuilder.jsx
    │   │   ├── Tasks.jsx
    │   │   ├── Login.jsx
    │   │   └── Signup.jsx
    │   ├── utils/
    │   ├── App.jsx
    │   └── main.jsx
    ├── index.html
    ├── vite.config.js
    └── package.json

Prerequisites: Node.js v18+, npm v9+, a free MongoDB Atlas account

git clone https://github.com/aryandas2911/DailyForge.git
cd DailyForge

cd backend
npm install

Create your .env file from the given template (see the Environment Variables section below):

# Inside the /backend directory

cp .env.example .env   

Then fill in your values (see the next section for what each variable means).

⚠️ Local dev note: The backend CORS origin is already configured for both the deployed frontend (https://dailyforge-frontend-lhjq.onrender.com) and local development (http://localhost:5173) in backend/src/server.js. No changes are needed for local development.

Start the backend dev server:

npm run dev

✅ Server should start at http://localhost:5000

Open a new terminal, then:

cd frontend
npm install

💡 Local dev note: To point the frontend to your local backend, copy frontend/.env.example to frontend/.env and ensure VITE_API_URL is set to http://localhost:5000/api.

Start the frontend dev server:

npm run dev

✅ App should open at http://localhost:5173

Open http://localhost:5173, sign up for an account, and start building your routines.

Copy the provided template to get started. Never commit the .env to git.

PORT=5000
MONGO_URI=your_mongodb_atlas_connection_string
JWT_SECRET=your_super_secret_key_here
#CLIENT_ORIGIN=your_deployed_frontend_url

How to get MONGO_URI:

1. Log into MongoDB Atlas
2. Create a free M0 cluster (if you haven't)
3. Click Connect → Connect your application → Copy the connection string
4. Replace <password> with your DB user's password

Copy the provided .env.example to a new file named .env.

Running locally? Update VITE_API_URL in your local .env file to http://localhost:5000/api/.

DailyForge supports Google Authentication via Firebase. Follow these steps to configure and enable Google Sign-In:

1. Go to the Firebase Console and click Add project to create a new project.
2. Once the project is created, click the Web icon (</>) on the Project Overview page to register a new Web App.
3. Copy the firebaseConfig object containing the API key, app ID, etc.
4. Go to Build → Authentication in the left sidebar and click Get Started.
5. Under the Sign-in method tab, click Add new provider and select Google.
6. Enable the provider, configure your support email, and click Save.

To enable the frontend and backend integration, copy the configuration values into your respective .env files:

Append your Firebase client configuration to your local .env file:

# Firebase Client configuration
VITE_FIREBASE_API_KEY=your_api_key
VITE_FIREBASE_AUTH_DOMAIN=your_auth_domain
VITE_FIREBASE_PROJECT_ID=your_project_id
VITE_FIREBASE_STORAGE_BUCKET=your_storage_bucket
VITE_FIREBASE_MESSAGING_SENDER_ID=your_messaging_sender_id
VITE_FIREBASE_APP_ID=your_app_id

Add your Firebase Project ID to secure RS256 token verification:

# Firebase verification configuration
FIREBASE_PROJECT_ID=your_project_id

The project is deployed on Render’s free tier. Services may go to sleep after inactivity, so the first request can take around 30–60 seconds to respond.

Recommended versions:

• Node.js v18+
• npm v9+

Check your installed versions:

node -v
npm -v

No. DailyForge uses MongoDB Atlas, so you only need a free Atlas account and a valid connection string.

Make sure:

• Backend CORS origin is set to:

origin: "http://localhost:5173"

• Frontend .env contains:

VITE_API_URL=http://localhost:5000/api

Backend variables go inside:

/backend/.env

Frontend variables go inside:

/frontend/.env

We love contributions! DailyForge is actively participating in GSSoC 2026 and welcomes contributors of all experience levels.

📄 Read the full guidelines: CONTRIBUTING.md

1. Pick an issue

• Browse open issues
• Look for good first issue if you're new
• Comment on the issue to get it assigned before starting work

2. Fork & branch

git clone https://github.com/<your-username>/DailyForge.git
cd DailyForge
git checkout -b <type>/<short-description>

Branch naming convention:

3. Make your changes

• Keep changes focused — one issue per PR
• Follow the existing code style
• Test your changes locally before pushing

4. Open a Pull Request

• Fill out the PR template completely
• Link the issue it resolves using Closes #<issue-number>
• Request a review from a maintainer

⚠️ PRs without a linked issue or description will not be reviewed.

We use labels to organize work. Here's what they mean:

Tips for new contributors:

• Start with good first issue — they're designed to be approachable
• Don't hesitate to ask questions in the issue comments
• One issue at a time — don't take on multiple issues until your first PR is merged

Need help with setup or contributing?

• Open a GitHub Issue
• Comment on an existing issue for clarification
• Contact the maintainer through the email provided below

• Read the setup instructions carefully
• Check the FAQ and Troubleshooting sections
• Search existing GitHub issues first

We welcome contributors of all experience levels 🚀

Have questions, ideas, or want to connect with other contributors?