How hungluong05/schedura works
Project type and purpose
• This is a full-stack calendar events management system (“Schedura”) with a React/TypeScript frontend and a Node.js/Express backend.
• Purpose: allow users to register/login, view and manage events (with tags), and synchronize those events with Google Calendar and Microsoft Outlook.
File structure
• Top-level directories:
• backend/ – Express API server
• frontend/ – React SPA (Vite + TypeScript)
• Backend substructure follows an MVC-ish pattern:
• config/ – auth and environment setup (Google, Microsoft, JWT)
• controllers/ – request handlers (auth, events)
• routes/ – API endpoint definitions (auth.js, calendar.js, user.js)
• models/ – Mongoose (or similar) schemas for User and Event
• database/ – connection logic
• middlewares/ – authentication middleware
• utils/ – calendar_sync logic with external providers
• Frontend substructure is componentized:
• src/pages – top-level views (Auth, Calendar, Tasks)
• src/components – reusable UI parts (Auth, Calendar views, NavBar, SideBar)
• src/context – global AuthContext
• src/hooks – custom hooks (useAuth, useUser, useLocalStorage)
• src/utils – route protection, helper functions
• Config/build files: package.json, tsconfig, tailwind.config, vite.config, .env loading.
Insights from README
• Describes two-step startup (npm install & npm start/dev)
• Highlights Google & Microsoft sync, custom tags.
Detail guidance
• Call out the calendar_sync utility as the bridge to external calendars.
• On the frontend, show ProtectedRoute and AuthContext wrapping Calendar and Tasks pages.
• Don’t overcrowd: only include modules that impact data flow or responsibilities.