How azizulabedinazmi/pocket-calendar works
Project type and purpose
• Pocket Calendar is a full-stack, server‐rendered web application built with Next.js 14’s App Router.
• It provides a weekly calendar interface, AI-assisted scheduling, analytics, weather integration, and optional cloud sync for personal and team use.
• Authentication is managed by Clerk; storage is a mix of LocalStorage (client), Vercel Blob or Misskey Drive (cloud).
File structure
• Top-level directories:
• app/ → Next.js App Router routes, layouts and server/client components
• app/api/ → serverless API route handlers (blob, chat, weather, share)
• components/ → reusable React UI components (account, analytics, sidebar, views)
• hooks/ → custom React hooks (toast, language, localStorage, mobile)
• lib/ → shared TypeScript utilities (i18n, ICS utils, analytics)
• Configuration files for build and deployment: next.config.mjs, bun.lock, tailwind.config.ts, tsconfig.json, middleware.ts.
README for additional insights
• Key features: AI scheduling, drag-and-drop UI, privacy (local first), optional cloud sync, multilingual, analytics, weather, import/export.
• Tech stack: Next.js, Tailwind CSS, shadcn/ui, TypeScript; Clerk auth; storage via LocalStorage, Vercel Blob, Misskey Drive; external APIs (OpenWeather, Groq).
• Deployment targets: Vercel or Netlify (serverless).