How thekovie/palatepicks works
Project type and purpose
• PalatePicks is a full-stack, server-side-rendered (SSR) web application built on Nuxt.js.
• It targets students who want to discover and review budget-friendly restaurants.
• It leverages Supabase for authentication, database (PostgreSQL), and file storage.
File structure
Top level
• nuxt.config.ts, package.json, pnpm-lock.yaml – Nuxt configuration and dependencies
• tsconfig.json, server/tsconfig.json – TypeScript settings for client and any server folders
• tailwind.config.js, assets/css/main.css – UI styling setup
• public/ – static, public-facing files (favicon, robots.txt, etc.)
• .github/, .gitignore, .npmrc, .editorconfig, .vscode/ – repo tooling & CI/CD configs
Nuxt folders
• pages/ – route definitions (Login.vue, Register.vue, profile/[id].vue, restaurant/[id].vue, etc.)
• layouts/ – layout templates (default.vue)
• components/ – reusable UI components (NavUser.vue, ReviewBox.vue, UploadPicture.vue, etc.)
• server/ – (empty except tsconfig) placeholder for server middleware or API routes if needed
README for additional insights
• Confirms tech stack: NuxtJS + Supabase
• Highlights use of Supabase for both database & authentication
• Notes deployment via Vercel (live site redirect on “forgot password”)
• Mentions environment variables stored in .env for local dev
Detail and component separation
• Break the front end into “Routing (pages/)”, “UI Components (components/)”, “Layouts (layouts/)”, and “Assets (public/ & assets/)”
• Server or API folder as a distinct microservice or function group (even if empty today)