How maximecloarec/projet-griffon-nuxt works
Project type and purpose
• This is a Nuxt 3–based web application (Vue 3 + TypeScript + Pinia-like stores), using file-based routing and server‐side rendering (SSR).
• Its purpose is to serve a multi-page game/join site with authentication, client-side state management, and static asset delivery.
File structure
• Top-level “app” folder holds the entire front-end:
• pages/ → Route definitions (file-based routing)
• components/ → Reusable UI pieces
• middleware/ → auth guard logic for protected pages
• stores/ → Pinia store (user.ts) for user session and state
• assets/, public/ → Styling (CSS), SVGs, robots.txt, other static files
• utils/ → Shared TypeScript types
• nuxt.config.ts configures the framework (SSR, build, modules).
• No dedicated “backend/” folder—implies either purely client + SSR or reliance on external APIs for persistent data.
Key insights from README
• It’s a minimal Nuxt starter, intended for local dev (npm/ pnpm/ yarn/ bun), SSR dev server at localhost:3000, static/SSG preview, and production builds.
• No mention of built-in database or API routes—architecture centers on Nuxt’s SSR/SPA capabilities.