How evantechdev/one-calendar works
Project type and purpose
• This is a full-stack, single-page web application built with Next.js 14 (App Router).
• It provides a weekly calendar UI, user authentication, AI-powered features, optional cloud sync, weather integration, and local data storage.
File structure
• Top-level “app” directory holds all Next.js routes, layouts, and API endpoints:
• app/page.tsx, app/layout.tsx, app/not-found.tsx, app/sitemap.ts
• app/(app) and app/(auth) folders for protected vs. public pages
• app/api/{blob, chat, share, weather}/route.ts for serverless functions
• “components” folder groups UI building blocks by domain (account, analytics, event, home, sidebar, ui, view).
• “hooks” and “lib” folders contain custom React hooks and utility libraries (i18n, icsUtils, notifications, time-analytics).
• Configuration files: next.config.mjs, tailwind.config.ts, tsconfig.json, middleware.ts, .env.example
README for additional insights
• Frontend: Next.js + React + TypeScript + Tailwind + shadcn/ui
• Auth: Clerk (third-party session management)
• Data storage:
• Client-side: LocalStorage
• Cloud sync: Vercel Blob or Misskey Drive
• External APIs:
• Groq API (AI scheduling suggestions)
• OpenWeather API
• Hosting: Vercel or Netlify; runtime target Bun or Node