| # | Section | What's Inside |
|---|---|---|
| 01 | 🧠 About Me | Background, values & developer identity |
| 02 | 🔧 Tech Arsenal | Full breakdown of my stack by domain |
| 03 | ✨ Featured Projects | 4 highlighted builds with architecture notes |
| 04 | 🚀 Quick Start | Clone & run any of my projects in under 5 min |
| 05 | 🏗️ Development Workflow | How I architect, build, and ship software |
| 06 | 📊 GitHub Analytics | Stats, streak, language breakdown & activity |
| 07 | 🗺️ Roadmap & Currently Building | Active projects + 2025 learning plan |
| 08 | 🌊 Contribution Activity | Snake animation of my GitHub contributions |
| 09 | 🤝 Collaboration Guide | PR process, commit standards, issue labels |
| 10 | 📬 Let's Connect | Reach out — DMs are open |
Hey, I'm Suman — a full-stack developer from West Bengal, India who builds things for the web, the blockchain, and eventually the machines 🤖.
My core is the MERN stack, but I enjoy exploring across the whole product surface — from database schema design to crafting interfaces that feel fast and sharp. Currently expanding into Blockchain / Web3 with Solidity & Hardhat, and working through the fundamentals of Machine Learning and Data Science end-to-end.
What drives me:
- 🏗️ Building products that actually get used — not just demos
- 🧹 Writing code that future-me won't need to rewrite from scratch
- 📖 Learning in public and sharing what I discover along the way
- 🎨 Making UIs that look deceptively simple but work beautifully
const suman = {
role : "MERN Stack Developer",
location : "West Bengal, India 🇮🇳",
coreStack : [
"MongoDB", "PostgreSQL",
"Express.js", "React",
"Node.js", "TypeScript",
],
currentlyBuilding : [
"NFT-integrated ride booking platform ⛓️",
"End-to-end ML workflows for real-world use cases 🤖",
"Data analysis pipelines with Python, NumPy & Pandas 📊",
],
learning : [
"Data Analytics", "Machine Learning",
"Smart Contract best practices (Hardhat)",
"Scikit-Learn & model evaluation",
],
openTo : [
"Freelance projects",
"Open source collaboration",
"Blockchain / Web3 DApps",
"Beginner-friendly AI / Data Science projects",
],
funFact : "I debug best with lo-fi music and a cold cup of tea ☕",
contact : "sumansahaweb.dev@gmail.com",
};| ⚡ Primary Stack | ⛓️ Blockchain | 🎨 Design | 🤖 AI / ML | 🌐 Projects Shipped |
|---|---|---|---|---|
| MERN + TypeScript | Solidity / Hardhat | Figma + Blender | Actively Learning 🔄 | 4 Live ✅ |
My complete toolkit, organized by domain.
A selection of my most meaningful builds — each solving a real problem.
📂 View architecture, features & details
EduQuest is a production-grade e-learning platform on the MERN stack enabling course creation, enrollment, real-time progress tracking, and tiered role management.
Core Features
| Feature | Description |
|---|---|
| 🔐 Auth & Roles | JWT-based authentication with Student / Instructor / Admin tiers |
| 📹 Content Delivery | Structured course modules with progress tracking per user |
| 💳 Payments | Gateway integration for course purchase flows |
| 📱 Responsive UI | Tailwind-based layout optimized across all viewport sizes |
| 🔍 Search & Filter | Course discovery with category and skill-level filters |
Monorepo Architecture
eduquest/
├── client/ # React SPA (Vite + TypeScript)
│ ├── src/
│ │ ├── components/ # Reusable UI components
│ │ ├── pages/ # Route-level page components
│ │ ├── hooks/ # Custom React hooks
│ │ ├── store/ # Global state (Context / Redux)
│ │ └── utils/ # Helpers, formatters, validators
│ └── vite.config.ts
│
├── server/ # Express.js REST API
│ ├── routes/ # API route definitions
│ ├── controllers/ # Business logic handlers
│ ├── models/ # Mongoose schemas (User, Course, Enrollment)
│ ├── middleware/ # Auth, error handling, rate limiting
│ └── config/ # DB connection, env config
│
└── README.md
Tech Stack: MongoDB · Express.js · React · Node.js · JWT · Tailwind CSS
📂 View architecture, features & details
A fully custom Shopify theme built with Liquid templating and Tailwind CSS for a premium art frames product line. Prioritizes performance, conversion, and a premium feel.
Core Features
| Feature | Description |
|---|---|
| 🎨 Custom Liquid Sections | Built-from-scratch theme sections and blocks — no Debut/Dawn base |
| ⚡ Optimized Images | Responsive srcset delivery with native lazy loading |
| 📐 Product Configurator | Custom UI for frame size & material selection |
| 🛒 Enhanced Cart UX | Live cart updates, quantity controls, persistent cart state |
| 📊 Analytics Hooks | Storefront event tracking via Shopify Analytics |
Theme Architecture
framecraft-theme/
├── assets/ # CSS, JS bundles, fonts, SVGs
├── config/ # Theme settings schema
├── layout/ # theme.liquid (root shell)
├── sections/ # Reusable page sections
│ ├── hero-banner.liquid
│ ├── product-grid.liquid
│ └── product-configurator.liquid
├── snippets/ # Reusable partials
├── templates/ # Page, product, collection templates
└── locales/ # i18n translation strings
Tech Stack: Shopify Liquid · Tailwind CSS · Vanilla JavaScript
📂 View architecture, features & details
A decentralized warranty management system where warranties are minted as NFTs on-chain — verifiable, transferable, and tamper-proof without any trusted third party.
Core Features
| Feature | Description |
|---|---|
| 🔐 On-Chain Warranties | Warranties minted as ERC-721 NFTs on purchase |
| 🌐 IPFS Metadata | Product & warranty metadata stored immutably on IPFS |
| 🦊 Web3 Auth | MetaMask-based wallet authentication — no passwords |
| 🔄 NFT Transfers | Warranty follows the product when ownership transfers |
| ✅ Claim Verification | On-chain claim status — no central authority needed |
System Data Flow
┌───────────────────────────────────────────────────────────────────┐
│ PURCHASE FLOW │
│ Customer Buys Product → Smart Contract Mints NFT Warranty │
│ → Metadata stored on IPFS │
│ → NFT sent to buyer's wallet │
├───────────────────────────────────────────────────────────────────┤
│ TRANSFER FLOW │
│ Owner Transfers Product → NFT Transferred to New Wallet │
│ → New owner inherits warranty rights │
├───────────────────────────────────────────────────────────────────┤
│ CLAIM FLOW │
│ Owner Initiates Claim → Contract verifies NFT ownership │
│ → Claim event emitted on-chain │
│ → Resolution process begins │
└───────────────────────────────────────────────────────────────────┘
Tech Stack: Solidity · Hardhat · IPFS · Web3.js · React · Node.js
📂 View architecture, features & details
A zero-dependency, zero-backend image format converter built in pure Vanilla JS. All processing happens in the browser — no files ever leave the user's machine.
Core Features
| Feature | Description |
|---|---|
| 🔒 Privacy First | 100% client-side — no uploads, no server, no tracking |
| 🖼️ HEIC Support | HEIC/HEIF → JPEG/PNG via WebAssembly decoder |
| 📦 Bulk Convert | Process entire batches and download as a single ZIP |
| 👁️ Live Preview | Instant preview of converted output before download |
| ⚡ No Install | Runs directly in the browser — nothing to install |
Browser Processing Pipeline
File Input (drag & drop / picker)
│
▼
Format Detection (MIME type + magic bytes)
│
├── HEIC/HEIF → WASM Decoder → Canvas Render
├── PNG/JPG → FileReader API → Canvas Render
└── Other → Format Error feedback
│
▼
Canvas → Blob (target format)
│
▼
JSZip → ZIP Archive → Download trigger
Tech Stack: Vanilla JavaScript · WebAssembly · Canvas API · Python (CLI version)
Get any of my projects running locally in under 5 minutes.
⚙️ MERN Stack Projects
# 1. Clone the repo
git clone https://github.com/Suman-byte8/<repo-name>.git
cd <repo-name>
# 2. Install all dependencies (root + client + server)
npm install
cd client && npm install && cd ..
cd server && npm install && cd ..
# 3. Configure environment variables
cp server/.env.example server/.env
# → Fill in: MONGO_URI, JWT_SECRET, PORT
# 4. Run development servers (concurrently)
npm run dev
# Client: http://localhost:5173
# Server: http://localhost:5000⛓️ Solidity / Hardhat Projects
# 1. Clone and install
git clone https://github.com/Suman-byte8/<repo-name>.git
cd <repo-name>
npm install
# 2. Start a local Hardhat node
npx hardhat node
# 3. Deploy contracts to the local network
npx hardhat run scripts/deploy.js --network localhost
# 4. Run the test suite
npx hardhat test
# Expected: All tests passing ✓
# 5. Connect MetaMask to localhost:8545 (Chain ID: 31337)🐍 Python / Data Science Projects
# 1. Clone and enter directory
git clone https://github.com/Suman-byte8/<repo-name>.git
cd <repo-name>
# 2. Create and activate a virtual environment
python -m venv venv
source venv/bin/activate # macOS / Linux
# or: venv\Scripts\activate # Windows
# 3. Install dependencies
pip install -r requirements.txt
# 4. Launch Jupyter Notebook (if applicable)
jupyter notebook
# 5. Or run the script directly
python main.py🐳 Docker (where available)
# Clone and build
git clone https://github.com/Suman-byte8/<repo-name>.git
cd <repo-name>
# Build and start all services
docker-compose up --build
# Stop containers
docker-compose downHow I go from idea to shipped product — consistently.
flowchart LR
A([💡 Idea]) --> B[Research &\nRequirements]
B --> C[Architecture\n& Design]
C --> D[Repo Setup\n& Tooling]
D --> E[Build Core\nFeatures]
E --> F{Code Review\n& Tests}
F -- Issues Found --> E
F -- Approved --> G[Staging\nDeploy]
G --> H{QA &\nFeedback}
H -- Revisions --> E
H -- Ship It! --> I([🚀 Production])
I --> J[Monitor &\nIterate]
J --> E
style A fill:#0F4C81,color:#fff,stroke:#0F4C81
style I fill:#22c55e,color:#fff,stroke:#22c55e
style F fill:#f97316,color:#fff,stroke:#f97316
style H fill:#f97316,color:#fff,stroke:#f97316
My Engineering Principles
📐 Architecture First → Think before you type. Draw the system first.
🧪 Test As You Go → Catch bugs in development, not production.
📝 Document Always → Your future self and contributors will thank you.
🔄 Ship Small, Often → Frequent focused PRs beat massive rewrites.
♻️ DRY + SOLID → Write code once, compose it everywhere.
🔍 Read the Errors → Stack traces tell you exactly what to fix.
| # | Project | Status | Stack | Target |
|---|---|---|---|---|
| 1 | NFT Ride Booking Platform | 🔄 In Progress | Solidity, IPFS, React, Node.js | Q3 2025 |
| 2 | End-to-end ML Workflow | 🔄 Learning | Python, Pandas, Scikit-Learn | Q3 2025 |
| 3 | Data Visualization Dashboard | 📋 Planning | Python, Matplotlib, Streamlit | Q4 2025 |
| 4 | Smart Contract Security Auditing Practice | 📋 Planned | Hardhat, Slither | Q4 2025 |
2025 Learning Roadmap — Suman Saha
──────────────────────────────────────────────────────────────────────
Q1 ██████████ MERN Advanced Patterns & Architecture ✅ Complete
Q1 ██████████ TypeScript Deep Dive ✅ Complete
Q2 ████████░░ Smart Contracts (Hardhat + Solidity) 🔄 Active
Q2 ██████░░░░ Python for Data Science Foundations 🔄 Active
Q3 ░░░░░░░░░░ Machine Learning Fundamentals 📅 Planned
Q3 ░░░░░░░░░░ NFT & DeFi Protocol Development 📅 Planned
Q4 ░░░░░░░░░░ Full ML Project End-to-End 📅 Planned
Q4 ░░░░░░░░░░ Advanced AI API Integration 📅 Planned
──────────────────────────────────────────────────────────────────────
Legend: ██ Done ▓░ In Progress ░░ Planned
I believe great software is built collaboratively. Here's how to work with me.
| 🔧 Freelance Web Development | Full-stack MERN apps, pixel-perfect UI implementation, Shopify customization |
| ⛓️ Blockchain / Web3 Projects | Smart contract development, NFT systems, DeFi integrations, wallet UX |
| 🤖 AI & Data Science Collabs | Beginner-to-intermediate ML projects, data pipelines, analysis & visualization |
| 🌐 Open Source Contributions | Bug fixes, documentation improvements, feature additions to tools I use |
# Fork → Clone → Branch → Code → PR
# 1. Fork the repo on GitHub, then clone your fork
git clone https://github.com/<your-username>/<repo-name>.git
cd <repo-name>
# 2. Add the upstream remote
git remote add upstream https://github.com/Suman-byte8/<repo-name>.git
# 3. Create a clearly named feature branch
git checkout -b feature/add-user-auth
# or: bugfix/fix-cart-total
# or: docs/update-api-readme
# 4. Make your changes, then commit with Conventional Commits
git add .
git commit -m "feat: add JWT-based user authentication"
# Types: feat | fix | docs | style | refactor | test | chore
# 5. Sync with upstream before pushing
git fetch upstream
git rebase upstream/main
# 6. Push and open a Pull Request
git push origin feature/add-user-auth| Area | Standard |
|---|---|
| Commits | Conventional Commits — feat:, fix:, docs:, chore: |
| Branches | feature/, bugfix/, hotfix/, docs/ prefixes |
| Code Style | ESLint + Prettier (config shipped in every repo) |
| PRs | Clear description · screenshots for UI changes · passing CI |
| Issues | Use provided templates — bug report / feature request / question |
🔴 [P0] Critical → Blocking production use — addressed immediately
🟠 [P1] High → Core feature broken — next sprint priority
🟡 [P2] Medium → Non-blocking bug or improvement — scheduled
🟢 [P3] Low → Nice-to-have polish — when capacity allows
📘 [Help Wanted] → Well-defined issue open for community PRs
📗 [Good First Issue] → Perfect entry point for new contributors
Got a project idea? Want to collaborate? Just want to talk tech?
Reach out — I reply to everyone.
