How rahidmondal/t8d works
Project type and purpose
• From the file tree and README, T8D is a monorepo full-stack “offline-first” to-do list application.
• Frontend: React + TypeScript + Vite + Tailwind CSS, built as a PWA.
• Backend: Node.js/TypeScript sync server & API.
• Monorepo uses pnpm workspaces, Docker for production, GitHub Pages for frontend hosting.
File structure
• Top level:
• backend/ – Node API + sync server (package.json, tsconfig.node.json).
• frontend/ – React client (src/, public/, config, tests).
• docker-compose.prod.yml, monorepo config (pnpm-workspace.yaml, tsconfig.json).
• frontend/src organizes components (TodoList, Form, ThemeContext, etc.), models (Task, TaskList), utils (database adapter + todo logic).
• Tests folder parallels src for unit/integration tests.
• Dockerfiles & Caddyfile in frontend indicate containerized, static-server deployment.
• Workflow docs describe branching, CI/CD, release.
README for additional insights
• Emphasizes offline-first feature and private task management.
• Lists tech stack & deployment targets (Docker, GitHub Pages).
• Monorepo structure synopsis confirms clear frontend ↔ backend split.
Essential architectural elements
• Don’t just show “frontend” and “backend”—break out local DB, service worker, sync module, and persistent DB.
• Build/deployment artifacts only if the audience cares about ops; otherwise focus on runtime.