How ftanborn/tan-link works
Project type and purpose
• This is a full-stack, server-centric Next.js application (built with Next’s App Router) that provides user profiles and link dashboards.
• Key features from the file tree and README:
• Frontend pages under src/app (Home, Auth flows, Dynamic profiles via [slug], Dashboard).
• A serverless API route for Cloudinary uploads (src/app/api/cloudinary/route.ts).
• Client-side state via React Contexts (AuthContext, ThemeContext, TourContext, ProfileThemeContext).
• Integration with Firebase (src/config/firebase.ts) for auth/data and Cloudinary for media.
• Analytics service and custom hooks for tracking.
File structure
• Top-level Next.js config: next.config.ts, tsconfig.json, package.json, public/
• src/app (Next.js pages and layouts)
• /api/cloudinary (backend serverless function)
• /auth (login, register, setup-username flows)
• /dashboard (appearance, links, profile, stats sub-pages)
• /[slug] (public user profiles)
• /r (possibly redirect short links)
• Shared error, loading, not-found handlers and global layout.
• src/components (reusable UI elements organized by feature)
• src/context (React Context providers for auth, theme, guided tours)
• src/services & src/hooks (analytics, API wrappers, custom React hooks)
• src/config (Firebase init) and src/theme (provider)
README
• Confirms Next.js App Router usage, dev commands, and deployment target (Vercel).
Details
• Dynamic route handling ([slug] → renders ProfileComponent).
• Static assets served from public/.
• Build/config files (next.config.ts) in a “Project Config” note.