How festa-di-primavera/fdp-app works
Project type and purpose
• This is a full-stack web application built with SvelteKit for managing tickets, orders, check-ins, and earnings for an event (“Festa di Primavera 2024”).
• The project uses SvelteKit’s filesystem-based routing, server endpoints, and components for the UI; Firebase (Firestore) as its primary database; Lucia-Auth layered on Firestore; ReSend for transactional email; and is hosted/deployed via Vercel (with serverless functions and cron jobs).
File structure
• src/routes: SvelteKit pages (+page.svelte), server endpoints (+server.ts / +page.server.ts) for both UI and REST API under /api.
• src/components & src/lib: reusable UI components (charts, forms, feedback), helper libraries (authentication, Firebase client, utilities).
• Configuration files: svelte.config.js, vite.config.ts, tailwind.config.cjs, vercel.json (cron job, builds).
• package.json / pnpm-lock.yaml define dependencies (SvelteKit, Flowbite-Svelte, Tailwind, Lucia-Auth, Firebase, ReSend).
README for additional insights
• Tech stack calls out SvelteKit UI, Flowbite, Tailwind, Firebase (Firestore), Lucia-Auth, ReSend, Vercel deployment & cron job.
• Environment variables list clarifies the integration points for Firebase, Google OAuth, ReSend, and the Vercel cron secret.
Detail without over-splitting
• Essential integration points (DB, email, OAuth, cron) clearly.