Full-stack2026
TAKLIFNOMA
- Role
- Full-stack · sole author
- Stack
- Next.js 16 · Prisma · PostgreSQL · Auth.js · grammY · next-intl · Tailwind v4 · MUI
PROBLEM
A separate invitation site per customer means a separate deployment and a separate bill. Taking orders, editing and publishing were all handled by hand.
SOLUTION
Every invitation is one database row served at /i/[slug] through ISR, so a new customer never needs a new project. Orders arrive through a Telegram bot, an admin customises the template and publishes it, and guests RSVP. Front end and back end live in one Next.js repo.
1
repo, one deployment
4
locales: ru · en · uz · uz-Cyrl