How scheffchuk/my-site works
Project type and purpose
• From the file tree, this is a Next.js full-stack application (using the app directory convention) that serves a multilingual personal/portfolio website with interactive features (e.g., AI chat and contact form).
• Key indicators:
• src/app/[locale]/… folder structure → i18n routing
• src/app/api/chat/route.ts → serverless API endpoint (chat)
• src/actions/sendEmail.ts → serverless email send action
• src/lib/astradb.ts → integration with Astra DB or similar datastore
File structure
Top-level files
• .eslintrc.json, .prettierrc, tsconfig.json → code quality and TypeScript config
• next.config.ts, postcss.config.mjs, tailwind.config.ts → Next.js & styling configuration
• package.json, pnpm-lock.yaml → dependencies and package manager
Key directories
• src/app/[locale]/…
– layout.tsx, page.tsx, globals.css → Next.js App Router layout/pages per locale
– api/chat/route.ts → serverless function for AI chat
• src/components → React UI components (header, footer, sections, UI primitives)
• src/actions → “backend” action functions (e.g., sendEmail) invoked on form submits
• src/lib → shared utilities and data clients (Astra DB, hooks, types, utils)
• src/email → email template code for contact form
• src/context → React context providers (active section, theme)
• src/i18n & messages → translation dictionaries and routing/navigation i18n helpers
• scripts/generate.ts → likely codegen for translation or assets
README
• (Empty in this case—no additional architectural hints.)
Detail level
• Folder’s responsibility (e.g., src/lib as Utilities Layer).
• Grouping: UI components vs. context providers vs. API handler code.
• With key files or modules (e.g., route.ts under API).