How suspishes/cedevita works
Project type and purpose
• This is a full-stack e-commerce/blog site built with the T3 Stack (Next.js 13 App Router, TypeScript, Prisma, Tailwind CSS, MDX, server/client React components) plus a Stripe payment integration.
• It serves product pages (src/app/Izdelki), an MDX-powered blog (src/clanki + src/app/blog), a shopping cart (src/app/kosarica), contact form, about, services, references, etc.
File structure
• Top level
• next.config.js, tsconfig.json, package.json – Next.js + TypeScript config
• prisma/schema.prisma & start-database.sh – database schema & startup script
• public/ – static assets
• src/app/… – Next.js App Router folder: pages, API routes, shared components
• src/server/db.ts – Prisma client setup
• src/clanki/*.mdx – raw blog content
• mdx-components.tsx – custom MDX components
• Next.js conventions
• server components (default .tsx under src/app)
• client components (files importing "use client") under components/client.tsx
• API routes under src/app/api/create-payment-intent/route.ts
README for additional insights
• Confirms technologies: Next.js, Prisma, Tailwind, Drizzle (not currently in tree), tRPC (not evident in code), NextAuth (not evident).
• Suggests deployment targets: Vercel, Netlify, Docker.
Elements
• Browser / User Interface
• Next.js App Server (App Router)
• API Route / Payment Service
• Prisma Client / DB Layer
• Database (e.g. Postgres)
• MDX Content Loader
• External: Stripe
• Static Assets (public/)
• Request/response between browser ↔ Next.js
• Data fetch from Next.js → DB
• API call from browser → API route → Stripe
• MDX file read → Next.js → browser
• Frontend (blue)
• Server/API (green)
• Data store (orange)
• External services (purple)