[Submission] Genesis — StoryForge

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Abhishek-Dige
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,146 +1,58 @@
-# DevStakes (Axios Web Wing)
+# StoryForge- By Team Genesis
 
+Welcome to the StoryForge repository!original repo -https://github.com/Abhishek-Dige/DevStakes.git
 
-**[Register Here →](https://forms.gle/yrQVjSU84b2Wk47Q8)**
+## 📂 Project Structure
 
----
+This project is divided into four main directories:
 
-## Event Overview
+- **`/client`**: The frontend application. Contains the UI components, state management, and user-facing features.
+- **`/server`**: The backend server. Contains the API routes, business logic, middleware, and our main entry point (`server.js`).
+- **`/database`**: Database scripts, connection utilities, schemas, and migrations.
+- **`/docs`**: Project documentation, design specifications, architecture diagrams, and reference materials.
 
-| Detail | Info |
-|---|---|
-| Duration | 3.5 days (84 hours) |
-| Team Size | 4-5 members (at least 1 girl mandatory) |
-| Primary Focus | React (Frontend) |
-| Bonus Points | Up to +20 for backend, ML integration, or strong system design |
+## 👥 Team Structure
 
----
+Our team consists of 5 members, divided into focused roles to ensure smooth and efficient development:
 
-## Timeline
+- **Frontend Team (2 Members)**: Responsible for building the `/client` directory, focusing on UI/UX, interface components, and API integration.
+- **Backend Team (2 Members)**: Responsible for the `/server` and `/database` directories, focusing on system architecture, database schema, API logic, and secure routing.
+- **Project Coordinator (1 Member)**: Abhishek is the Project Coordinator. He will be coordinating tasks between the frontend and backend teams.
 
-### Day-0
+## 🌿 Git Discipline & Workflow
 
-| Time | Activity |
-|---|---|
-| 12:00 PM | Ideas revealed — teams choosing from the given set can start coding immediately |
-| 12:00 PM – 6:00 PM | Custom Idea Submission Window |
-| 10:00 PM | Idea approval results announced — event officially starts for all teams |
+To maintain a clean, stable codebase and avoid stepping on each other's toes, all collaborators **must** adhere to the following Git workflow:
 
-### Day-1, Day-2, Day-3 — Coding Period
+1. **Never commit directly to `main`.** 
+   The `main` branch should always represent the stable, working state of our application.
 
-- Coding stops at the **end of Day-3**
-- The **top 5 teams** may be called for an **offline pitch** to explain their codebase and demonstrate understanding
-- Top 3 winners are decided from the offline pitch
+2. **Always pull the latest changes before starting work.**
+   ```bash
+   git checkout main
+   git pull origin main
+   ```
 
----
+3. **Create a new branch for every task.** 
+   Use descriptive branch names (e.g., `feature/login-page`, `bugfix/api-crash`, `setup/database-schema`).
+   ```bash
+   git checkout -b feature/<your-feature-name>
+   ```
 
-## Scoring Criteria
+4. **Commit your work with clear messages.**
+   Make small, atomic commits rather than one massive commit. 
+   ```bash
+   git add .
+   git commit -m "feat: setup basic user schema"
+   ```
 
-| Criterion | Description | Points |
-|---|---|---|
-| Core Functionality | Does it actually work end-to-end? | 30 |
-| UI / UX Quality | Visual polish, responsiveness, usability | 20 |
-| Performance | Lighthouse score — speed, accessibility, SEO | 15 |
-| Clean Code & Structure | Readable, modular, no spaghetti | 15 |
-| Git Practices | Commits, branching, PRs with descriptions | 10 |
-| Deployed & Live Link | Vercel / Netlify, accessible URL submitted | 5 |
-| Idea Bonus *(custom only)* | Originality & quality of self-proposed idea | 0–5 |
-| **Total** | | **100** |
+5. **Push your branch to the shared repository:**
+   Since everyone is a collaborator, you can push your branch directly to the main repository.
+   ```bash
+   git push -u origin feature/<your-feature-name>
+   ```
 
-> **+20 bonus points** available for implementing a backend, integrating ML models, or demonstrating strong system design.
+6. **Merge / Pull Request:** 
+   Submit a Pull Request from your branch to the `main` branch. 
 
----
-
-## Ideas
-
-You may choose **one** of the ideas below, or propose your **own custom idea** (subject to approval, eligible for up to 5 bonus points).
-
----
-
-### 1. Real-Time "Auction/Bidding" Portal
-
-A high-adrenaline platform where unique items are put up for timed, live auctions, requiring instant feedback and a seamless user experience.
-
-- **Frontend Challenge:** Handling race conditions and state synchronization. When two users bid at the exact same millisecond, the frontend must handle "Optimistic Updates" (showing the user's bid immediately for a snappy UX) while simultaneously validating against the server clock to handle rejections gracefully.
-- **Practical Use:** E-commerce, charity fundraisers, or digital asset trading.
-
----
-
-### 2. Smart "Expense Splitter"
-
-A comprehensive financial utility to manage group expenses, track shared bills, and "settle up" debts among friends or roommates.
-
-- **Frontend Challenge:** Building intuitive, dynamic forms for complex splits (e.g., "A paid 70%, B and C split the rest, but D owes for drinks"). Managing complex localized state without lagging the UI.
-- **Algorithmic Complexity:** The "Simplifying Debts" algorithm (often solved using graph theory/flow networks). If A owes B $10 and B owes C $10, the system should suggest A pays C $10 directly. Handling math precision and multi-currency conversions locally in the browser.
-- **Practical Use:** Essential for university students living in hostels, shared flats, or group travel.
-
----
-
-### 3. Dynamic Team Builder
-
-An intelligent matching platform where users input their skills, and the system automatically forms balanced, highly functional teams based on specific event constraints.
-
-- **Frontend Challenge:** Creating a rich, interactive drag-and-drop interface (similar to a Kanban board) where organizers can visually tweak the auto-generated teams. Visualizing skill distributions using charts (e.g., radar charts for team stats).
-- **Algorithmic Complexity:** Constraint satisfaction. If 80% of users are frontend developers and 20% are designers, the system must still create fair teams without perfect combinations, distributing the rare skills evenly.
-- **Practical Use:** Automating team formation for hackathons, college projects, or corporate workshops.
-
----
-
-### 4. Smart "Exam Preparation Planner"
-
-An adaptive study schedule generator that takes a student's syllabus, available hours, and target grades to map out a day-by-day learning journey.
-
-- **Frontend Challenge:** Building interactive calendars, Gantt charts, or timeline views from scratch in React. Handling complex date/time logic and allowing users to drag, drop, and resize study blocks.
-- **Algorithmic Complexity:** Priority-based time allocation. What happens when time is insufficient for full syllabus coverage? The system must dynamically recalculate and prioritize high-weightage topics over minor ones.
-- **Practical Use:** Helping students manage time efficiently and reduce pre-exam anxiety.
-
----
-
-### 5. Visual Node-Based Learning Roadmap Builder
-
-A platform where educators or seniors can create interactive, branching "tech trees" (like in video games) for learning new skills (e.g., "How to learn Web Dev").
-
-- **Frontend Challenge:** Heavy manipulation of the DOM and Canvas/SVG. Using libraries like React Flow to let users drag nodes, connect them with animated edges, zoom, pan, and handle complex graph state management in the browser.
-- **Practical Use:** Replacing static PDF roadmaps with interactive, trackable learning journeys for college clubs or online courses.
-
----
-
-### 6. Offline-First Markdown Note-Taking App
-
-A distraction-free, highly performant note-taking application designed for developers and students, capable of working entirely offline.
-
-- **Frontend Challenge:** Building a rich text editor that parses Markdown to HTML in real-time. Implementing an "Offline-First" architecture using IndexedDB/Service Workers in React, ensuring the user can close the tab, lose internet, and never lose a keystroke.
-- **Practical Use:** A lightweight Notion/Obsidian alternative tailored for rapid class notes or code snippets.
-
----
-
-### 7. Custom Idea *(Bonus: up to 5 points)*
-
-Have a unique idea not listed above? Propose it!
-
-- Each team can submit **at most 2 custom ideas** during the Day-0 submission window (12PM–6PM).
-- Approved ideas earn an **idea bonus of 0–5 points** based on originality and quality.
-- Approval results are announced at **10PM on Day-0**.
-
----
-
-## Rules
-
-1. Teams must have **4 to 5 members**, with **at least 1 girl**.
-2. The primary tech stack must be **React based** (frontend-first).
-3. Each team must choose **one idea** — either from the given set or a custom approved idea.
-4. Teams submitting a custom idea can submit a **maximum of 2 ideas** for review.
-5. Teams selecting from the given set may **begin coding at 12PM on Day-0**.
-6. Custom idea teams may begin coding (for custom idea) only after **approval at 10PM on Day-0**.
-7. All code must be pushed to a **Git repository** with clear commit history, branching, and PR descriptions.
-8. A **deployed live link** (Vercel/Netlify) must be submitted for full scoring.
-9. Coding officially **stops at the end of Day-3**.
-10. Top 5 teams may be invited for an **offline pitch** to verify codebase understanding.
-
----
-
-## Registration
-
-**[Fill the Registration Form →](https://forms.gle/yrQVjSU84b2Wk47Q8)**
-
----
+7. **Code Review & Merge:** 
+   The Project Coordinator (Abhishek) will review the code, ensure it works correctly without breaking existing features, and then merge it into `main`. Once merged, delete your feature branch and start the cycle again!

teams/Genesis/storyforge/.gitignore

@@ -0,0 +1,3 @@
+node_modules
+.env
+.DS_Store

teams/Genesis/storyforge/client/Story_Forge_Frontend/.gitignore

@@ -0,0 +1,24 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+lerna-debug.log*
+
+node_modules
+dist
+dist-ssr
+*.local
+
+# Editor directories and files
+.vscode/*
+!.vscode/extensions.json
+.idea
+.DS_Store
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?

teams/Genesis/storyforge/client/Story_Forge_Frontend/README.md

@@ -0,0 +1,16 @@
+# React + Vite
+
+This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
+
+Currently, two official plugins are available:
+
+- [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react) uses [Oxc](https://oxc.rs)
+- [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react-swc) uses [SWC](https://swc.rs/)
+
+## React Compiler
+
+The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see [this documentation](https://react.dev/learn/react-compiler/installation).
+
+## Expanding the ESLint configuration
+
+If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the [TS template](https://github.com/vitejs/vite/tree/main/packages/create-vite/template-react-ts) for information on how to integrate TypeScript and [`typescript-eslint`](https://typescript-eslint.io) in your project.

teams/Genesis/storyforge/client/Story_Forge_Frontend/eslint.config.js

@@ -0,0 +1,29 @@
+import js from '@eslint/js'
+import globals from 'globals'
+import reactHooks from 'eslint-plugin-react-hooks'
+import reactRefresh from 'eslint-plugin-react-refresh'
+import { defineConfig, globalIgnores } from 'eslint/config'
+
+export default defineConfig([
+  globalIgnores(['dist']),
+  {
+    files: ['**/*.{js,jsx}'],
+    extends: [
+      js.configs.recommended,
+      reactHooks.configs.flat.recommended,
+      reactRefresh.configs.vite,
+    ],
+    languageOptions: {
+      ecmaVersion: 2020,
+      globals: globals.browser,
+      parserOptions: {
+        ecmaVersion: 'latest',
+        ecmaFeatures: { jsx: true },
+        sourceType: 'module',
+      },
+    },
+    rules: {
+      'no-unused-vars': ['error', { varsIgnorePattern: '^[A-Z_]' }],
+    },
+  },
+])

teams/Genesis/storyforge/client/Story_Forge_Frontend/index.html

@@ -0,0 +1,16 @@
+<!doctype html>
+<html lang="en">
+
+<head>
+  <meta charset="UTF-8" />
+  <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
+  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+  <title>StoryForge</title>
+</head>
+
+<body>
+  <div id="root"></div>
+  <script type="module" src="/src/main.jsx"></script>
+</body>
+
+</html>