How rafixx/personal_schedule works
Project type and purpose
• This is a single-page web application (SPA) entirely running in the browser: a weekly meal-planner that persists data locally (IndexedDB via Dexie), lets users assign dishes to days (drag & drop), then computes and exports a consolidated shopping list.
File structure
• Top-level sources (src/):
• components/ – small, reusable UI pieces (DayCell, Toolbar, etc.)
• pages/ – route targets (PlannerPage, DishesPage, ShoppingListPage)
• layouts/ – shell around pages (DashboardLayout)
• shared/ – cross-cutting UI (Sidebar), routing definitions, helpers
• store/ – global state with Zustand (plannerStore.ts)
• data/ – Dexie DB schema (db.ts), repositories.ts, demo data
• domain/ – business logic (types, computeShoppingList)
• utils/, config files, public/ (static assets + sample menu.json), index.html
• Build & config: Vite (vite.config.ts), TypeScript (tsconfig.json), TailwindCSS, ESLint, Prettier, CI pipeline.
README
• Key features: drag & drop meal assignments, JSON import/export, local persistence, no server.
Main components & interactions
a. Presentation Layer
• Browser/Client
• index.html → main.tsx (React entry point)
• React Router (routes.tsx)
• DashboardLayout wraps individual Pages
• Pages composed of UI Components (PlannerView, WeekRow, DayCell, DishPicker, Toolbar) and shared Sidebar
b. State & Business Logic Layer
• Zustand store (plannerStore.ts): holds current plan, triggers updates
• Domain services (computeShoppingList in domain/shopping.ts): computes consolidated shopping list from state
• Utilities (date handling, helpers)
c. Data Persistence Layer
• Dexie-based repositories (data/repositories.ts) with IndexedDB schema (data/db.ts)
• Demo data loader (data/demo.ts)
• JSON import/export handlers (likely in shared/utils or domain)
d. External Libraries & Frameworks
• Vite (dev server, build pipeline)
• TailwindCSS for styling
• @dnd-kit for drag & drop interactions
Architectural patterns & principles
• Layered architecture (Presentation / State & Logic / Persistence)
• Repository pattern (abstract DB operations)
• Unidirectional data flow: UI actions → Zustand store → domain logic → persistence → UI
• Component-based design (atoms → molecules → organisms)
• SPA routing (React Router)
Detailed list of elements
• index.html & main.tsx entry
• Router component (routes.tsx)
• DashboardLayout
• PlannerPage, DishesPage, ShoppingListPage
• Core components: PlannerView, DayCell, WeekRow, DishPicker, Toolbar, Sidebar
• State container: plannerStore.ts
• Business logic: computeShoppingList (domain/shopping.ts)
• DB layer: db.ts, repositories.ts, IndexedDB
• Demo loader (demo.ts)
• JSON import/export module
• External services: @dnd-kit, Lucide-react, TailwindCSS, Vite dev/build